Les articles d'aide existent en allemand et en anglais. Vous les lisez ici en anglais.
Démarrage et compte
How long until data appears?
Individual events appear in the live test within seconds. Journeys and conversions are created during processing and usually appear within minutes; attribution shares are calculated afterwards.
When do I see the first numbers after installing?
| View | Typical delay |
|---|---|
| Live test in “Setup” | seconds |
| Raw events and event list | seconds |
| Journeys and touchpoints | minutes, depending on the queue |
| Conversions | minutes |
| Attribution shares and model comparison | after the next attribution run |
| Ad spend from the platform sync | every six hours, retroactively; the first fetch minutes after connecting |
Note
If a view stays empty permanently, delay is almost never the cause. If the portal shows “Measurement paused: DPA missing.”, the data processing agreement is missing: until it is concluded, Metrunio accepts nothing. Otherwise check “No data after setup? Check these six points” and the processing backlog under “Data status”.
Dernière vérification le 5 oct. 2026
Également demandé
- Why do I not see numbers yet?
- How fast is the data?
- Is there a delay?
Articles connexes
- 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.
- How do I conclude the data processing agreement?
How do I conclude the DPA with Metrunio, and why is nothing measured before?
For every account, measurement starts only once the data processing agreement (DPA) is concluded; until then Metrunio accepts nothing and stores nothing. You conclude it in the portal under “Privacy” or in the setup step “Conclude the DPA”, and for a Shopify store also right in the app: enter the company, its address and the person concluding it, confirm they are authorised, done. Data arrives a few seconds later, without any change to your installation.
- What does a processing backlog mean?
Events have arrived but journeys are not appearing. Why?
A queue sits between reception and reporting. When it grows faster than it is worked off, a backlog forms: raw events are already there, journeys and conversions are not yet. If processing an event fails for good, the portal reports it as FAILED_JOBS for seven days; support can replay it.
- When are attribution shares recalculated?
I changed the settings. Why do I still see the old numbers?
Attribution shares are produced in runs, not on every page load. After changing the model or windows, the new values apply from the next run; late-arriving contacts also change an already calculated journey.