Installation
Measuring leads, sign-ups and purchases with Google Tag Manager
Add another tag from the “Metrunio Tracking” template, set the tag type to “Conversion” and pick the kind: goal step (such as a sign-up), lead or purchase. The fields take variables from your data layer; the tag fires on the event of the action and, in tag sequencing, after the base tag. If no decision has been made in the banner yet, Metrunio drops the conversion instead of holding it back.
How do I measure leads, sign-ups and purchases with Google Tag Manager?
The “Metrunio Tracking” template has two tag types. The base tag loads Metrunio on all pages. A tag of type “Conversion” reports a single action, and you add as many of them as you have actions to measure. There are three kinds: a goal step is a step of your funnel, such as the sign-up, and counts once per customer. A lead comes from a form or an appointment. A purchase is an order with an order number.
Report a sign-up as a goal step if further steps follow, such as set up and first payment. If the sign-up is the close itself, report it as a lead.
Step by step
- 01Check that the base tag runs: a tag from the template with the tag type “Base (loads Metrunio)” and a trigger for all pages. The article “How do I connect Google Tag Manager?” shows how to add it.
- 02Add the variables. Under “Variables”, add a data layer variable for each value your page writes into the data layer, for example transaction_id, value and currency. If your data layer does not provide a value, leave the field in the tag empty.
- 03Add the trigger. If your page writes an event into the data layer after the action, such as purchase or sign_up, use a trigger of type “Custom Event” with that name. Otherwise use a page view trigger on the thank-you page.
- 04Add the tag: a new tag from the “Metrunio Tracking” template, tag type “Conversion”. Pick the kind and fill the fields. You insert a variable through the icon next to the field.
- 05Set the tag sequencing. Under “Advanced Settings” and “Tag Sequencing”, choose to fire the base tag before this tag, and not to fire this tag if the base tag fails.
- 06Check in preview. Trigger the action and open your browser’s console. “Metrunio: conversion handed over” means the tag passed the conversion to Metrunio. “Conversion dropped” means no decision had been made in the banner yet.
- 07Publish the container and check in the portal under “Orders & goals”. The conversion appears there; a goal step with a new key creates its definition there by itself, and you can add its name and value.
The fields per kind
| Kind | Required | Optional | What the tag reports |
|---|---|---|---|
| Goal step | key, such as signed_up | customer ID | first the customer ID, then the step |
| Lead | nothing | lead ID, value, currency | a lead |
| Purchase | order number | value, currency | a purchase |
With a customer ID, a goal step counts once per customer; without it, once per browser. Without a lead ID, Metrunio takes the ID it wrote into a form in this session. If there is none, Metrunio does not accept the lead. If your form or CRM provides an ID, enter it: a later import from the CRM then finds the lead again. The tag reads the value with a point or a comma; without a currency, EUR applies.
When a conversion is dropped
Metrunio only measures after the decision in the banner. If the conversion tag fires before it, Metrunio drops the conversion with all its details and does not catch up on it after a later consent either. This mainly happens on thank-you pages: the page loads, the tag fires at once, and the consent tool has not yet reported the stored decision.
- Fire the tag on an event after the action instead of on the page view.
- Place it after the base tag in tag sequencing.
- Pick your tool under “Consent tool” in the base tag so Metrunio takes the decision early.
- Also report purchases and leads that must not be missing through the Server Events API from your shop or CRM.
Note
The template does not hold back a conversion without a decision, not even for a moment. If consent has already been given and Metrunio has not loaded yet, it waits until the base tag has loaded Metrunio. That keeps the sentence in the privacy policy true that nothing sits in working memory before the decision.
And the trigger in the setup wizard?
When you add a conversion in the setup wizard, you pick a trigger such as “An existing GTM event” or “Data layer event”. It only describes where you expect the conversion from. Counting goes by kind: a purchase counts for the conversion of type purchase, a lead for the one of type lead, a goal step by its key. The conversion tag is the route by which such an event gets from Tag Manager to Metrunio.
Last reviewed on 20 Oct 2026
In the customer portal
Also asked
- How do I measure a sign-up with Tag Manager?
- How do I report a lead through GTM?
- How do I pass the order number and value from the data layer to Metrunio?
- metrunio.goal in Google Tag Manager
- Metrunio conversion tag in Tag Manager
- Why does my conversion from Tag Manager not arrive?
- What does “conversion dropped” mean in the GTM preview?
- Does the conversion tag have to fire after the base tag?
Related articles
- How do I connect Google Tag Manager?
How do I install Metrunio through Google Tag Manager?
You download the “Metrunio Tracking” template as a file in “Setup” and import it into your container, without any change to your website’s source code. You create a base tag from it, enter the write key, choose the trigger “Initialization - All Pages” and publish. For leads, goal steps and purchases you add more tags of tag type “Conversion” from the same template.
- How do I report a funnel step?
How do I send the steps of my funnel from the browser or the backend?
In the browser with
metrunio.identify(userId)once after sign-in and thenmetrunio.goal('key')per step; from the backend withPOST /v1/server/eventsand an event of typegoalcarryinggoal_keyanduser_id. Both routes are equivalent; a step without a customer identifier is rejected. - How do I test my first conversion?
How do I check that a conversion arrives correctly?
The setup assistant has a step called “Run a test conversion”. It creates a test for the goal you set up: a test purchase or a test sign-up with a test visit before it, or the first step for funnel steps. Everything is stored as test data, appears immediately in the live checklist and stays excluded from standard reports. The test does not prove the installation on your website.
- How does Metrunio take the decision from my consent tool?
Do I have to call metrunio.setConsent myself if I use Usercentrics, Cookiebot, Complianz, Borlabs Cookie, Real Cookie Banner or another common consent tool?
Through the consent bridge, without you calling
metrunio.setConsentyourself: for thirteen tools this small additional script reads the decision from your banner and passes it to Metrunio, including every later withdrawal. The installation code in the portal contains it as soon as you choose your tool in the consent step, and the Shopware plugin adds it by itself. - 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.
- How do I get CRM deals into the reporting?
Can I import conversions that did not happen on the website?
You import them as CSV: a lead closed on the phone weeks later just as well as a purchase in the shop. Matching happens through a unique anchor (order ID, lead ID or click ID); rows without such an anchor are rejected rather than guessed.