Les articles d'aide existent en allemand et en anglais. Vous les lisez ici en anglais.
Installation
How do I measure over my own domain?
In “Setup” you enter a name such as gauge.your-domain.com, and Metrunio gives you three DNS records at once (two CNAME and one TXT). Once they are in place and a certificate has been issued for your name, the address goes live; with the snippet or Tag Manager you then switch your setup, while the Shopify app and the plugins for Shopware and WordPress switch themselves. Measurement then runs first-party and is cut less often by ad blockers and browser tracking protection.
How do I set up a custom measurement domain so ad blockers cost me less data?
Some of your visitors block addresses that do not belong to your domain. What gets lost is not evenly distributed: it skews towards technically minded people and towards particular channels. A custom measurement domain reduces that loss.
How to set it up
- 01Have a website added. The measurement domain belongs to it; without a website the card shows this notice instead of the input field.
- 02In the portal under “Setup”, enter a name, for example gauge.your-domain.com. Not your domain itself: your website lives there.
- 03Create the three records shown at your DNS provider: a CNAME to our target host, a TXT record as proof and a CNAME under _acme-challenge for the certificate, that one without a proxy. With some providers, the provider creates all three in a single click (see below).
- 04Wait. We keep checking; after you add the records it usually takes minutes, occasionally hours.
- 05As soon as the address works, it goes live by itself and you get an email. What to do next depends on how Metrunio is set up on your site (see the next section). There is nothing to switch before that: your current setup keeps measuring.
Note
The TXT record is needed when your provider hides the CNAME, for example Cloudflare with the proxy switched on. There a DNS lookup shows an IP address instead of the chain, and without the TXT record there would be no way to prove the domain is yours.
Note
The third record (_acme-challenge) belongs to the certificate. Google uses it to check that the domain is yours before issuing a certificate for your name. Without it the proof still passes, but the address never goes live.
After going live: depending on your setup
The go-live email and “Setup” name the step for each way your website measures. If it measures in several ways, each of them applies. Until you have switched, your current setup keeps measuring over the shared address; nothing is lost.
- Code snippet: replace the tracking code on your website. The code in “Setup” now names your address.
- Google Tag Manager: the “Metrunio Tracking” template only loads scripts from the address it contained when you imported it. Download it again in “Setup”, import it in GTM over the existing template (Templates → Metrunio Tracking → ⋮ → Import), enter https:// followed by your address in the Metrunio tag’s “Collector address” field, and publish the container.
- Shopify app: there is nothing for you to replace. The app switches the theme embed, the checkout pixel and the order reports to your address by itself. That happens at the latest the next time you open it in the Shopify admin, and earlier if your theme changes. Best open it once right away.
- Plugins for Shopware and WordPress: there is nothing for you to replace. The plugin switches the snippet, the consent bridge and the order reports to your address by itself, within an hour at the latest or as soon as you open its settings. Cached pages carry the old address until the cache renews them and keep measuring over it until then; if you want it at once, clear the cache.
- Server Events API: nothing changes for calls from your server. Ad blockers and browser tracking protection only act in the browser; the shared address keeps accepting your calls. You can switch, but you do not have to.
Note
No app switches the ad pixels and viewability tags in your campaigns, not even the Shopify app. They sit on other people’s pages; replace them so that pixel, tag and tracking code name the same address.
Caution
If you remove a live measurement domain, the same applies in reverse: its certificate is cleared away within an hour. Switch the tracking code and the GTM tag back first, and with Shopify open the app once afterwards. Until then your shop does not measure.
One identifier across subdomains
Through your measurement domain, Metrunio also sets the visitor identifier as a cookie on your domain (metrunio_aid), only with consent to analytics. www.your-domain.com and checkout.your-domain.com then see the same visitor, and someone who clears your site’s storage in their browser but keeps the cookies is recognised. The cookie is HttpOnly, lasts 13 months and disappears when consent is withdrawn or with metrunio.reset().
- The cookie only exists when your page sits under the same domain as the measurement domain: gauge.your-domain.com for www.your-domain.com and checkout.your-domain.com. Through the shared address, Metrunio sets none.
- If the browser brings the cookie along, its identifier applies, and the SDK takes it over into its storage.
- Without consent to analytics it is neither set nor read. If it arrives anyway, Metrunio removes it.
Note
Safari shortens cookies set through a measurement domain with a CNAME to seven days. If someone returns with Safari after more than a week, a new identifier begins. We promise nothing beyond that.
Your visitors should be able to read this before they decide in the banner. So name metrunio_aid in your consent management under analytics and in your privacy notice: name, reach (all subdomains of your domain), purpose (linking visits and orders of the same browser, even after the site’s storage was cleared) and duration (13 months, seven days in Safari).
Legal note
The cookie carries the same identifier as the site’s storage and is only set with consent to analytics. A new data processing agreement or a checkbox of its own is not automatically needed for it. Whether your description of analytics covers the wider reach is for you to check as the controller.
A path of its own for the SDK
With the code from the setup, your website no longer loads the SDK from /v1/t.js but from a random path under your measurement domain, such as gauge.your-domain.com/3f9a1c7e2b4d.js. A freshly downloaded GTM template uses it too, and the WordPress plugin picks it up by itself once the domain is live. Older code keeps loading as before, as do the Shopware plugin and the Shopify app.
Note
The path changes where the script lives, not what it does: without consent it still measures nothing. We make no promise against ad blockers with it.
Why it takes a moment
Your browser connects to gauge.your-domain.com and expects a certificate for exactly that name. We request it as soon as the CNAME or TXT record is verified, and Google issues it once it sees the _acme-challenge record (usually within minutes, occasionally within an hour). Until then the tracking code, the template and the Shopify app keep naming the previous address: switching earlier would send the browser to an address whose certificate it rejects. That would be an outage, not progress.
After going live: keep all three records
The certificate is valid for 90 days and renews itself through the _acme-challenge record. If you delete it, your address keeps measuring at first, but renewal fails, and once the certificate expires it measures nothing. We therefore check regularly: if the record is missing, the certificate expires in less than three weeks, or the address does not respond, you get an email, and “Setup” shows what to do.
Names that will not work
- Your domain itself (your-domain.com). Your website’s record lives there, and a CNAME cannot coexist with any other record on the same name: your website would go down.
- www, mail, smtp, mx and similar. They carry your website and your email; a CNAME there halts your operations.
- A name someone else has already claimed with us. A hostname belongs to exactly one party in DNS.
Without typing: your provider creates the records
Below the records there is a “Check provider” button. It checks whether your DNS provider supports the Domain Connect standard and has enabled our template. If both are true you are taken there, sign in, and see what is to be created before you approve. Your provider creates all three records itself. Its window then closes and you are back in the portal: the card checks by itself and shows the new status as soon as we see the records (under a minute in our own test). If not, the button says so and you enter the records by hand. Which providers are covered is deliberately not listed here: the list changes, and a name that is here but does not apply there costs you a wasted attempt.
Note
Metrunio gets no access to your domain and no password. We only assemble the address on which you approve; everything else happens between you and your provider.
Strato, United Domains, Hetzner, All-Inkl and DomainFactory do not support the standard. For their customers it stays with typing. That is the normal route.
Caution
Even this does not make measurement complete. Anyone using a resolver such as NextDNS or Pi-hole has a device that follows the CNAME chain and sees where it ends. The request is dropped before the browser is involved. That affects a small share, but not none, and no provider gets around it.
Dernière vérification le 13 oct. 2026
Dans le portail client
Également demandé
- own domain for tracking
- set up CNAME for measurement
- first-party tracking
- get around ad blockers
- less data loss from ITP
- subdomain for tracking
- What is the _acme-challenge record?
- certificate for measurement domain is not issued
- Can I delete the _acme-challenge record?
- Do I have to replace the tracking code with Shopify?
- measurement domain with the Shopify app
- switch the measurement domain in Google Tag Manager
- What do I do once my measurement domain is live?
- cookie on your own domain
- visitor identifier across subdomains
- What do I have to say about metrunio_aid in the cookie banner?
Articles connexes
- How do I install the code snippet?
How do I install Metrunio without a tag manager?
The finished code block is in the portal under “Setup → Snippet” and contains site ID and collector address. You see the write key only once, when it is created; if it is no longer known, the code carries the placeholder YOUR_WRITE_KEY and a button next to it creates a new one. The block belongs immediately before the closing head tag and loads asynchronously.
- How do ad blockers affect measurement?
Do I lose data to ad blockers and browser protections?
Ad blockers and browser protections cost part of the browser signals, as with any client-side measurement. Metrunio does not circumvent these protections. Conversions can instead be reported server-side, where the browser plays no part.
- Where do I install tracking in my shop system?
How do I install Metrunio in WordPress, Shopify, Shopware or Webflow?
For Shopify, Shopware 6 and WordPress with WooCommerce there is an extension that measures visits, consent and orders at once. The other systems have a place for custom head code; the table names the route per system. Without an extension, we additionally recommend the Server Events API for purchases, because it works independently of the browser.
- How do I connect Google Tag Manager?
How do I install Metrunio through Google Tag Manager?
You add the “Metrunio Tracking” template from the Tag Manager template gallery or download it as a file in “Setup”. You create a tag from it, enter site ID and write key, choose the trigger “Initialization - All Pages” and publish. This route needs no change to your website’s source code.
- How do I set up Metrunio in Shopify?
How do I connect my Shopify store to Metrunio?
You install the Metrunio app in your store via its installation link: from the setup assistant in the portal or from our email. If you do not have a Metrunio account yet, the app creates one without a second sign-up once you accept the terms and conclude the data processing agreement with two tick boxes; an existing account you connect by signing in to the portal. Measurement starts only once the DPA is concluded, and then covers storefront, checkout and order at once, with no change to your theme code.
- How do I report conversions server-side?
How do I send events from my shop, CRM or backend?
Through POST /v1/server/events to the collector, with the server key in the authorization header. The portal shows the address and the ready-made call for your website under “Setup” on the “Server Events API” tab. The call is independent of the browser and therefore robust against ad blockers and short-lived cookies.
- Which emails does Metrunio send, and how do I stop them?
I would like fewer emails. Which ones are there, and what can I unsubscribe from?
There are five kinds: operational messages (invitation, password, invoice, event allowance notices and the end of the trial), the weekly or monthly report, getting-started notes during the first few weeks, for agencies two emails about their clients (the weekly email about clients with open items and the monthly report as a PDF), and the newsletter. The first kind cannot be unsubscribed from, because without it access or billing does not work. You unsubscribe yourself from the report, the getting-started notes and the two client emails under “Settings → Notifications → Your emails”; with the Admin role you can also switch the report and the notes off for everyone there. You unsubscribe from the newsletter through the link in every issue.
- Which data is stored?
What exactly does Metrunio hold about my website’s visitors?
Pseudonymous identifiers, event data with timestamps, campaign and click identifiers, and conversion values. No raw IP addresses; event fields are not meant to hold plain-text names or contact details. Detected email addresses and phone numbers cause rejection; the automatic check does not detect every kind of personal data, though.