Skip to content

INTEGRATION

Four ways in, your data out at any time.

Shopify app, plugin for Shopware or WordPress, Google Tag Manager, code snippet or Server Events API: all lead to the same data model. You pick the route that fits your system, and the connection test tells you whether data is arriving. Costs and pushback come afterwards: with a sign-in for Google Ads and Meta, and at about an hour per ad platform for TikTok, LinkedIn and Microsoft Advertising.

After you sign up, the wizard shows you the steps and the time remaining.

01 / ROUTES

From shop plugin to server API: one data model.

ROUTE 01 / RECOMMENDED

Google Tag Manager

Import the template, insert site ID and write key, publish. No change to your source code.

ROUTE 02

Code snippet

One block in the head section. With guides for WordPress, Shopware, Webflow and plain HTML.

ROUTE 03

Server events API

Your shop or CRM reports conversions directly, independent of the browser. With HMAC signature and replay protection. If you sell through Stripe or PayPal, no code is needed: Metrunio accepts their webhooks.

ROUTE 04 / SHOPIFY, SHOPWARE, WORDPRESS

Shopify app, plugin for Shopware or WordPress

Install and connect it. If you don’t have a Metrunio account yet, the app creates one, with no second sign-up. In the same step you conclude the data processing agreement; before that the app measures nothing. Then switch on the app embed in your theme; the app tells you whether it’s on. It measures storefront, checkout and order at once. No custom script runs on Shopify’s payment pages, so a snippet in the theme measures nothing there. For Shopware 6 the same comes as a plugin: install it, connect it in its settings, choose your consent tool. It reports orders, cancellations and refunds straight from the shop server. For WordPress there is a plugin that does the same with WooCommerce: install it, connect it in its settings, check the consent tool it detected. Without WooCommerce it measures page views and ad contacts, but no form enquiries. You download the plugins in the portal under “Setup assistant”. The app’s installation link is there too, or we send it to you by email.

02 / SHOP SYSTEMS

One page per shop system.

What the extension measures on your system, how you install it and where its limits are.

03 / CONSENT

Your CMP stays your CMP.

Metrunio does not replace consent management. It reads the state from the system you already use.

Ready-made presets for Google Consent Mode, IAB TCF, Usercentrics, Cookiebot, consentmanager, CCM19, OneTrust and the Shopware cookie manager, for WordPress also Complianz, Borlabs Cookie, CookieYes, Real Cookie Banner and the WP Consent API, plus generic CMPs and custom consent APIs. Except for the generic and custom ones, the installation code takes the decision from your banner by itself, including every withdrawal, and does not count consent given without a click. A check view on your own website shows which tool it detects and what that tool reports. A rule check runs six cases against your setting; whether your website reports consent and withdrawal correctly shows in the live test with real page views, each signal with its time and consent status.

By default, Metrunio stores nothing without matching consent, not even a purchase in the browser, and the tracking script sends nothing before a decision. One documented case differs: orders and refunds your server reports without consent count towards revenue for reconciliation, with their order number and without browser, customer or advertising identifiers, and are not attributed, except via the checkout if you switch it on. After a refusal in the banner this only applies with an activated additional instruction for revenue reconciliation. Without consent on the ad side, the click redirect passes on only the campaign, no click ID. Anonymous reach measurement before consent is hidden. What happens without consent

04 / ORIGIN

Google, Bing and ChatGPT identify themselves.

Where a visit came from is already in what the browser sends. You set up nothing at any platform for it.

The platforms’ click identifiers (gclid, msclkid, fbclid, ttclid) and the referrer give you channel and source: paid search, organic search, organic social, AI assistants, email, referral. Auto-tagging is enough. An ad account is connected only for what the click does not carry: campaign names and cost. Where every signal is missing the channel is “Direct”, and that means “we do not know where from”, not “someone typed the address”.

What is recognised without setup and what is not

05 / PLATFORMS

Meta, Google Ads, TikTok, LinkedIn, Microsoft.

For these five the exchange runs both ways: automatically, through your own access to the ad account, which is held encrypted.

  • Costs come in

    Every six hours and retroactively, because the platforms revise their figures; the first fetch comes minutes after connecting, and “Fetch now” fetches in between. Anything that cannot be matched to a campaign is left out rather than guessed. The connection lists those campaigns, and you assign them there or create them with the channel of your choice.

  • Conversions go back

    Via the click identifier: gclid, fbclid, ttclid, li_fat_id, msclkid. Without a matching click the conversion is skipped, with the reason recorded. Per destination you choose whether the platform receives the revenue or the contribution margin of a purchase, and whether it only receives purchases by new customers.

  • Closings without a website

    Offline conversions from CRM, point of sale or phone sales can be imported and joined to the measured journey via order number, lead identifier or click identifier. The SDK writes the lead identifier into your form itself, together with source, medium and campaign: it travels with the enquiry into your CRM and comes back with the deal. On every plan.

  • Measurement over your address

    A custom measurement domain such as gauge.your-domain.com. Ad blockers and browser tracking protection then cut less often, and with consent the same visitor identifier applies on every subdomain of your website.

With Google Ads and Meta you sign in with your account at the platform and then pick from a list what gets connected: the ad account, and for pushback to Meta the pixel; for pushback to Google you also enter the conversion action. There is no token to fetch, and one sign-in covers both the cost import and pushback (costs from Pro, pushback from Growth). TikTok, LinkedIn and Microsoft Advertising are still connected with an access token and the account and customer numbers from the ad account, because signing in with them requires a partner approval; Microsoft Advertising also needs a developer token that has to be approved. Budget the better part of an hour per platform there, and someone with access to the ad account. The help centre walks through it field by field.

Five platforms hand over costs automatically and take conversions back; for those five we stand behind the result. For DSPs, ad servers and affiliate networks, the CSV import is the intended route: you measure impression, viewability and click there yourself anyway, and for the costs alongside them a file is enough, or a sheet that Metrunio reads every day.

Which credentials the ad platforms ask for, and where they live

06 / OUT

Your data goes back out.

Your raw data is available for export in full at any time, in the same state the reports are calculated from.

  • CSV at raw-data level

    Recalculate every figure yourself, at no extra charge while the contract runs.

  • Read API

    Your own key, documented as OpenAPI. For your own reporting and business intelligence; templates for Google Sheets, Power BI and Excel are in the help centre. From Growth.

  • MCP server

    Your measurement data in Claude, ChatGPT or your own AI tool: not as an export, but as a question. From Growth.

  • BigQuery

    For reports across long periods, Metrunio calculates from a mirror in BigQuery. Your queries go through the same read API, with the same figures.

  • Webhooks

    New orders and leads, refunds, alerts and cost syncs go signed to your CRM or to Zapier and Make. They carry no browser or customer identifier, but they do carry the order or lead identifier, value and time, and these can be personal data. From Growth.

  • Slack and Teams

    Alerts and the weekly or monthly report as a short summary in your channel, with a link to the portal. On every plan.

How GA4, Matomo and the platforms hand out raw data

07 / AFTERWARDS

How the installation works.

A guided assistant in six phases, from company and DPA to the first verified journey, an automatic connection test and error messages that name the next step. The ready-made code blocks are generated in “Setup” after you sign up. Measurement starts only once the data processing agreement is concluded, in the portal or right in the Shopify app.

The six phases in detail

See what your data tells you.

Look around in the demo first. Your own account is currently available by invitation only.

Open the demoRequest access