---
slug: rechtsgrundlage
title: "Do I need a cookie banner for Metrunio?"
category: datenschutz
locale: en
updated: 2026-10-17
keywords: ["cookie banner","TDDDG","GDPR","ePrivacy","EDPB","legal basis","consent","privacy policy"]
questions: ["Do I need consent and an entry in the cookie banner for Metrunio?","Do I need a cookie banner?","What do I have to state about Metrunio in the cookie banner?","Does Metrunio have to be in the privacy policy?","TDDDG","Is this GDPR compliant?","ePrivacy"]
url: https://bench.metrunio.com/en/help/rechtsgrundlage
---

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

Metrunio is built so that consent-based measurement is the normal case: without consent an event is not stored, and the consent state is present per event and available for analysis. The exception is purchases and refunds your server reports without consent: without a decision in the banner and, only with an activated additional instruction, after a refusal. They are stored for revenue reconciliation without browser, customer or advertising identifiers; you can switch this off under Privacy.

## What you state in the cookie banner

- Service: Metrunio, a service of Kokolorum GmbH, Industriering Ost 66, 47906 Kempen, Germany. Metrunio processes the data on your behalf.
- Purpose: measuring which visits and ad contacts preceded an order or lead, and distributing the revenue across them by a rule.
- Category: the visitor ID needs consent to analytics (statistics), the view ID for seen ads consent to marketing. You map how the categories are called in your banner during setup.

| Name | Type and lifetime | Needs |
| --- | --- | --- |
| metrunio_anonymous_id | localStorage, no fixed expiry; removed on withdrawal | consent to analytics |
| metrunio_session | sessionStorage, until the tab is closed | consent to analytics |
| metrunio_queue | localStorage, until the waiting events have arrived | a decision in the banner |
| metrunio_consent_pending | localStorage, until the decision has been reported | a decision in the banner |
| metrunio_view | cookie of the measurement address, 30 days | consent to marketing |
| metrunio_aid | cookie on your domain, 13 months (Safari seven days), only with your own measurement domain; valid on all subdomains | consent to analytics |

What each entry is for, and what else Metrunio stores, is in “Which data is stored?”. For revenue reconciliation there is a separate building block for your privacy policy.

EDPB Guidelines 2/2023 address tracking pixels and tracking links under the same ePrivacy rules; they therefore also cover impression pixels and click redirects.

> **Legal note:** We are preparing a building block “Measurement with Metrunio” for your privacy policy; until then, use the details above and agree your text with your data protection adviser.

> **Legal note:** This description is no substitute for legal advice. The legal notice, privacy policy and consent concept of your website are for you to review with your own legal adviser; the legal basis per signal and purpose must be documented.

## Also asked

- Do I need a cookie banner?
- What do I have to state about Metrunio in the cookie banner?
- Does Metrunio have to be in the privacy policy?
- TDDDG
- Is this GDPR compliant?
- ePrivacy

## Related

- https://bench.metrunio.com/en/help/consent-grundsatz
- https://bench.metrunio.com/en/help/was-wird-gespeichert
- https://bench.metrunio.com/en/help/consent-tool-verbinden
- https://bench.metrunio.com/en/help/auftragsverarbeitung
- https://bench.metrunio.com/en/help/datenschutzerklaerung-umsatzabstimmung