Consentimiento

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

• How do I connect my consent tool?

  Which consent tools behind my cookie banner are supported, and how do I map the categories?

  In “Setup” you select your consent tool, the tool behind your cookie banner; for the common systems the categories are pre-filled. Other CMPs and custom consent APIs can be mapped freely.

• How does Metrunio take the decision from my consent tool?

  Do I have to call metrunio.setConsent myself if I use Usercentrics, Cookiebot, Complianz, Borlabs Cookie, Real Cookie Banner or another common consent tool?

  Through the consent bridge, without you calling metrunio.setConsent yourself: for thirteen tools this small additional script reads the decision from your banner and passes it to Metrunio, including every later withdrawal. The installation code in the portal contains it as soon as you choose your tool in the consent step, and the Shopware plugin adds it by itself.

• How do I check my consent status?

  How do I make sure consent takes effect correctly?

  With two checks that show different things. The rule check under “Setup → Consent” runs six cases against your saved setting, without your website. Whether the website reports consent and withdrawal correctly only shows in the live test with real page views: for each signal the time, source and reported consent status.

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

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

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

Al centro de ayuda