Les articles d'aide existent en allemand et en anglais. Vous les lisez ici en anglais.
Qualité des données et dépannage
What does the setup health centre do?
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 find out what is missing in my setup?
What is detected
- A missing data processing agreement, without which Metrunio accepts nothing (PROCESSING_AGREEMENT_MISSING).
- No website created, no events in the past 24 hours, or test events only.
- Events without any consent information, and events rejected for lack of matching consent.
- A high share of rejected events, and one finding per reason with its error code, for example for domains that are not allowed or plaintext personal data (DOMAIN_NOT_ALLOWED, PII_DETECTED).
- No conversion defined, and conversions without a preceding contact.
- Processing backlog in the queue.
- Events whose processing failed in the last seven days (FAILED_JOBS).
On the overview the diagnosis appears as a single line with the way here. A finding that prevents measurement, such as “no data in 24 hours”, stays there as a prominent box. The “Data status” page reads the same source: what appears here as failed processing is listed there under “Processing” as an open task.
Note
The rule in the product: every finding names cause, effect, error code and the steps to fix it. After reading a message you know what to do, and you find the matching help article in the same place.
Dernière vérification le 12 oct. 2026
Dans le portail client
Également demandé
- Run diagnostics
- What is the health check?
- Check my setup
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.
- What do the error codes mean?
The collector answers with a code. What does it mean?
Every rejection carries a code together with a title, explanation, data effect and resolution steps. This table lists all codes of the collector and of processing with their meaning.
- Why are my events rejected?
The collector does not accept events. How do I find the cause?
The collector response states a status per event and, on failure, the reason. Check that response first; “Data status” in the portal additionally summarises the reasons over the period.
- 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.