Qualité des données et dépannage

• 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.

• 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.

• 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.

• How do ad blockers affect measurement?

  Do I lose data to ad blockers and browser protections?

  Ad blockers and browser protections cost part of the browser signals, as with any client-side measurement. Metrunio does not circumvent these protections. Conversions can instead be reported server-side, where the browser plays no part.

• Are bots filtered out?

  Do automated requests distort my numbers?

  Obvious bots are detected through a user-agent heuristic and excluded. That is not full bot management.

Vers le centre d'aide