Ir al contenido

Los artículos de ayuda existen en alemán e inglés. Aquí los lees en inglés.

Primeros pasos y cuenta

How do I test my first conversion?

The setup assistant has a step called “Run a test conversion”. It creates a test purchase with a test visit before it, both stored as test data: they appear immediately in the live checklist, the journey shows an attributed touchpoint, and they stay excluded from standard reports.

How do I check that a conversion arrives correctly?

  1. 01Open “Setup” and go to the step “Run a test conversion”.
  2. 02Click “Trigger test conversion”. Metrunio sends a test visit with the campaign “metrunio-test” and, one minute later, a test purchase of €99, both as test data.
  3. 03Watch the live checklist: “Conversion received” and “Journey created” must appear.
  4. 04Check the journey under “Customer journeys”; “Show test data” switches the list to test data.
  5. 05Reset the test data before you go live.

To verify your own shop end to end, place an order in test mode as well: set testMode: true in the SDK, or send the server event with environment: "test".

Funnel steps of an application are checked under “Orders & goals”: “Send test step” on a step creates a test event that counts immediately as a conversion of that step, in the test data and not in the reports.

Note

The test visit is only an example so you can see what an attribution looks like; it never appears in production data. If a real order shows the conversion but without a measured touchpoint before it, and therefore unattributed, a shared identifier between website and shop is usually missing. The article “Why is a conversion not attributed?” lists the possible causes.

Revisado por última vez el 15 oct 2026

En el portal del cliente

Go to setup

También se pregunta

  • How do I test tracking?
  • How do I trigger a test conversion?
  • Is my conversion tracking working?
  • What is the metrunio-test campaign?

Artículos relacionados

  • How do I keep test and production data apart?

    Do my tests distort the reports?

    Metrunio keeps them apart itself, so your tests do not distort the reports: every event from the assistant and the live test carries the environment “test” and is excluded from standard reports. In “Setup” you delete all test data with “Reset test data”; first it shows you what will disappear.

  • No data after setup? Check these six points

    No data arrives after installation. What do I check?

    First: is the data processing agreement concluded? Without it Metrunio accepts nothing, and the portal shows “Measurement paused: DPA missing.”. If it is concluded, the GTM container is usually not published, consent is missing or the domain is not in the allowed list; these six steps cover the most common causes.

  • What does the setup health centre do?

    How do I find out what is missing in my setup?

    The health centre runs a diagnosis across your setup and reports every finding with cause, effect, error code and the steps to fix it, rather than just an error message.

  • 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 then metrunio.goal('key') per step; from the backend with POST /v1/server/events and an event of type goal carrying goal_key and user_id. Both routes are equivalent; a step without a customer identifier is rejected.

Mira lo que cuentan tus datos.

Echa un vistazo primero a la demo. Por ahora, solo hay cuenta propia con invitación.

Abrir la demoSolicitar acceso