Les articles d'aide existent en allemand et en anglais. Vous les lisez ici en anglais.
Protection des données et sécurité
Additional instruction for revenue reconciliation
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.
When do orders count after a refusal in the cookie banner?
Revenue reconciliation is a purpose of its own, separate from tracking: purchases and refunds your server reports without consent count towards measured revenue, so that your totals match your shop and a refund finds its purchase. Metrunio stores the order number, the type of transaction (order, subscription renewal or refund), amount, currency and the day of the order. Browser, customer and advertising identifiers, the subscription ID, line items, page and campaign are removed before storing. That does not make the data anonymous: your shop can link the order number to a person, and the order number stays as the necessary order key.
What the instruction changes
| Case | Without the instruction | With the instruction activated |
|---|---|---|
| Server order without a decision in the banner (unknown) | counts for revenue reconciliation | counts for revenue reconciliation |
| Server order after a refusal (denied, or partial without analytics) | rejected (CONSENT_MISSING), nothing stored; notice in the setup check | counts for revenue reconciliation, not attributed |
| Purchase from the file import with consent_state denied | rejected on import, with the reason | counts for revenue reconciliation |
| Order from the browser after a refusal | rejected | rejected |
A refusal is not turned into consent: the order is never linked to a visit, never attributed to a channel and never reported to an advertising platform. Activating the instruction does not bring back orders that were rejected earlier.
How to activate it
- 01Request the template of the additional instruction from support@metrunio.com.
- 02Fill in the mandatory details: sources, order key, retention period, legal basis and how buyers can object. Record your balancing of interests, including for the case of a refusal.
- 03Add to your privacy policy. A text block is in the article “Privacy policy text block: revenue reconciliation”.
- 04Send the instruction back signed. We activate it and tell you the version and the time; your account’s change log shows “Additional instruction for revenue reconciliation activated”.
- 05From that moment on, orders after a refusal count. If you want to end this, revoke the instruction in the portal under “Privacy → Additional instructions”: Metrunio then rejects such orders again within ten seconds at the latest.
In the step “Conclude the data processing agreement”, this additional instruction is listed with what it needs, but without a checkbox: a checkbox alone does not replace the details on sources, order key, retention period, legal basis, balancing of interests and how to object. It still only becomes active once we have the completed template.
Note
The additional instruction extends revenue reconciliation to orders after a refusal and requires it. If you switch revenue reconciliation off in the portal under Privacy, the instruction is paused as well until you switch it back on.
Refusal, withdrawal and objection
- Refusal in the banner: it concerns tracking and is not an objection to revenue reconciliation. With the instruction activated, the order counts, without any link to the visit.
- Withdrawal of consent: Metrunio deletes what rested on the consent, including an order your shop reported with this browser’s identifier. It is not moved into revenue reconciliation. Orders reported without consent stay.
- Objection to revenue reconciliation: if a buyer contacts you, create a request of type “Objection” under “Privacy” with the order number as the identifier and execute it. Metrunio deletes the order including its refunds and puts the order number on the suppression list. Intake then rejects new reports of this order (SUBJECT_SUPPRESSED), including from the import.
Legal note
Whether revenue reconciliation after an explicit refusal of tracking can rest on your legitimate interest is for your own balancing of interests to decide. The instruction does not create a legal basis towards your buyers. The balancing of interests, the information in your privacy policy and the way to object are your responsibility as controller; settle them with your privacy counsel.
Dernière vérification le 16 oct. 2026
Dans le portail client
Également demandé
- Revoke the revenue reconciliation instruction
- Why are orders missing after a refusal?
- How do I activate the additional instruction?
- CONSENT_MISSING for an order with denied
- What is revenue reconciliation?
- Is a refusal in the banner an objection?
- A buyer objects to revenue reconciliation. What do I do?
- Delete and block an order number
- Shopware plugin: orders missing after a refusal
- Are orders without consent anonymous?
Articles connexes
- Privacy policy text block: revenue reconciliation
What does my privacy policy need to say about revenue reconciliation?
Your privacy policy must name revenue reconciliation as a purpose of its own alongside tracking, with the legal basis (legitimate interest under Art. 6(1)(f) GDPR), the data, Metrunio as processor, the retention period and how to object. Metrunio’s privacy policy does not inform your buyers. The block below is a draft for you to adapt.
- 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.
- How do I handle access, deletion and objection?
A data subject exercises their rights. What do I do?
Privacy requests are handled in the portal under “Privacy”, not by ticket. Every request is recorded and logged in the change log; the data subject is located through a pseudonymous identifier.
- Does a deletion take lasting effect?
Does a deleted person’s data come back on their next visit?
It lasts: a deleted person’s data does not come back on their next visit. Deletion and objection put the identifiers concerned on a suppression list; only a hash of them is stored, which is still pseudonymous personal data and is read for nothing but enforcing the suppression. The collector rejects events from suppressed persons before anything is stored.
- Where is the data processed?
Is there a data processing agreement, and where are the servers?
Application, database and analytics storage are planned for the europe-west3 region (Frankfurt); what goes beyond that, such as logs and support access at the cloud provider, is listed in the sub-processor list under “Documents”. You conclude the data processing agreement with us in the portal under “Privacy” or in the Shopify app; nothing is measured before that. We have our own agreements with our sub-processors.