Installation
Do click IDs get lost in a redirect?
The tracking checker on the website at /en/tracking-checker shows you, without an account: it calls your address with test values for gclid, fbclid, msclkid, ttclid and the UTM parameters, follows up to five redirects and shows at which one a value gets lost. It also names the consent tool and tracking tags found in the page’s HTML.
How do I check whether gclid, fbclid and UTM parameters reach my website?
When someone clicks an ad, the ad adds its ID to the address: gclid for Google, fbclid for Meta, msclkid for Microsoft, ttclid for TikTok, often with UTM parameters as well. The tags on the landing page read them there. If your website redirects first, from http to https, from your-shop.com to www.your-shop.com or into a language folder, and drops the part after the question mark on the way, none of it arrives. The page still loads, which is why it rarely gets noticed.
How to check
- 01Open the tracking checker at /en/tracking-checker.
- 02Enter the destination URL of one of your ads, exactly as it appears in the ad.
- 03Under “Redirects”, read which step drops which values, and under “Test values”, what arrives at the last address.
If the page says “The tracking checker is not available right now” instead of showing the form, we have switched it off for the time being. Try again later.
If values get lost
- Set up the redirect so it keeps everything after the question mark.
- Or point your ads straight at the last address in the chain. Then there is no redirect left that could drop anything.
- Check again afterwards.
What the checker reads and what it does not
On the last page it reads the HTML your server delivers and names known consent tools and tracking tags, including the Metrunio installation code. It does not run JavaScript. Anything a script loads later, such as tags from Google Tag Manager or through Shopify’s pixel interface, is not in the HTML and so does not appear in the list. Whether a tag actually fires only shows on a visit in a browser.
The result shows the host, the path and the test values of every address. Other values after the question mark appear as “…”, such as a session ID or the token of a sign-in link; the check does not need them. The same goes for a part of the path that looks like an identifier, such as the token in /reset/aZ3kP9qL2mX7vB4nR8tW. Words, slugs and short numbers such as /en/products/blue-shoes-42 stay as they are.
Note
The checker sends no cookies. A shop that sets a cookie on the first visit and then redirects back therefore shows up as a circle of redirects, even though the page loads in a browser. If the last address answers with 403 or 503, protection against automated requests is often behind it.
No account, nothing kept
The checker needs no account and does not ask for contact details. Do not enter confidential links, access tokens or personal data: our servers call the address you enter. We process the address and the result only for the check and do not keep them. All we count is how often checks come from one connection, using a checksum of the IP address that is forgotten after ten minutes. Only public addresses on ports 80 and 443 are called, for the address you enter and for every redirect. In your server’s logs the checker shows up as MetrunioTrackingCheck.
Last reviewed on 16 Oct 2026
Also asked
- Tracking checker
- gclid lost after a redirect
- fbclid missing after a redirect
- Do UTM parameters survive a redirect?
- Redirect from http to https drops parameters
- Which consent tool does my website use?
- Is my tracking installed correctly?
Related articles
- Are Google, Bing and others recognised automatically?
Do I have to set anything up at Google or Bing for the source to be recognised?
Automatically, with nothing to set up at Google or Bing. Metrunio reads the origin from what the browser sends anyway: the referrer and the platforms’ click identifiers (gclid, msclkid, fbclid, ttclid). Channel and source therefore appear in the report straight away. You only need to connect something if you also want campaign names and cost: that is what linking the ad account is for.
- Do I still need UTM parameters?
How do UTM parameters relate to Metrunio click tracking?
UTM parameters are still read and stored, but they are the weaker source. Where a Metrunio click URL is in use, a signed click with an unambiguous identifier is created; UTM remains useful for channels where you cannot set your own tracking link.
- 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 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 connect my consent tool?
Which consent tools behind my cookie banner are supported, and how do I map the categories?
In “Setup” you select your consent tool, the tool behind your cookie banner; for the common systems the categories are pre-filled. Other CMPs and custom consent APIs can be mapped freely.