Les articles d'aide existent en allemand et en anglais. Vous les lisez ici en anglais.
Consentement
What happens without consent?
By default, Metrunio stores nothing without matching consent, not even a raw event, and the tracking script sends nothing before a decision. One documented case differs: purchases and refunds your server reports without consent count towards measured revenue for revenue reconciliation, with their order number and without browser, customer or advertising identifiers, and are not attributed. After a refusal this only applies with an activated additional instruction. Without consent on the ad side, the click redirect passes on only the campaign, no click ID.
Is nothing really stored without consent?
| Purpose | Events concerned |
|---|---|
| Analytics | session_start, page_view, product_view, add_to_cart, form_submit, lead, purchase, refund, custom, goal, survey |
| Marketing | ad_impression, ad_viewable_impression, ad_click, email_open |
The check happens twice: the SDK does not even send advertising events without marketing consent, and the collector checks the reported state a second time. What is rejected is not stored, not even as raw data for a later evaluation.
One case that differs, and the click redirect
- Purchases and refunds that arrive through the server API or the historical import without a consent decision (consent_state unknown) are stored for revenue reconciliation: with their order number, without browser, customer or advertising identifiers. They appear as unattributed with the reason “No consent”. They are still personal data, because your shop can link the order number to a person. After a refusal (denied) the same only applies if the additional instruction for revenue reconciliation is activated for your account; otherwise the order is rejected. Details in the article on consent for server events.
- The redirect of a tracking link measures the click only with consent on the ad side (c=1), and only then passes on a click ID (metrunio_cid). Without it, it still redirects and appends only the campaign (metrunio_camp), the same for every click. The visit then counts for the campaign without being linked to a click. A visit is linked to the click, the impression and viewability only with marketing consent in your shop. Whether appending the campaign without consent is permissible has not yet been conclusively assessed.
Not an exception, but for completeness: every time a tracking element is loaded, a counter on that element goes up, together with the time of the last request. This happens without consent too. No identifier, no address and no per-request time is attached to it; it only tells you whether an element is being served. Anonymous reach measurement before consent has been hidden since 29 September 2026.
What happens in which state
| State | Events from the browser | Ad contacts (pixel, tag, click) | Purchases and refunds from the server |
|---|---|---|---|
| No decision yet | The script sends nothing, nothing sits on the device. | Measured only with consent on the ad side (c=1); nothing links them to the shop yet. | With unknown: stored with the order number, without browser, customer or advertising identifiers, counted in revenue, not attributed. |
| Refused | Nothing; anything held back is discarded. | As before a decision: no link to the browser is created. | With denied: as with unknown only with an activated additional instruction; without it rejected (CONSENT_MISSING), nothing stored. |
| Consented | Measured, with identifier, journey and attribution. | Linked to the browser through the click ID and the view identifier; the view identifier only with marketing consent. | With granted or a matching partial: measured and attributed like a purchase in the browser. |
| Withdrawn | Whatever the new state no longer covers is deleted; the script removes its identifier and session. | Those linked to this browser: deleted; the metrunio_view cookie is removed. All others stay. | Reported with this browser’s identifier: deleted, not moved into revenue reconciliation. Reported without consent (no decision or after a refusal): untouched. |
| Consented again | New identifier, new journey. | The old contacts no longer exist; the old destination URL brings nothing back either. | As for “consented”. |
Legal note
Metrunio does not replace consent management. You still need a CMP that collects and documents consent. Settle the specific arrangement for the two differing cases and the ad contacts after a withdrawal with your privacy counsel. For revenue reconciliation, your own privacy policy must state the purpose, the legal basis and how to object.
Dernière vérification le 13 oct. 2026
Également demandé
- Does Metrunio need a cookie banner?
- What happens when a user declines?
- Do you store data without consent?
- Which exceptions apply without consent?
- What applies before a decision, after refusal, consent and withdrawal?
- Are ad contacts measured without consent?
Articles connexes
- What happens before consent?
Can I measure anonymously before consent?
The default is “block_all”: nothing is stored before consent, and the tracking script sends nothing. Anonymous reach measurement before consent has been hidden since 29 September 2026 and can no longer be selected: the script sends nothing before a decision anyway, so it would stay empty. If you had already enabled it, earlier figures remain visible under “Reach”.
- Does consent apply to server events too?
Do I need consent when I send server-side?
Yes, because server-side processing does not mean exemption from consent: pass consent_state and consent_purposes in the event; without matching consent an event is rejected. The exception is purchases and refunds with consent_state unknown: they are stored for revenue reconciliation, with their order number and without browser, customer or advertising identifiers, count towards measured revenue and appear as not attributed with the reason “No consent”. With denied this only applies if the additional instruction for revenue reconciliation is activated for your account. You can switch revenue reconciliation off in the portal under Privacy; such an order can only be attributed via the checkout, if you switch that on.
- What happens when consent is withdrawn?
A visitor withdraws consent. What happens to the data?
From the moment of withdrawal nothing more is stored, and queued reports to advertising platforms no longer go out. Metrunio then automatically deletes what that browser reported under the withdrawn purpose, usually within a few minutes, and you do not need to create a request. Metrunio also deletes ad contacts from pixel, tag and click redirect that are linked to this browser; all other ad contacts stay.
- Which data is stored?
What exactly does Metrunio hold about my website’s visitors?
Pseudonymous identifiers, event data with timestamps, campaign and click identifiers, and conversion values. No raw IP addresses; event fields are not meant to hold plain-text names or contact details. Detected email addresses and phone numbers cause rejection; the automatic check does not detect every kind of personal data, though.
- Additional instruction for revenue reconciliation
When do orders count after a refusal in the cookie banner?
Orders your shop reports server-side after a refusal in the banner only count if the additional instruction for revenue reconciliation is activated for your account. You fill it in and sign it, and then we activate it; without it Metrunio rejects such orders. Orders with no decision in the banner at all count even without the instruction.