Conversion via the address of the confirmation page

1. 01Open “Orders & goals” and create a conversion, for example with the template “Lead form”, “Sign-up”, “Appointment” or “Your own goal page”. In the setup assistant, choose “Sign-up via the confirmation page” for an application, or the trigger “A confirmation page is opened” for a shop.
2. 02Enter the path under “Address of the confirmation page”, for example /thank-you. A full address from the address bar works too; Metrunio takes the path from it.
3. 03Choose the comparison: “equals” for exactly this page, “starts with” for every page whose path begins like this, “contains” for a part anywhere in the path.
4. 04Save. After one minute at most, every matching page view counts.
5. 05Check it with your real page: submit the form once yourself, accept statistics in the banner and look at the live checklist in the setup.

What is compared

Metrunio compares the path of the opened page as it is stored: without the query (everything from ?) and without the anchor (from #). Upper and lower case do not matter, nor does a trailing slash. /Thank-you/?source=mail is therefore the same page as /thank-you.

Numbers and identifiers in the path, such as /order/12345, are stored as :id. A rule with the number would never match, so the portal rejects it. Use “starts with” and the part before it, /order. The portal does not accept an address with @ either: that would be an email address, not a path.

What counts

The conversion takes the type of the template, so an enquiry for “Lead form”, “Sign-up” and “Appointment”, and the value of the definition. A fixed value is a set acquisition value and never part of revenue; the page view itself brings no value. The conversion is measured, because the page was opened. From there it works like every conversion: it is attributed to the touchpoints before it, appears in the journey and is returned to connected ad platforms as far as the visitor’s consent allows.

Limits

• Only with consent to statistics. Without it, Metrunio does not measure the page view, and no conversion is created.
• Once per visit and conversion: reloading, the back button or a second view in the same visit does not count again. A later visit by the same person counts again.
• From the moment you save: earlier page views do not become conversions afterwards. If you change the address or the comparison, the new rule applies from then on.
• Excluded pages: if the confirmation page falls under “Excluded pages”, Metrunio does not store its path, and no rule can match. For “equals” and “starts with” the portal tells you when you save; for “contains” check it yourself.
• Single-page apps: only what the SDK measures as a page view counts. If your application changes the address when it switches to the confirmation, the SDK measures the switch by itself. If it shows the confirmation without a new address, there is no page a rule could match; report the enquiry with a call instead.
• One page view, one conversion: if two rules match the same page view, the older one counts.
• Own identifier: the conversion carries an identifier that Metrunio builds from visit and goal. It does not link to your CRM. If you need that link, report the enquiry with an identifier (article “How does the origin of an enquiry get into my CRM?”).
• The button “Trigger test conversion” in the assistant sends a test enquiry, not your page. You only check the address route by opening the page yourself.