Los artículos de ayuda existen en alemán e inglés. Aquí los lees en inglés.
Consentimiento
What happens 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”.
Can I measure anonymously before consent?
| Setting | Effect |
|---|---|
| block_all (default) | Nothing is stored. |
| analytics_only_after_consent | Analytics only after consent, marketing still blocked. |
| anonymous_analytics_pending_review | Anonymous reach measurement before consent, hidden since 29 September 2026. |
Note
Why it is hidden: before a decision, the tracking script sends nothing at all, page views included. Reach measurement only ever received figures through two paths on which the script broke that rule: at checkout and when the page was left. Both have been closed since 29 September 2026. We do not offer a setting that would then measure nothing. Sites that have it keep it until you change it; the description below applies to what was counted until then.
Two documented cases differ from the default, without the tracking script sending anything before a decision: orders your server reports without consent, and the click ID the click redirect appends to the destination URL. Both are described in the article “What happens without consent?”.
What reach measurement stores and what it does not
The fallback is a count, not a record. What is stored is when a view arrived, which page was read, and which channel and source it came from. Anything that would let two views be connected to one person is discarded before storage.
| Counted | Not stored |
|---|---|
| Page view and session start | Pseudonymous id, session id, customer id |
| Channel and source (organic search, Google) | Click and impression identifiers |
| Day and website | IP address, not even as a hash |
| Page path | Query string, free-form fields, cart lines |
- Purchases, leads, carts and form submissions are not stored without consent, not even anonymously.
- The counted views produce no journeys, no conversions and no revenue.
- The numbers appear in the portal under “Reach”, an area of their own, expressly separate from attribution. The attribution page shows only the total and a link to it.
- Once consent is in place the fallback no longer applies; after a refusal it does not either.
What sits in the browser before consent
Nothing. This is a separate question: section 25 TDDDG is not about what sits on our servers but about what is written to, or read from, your visitors’ devices, whether or not it identifies anyone. Before a decision the SDK writes neither the pseudonymous id nor the session id nor the queue, and it reads nothing either. The held-back events do carry a session id, but it lives in memory and only moves onto the device once consent is given. After a refusal it is discarded.
This holds for all three settings. Reach measurement does not touch the device either: it counts what the browser sends of its own accord and stores nothing there. Before the decision the SDK does not write a session id either; our tests check this in both browser stores.
Note
A subject access request under Article 15 cannot return these rows, and a deletion cannot find them: nothing is stored that would tie them to a person. That is the purpose of the setting and at the same time its limit.
Legal note
The third setting carries “pending review” in its name for a reason: it must be reviewed by privacy counsel before it is used. Whether section 25 TDDDG applies depends on the individual case; Metrunio does not make that decision for you.
Revisado por última vez el 15 oct 2026
También se pregunta
- Anonymous measurement without consent
- Cookieless tracking
- What is block_all?
- Is tracking without consent possible?
- What is measured without consent?
- Are cookies set before the banner?
- What is stored in the browser before consent?
- Do you use localStorage without consent?
Artículos relacionados
- What happens without consent?
Is nothing really stored 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.
- 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.
- Do I need a cookie banner for Metrunio?
Do I need consent and an entry in the cookie banner for Metrunio?
Yes: Metrunio measures visits and ad contacts only with consent, so it belongs in your cookie banner and your privacy policy together with its storage entries. Without consent it accepts at most purchases and refunds for revenue reconciliation, without browser, customer or advertising identifiers. The legal framework is Section 25 TDDDG: storing and reading information on a device generally requires consent.
- Are Google, Bing and others recognised automatically?
Do I have to set anything up at Google or Bing for the source to be recognised?
Automatically, with nothing to set up at Google or Bing. Metrunio reads the origin from what the browser sends anyway: the referrer and the platforms’ click identifiers (gclid, msclkid, fbclid, ttclid). Channel and source therefore appear in the report straight away. You only need to connect something if you also want campaign names and cost: that is what linking the ad account is for.