Los artículos de ayuda existen en alemán e inglés. Aquí los lees en inglés.
Protección de datos y seguridad
Privacy policy text block: measurement and web analytics
Your privacy policy describes measurement with Metrunio in a section of its own: the purposes including web analytics, the data processed, consent as the legal basis, Metrunio as processor, the retention period and withdrawal. The block below is a draft with placeholders. Add the modules for the country view, post-purchase question, forms, conversions sent back to ad platforms and the data assistant only if you use them.
What does my privacy policy need to say about measurement with Metrunio?
Your visitors read your privacy policy, not Metrunio’s. The block describes what Metrunio measures for you with their consent, web analytics included. Fill in the details in square brackets. The German version addresses visitors formally, as is usual in privacy policies.
The core text
Measurement and web analytics with Metrunio. With your consent we use Metrunio, a service of Kokolorum GmbH, Industriering Ost 66, 47906 Kempen, Germany. We use it to analyse how our website is used and which visits and advertising contacts precede an order or enquiry. This includes page views, visits and page sequences as well as the time during which a page is shown in a visible browser tab. This time does not prove that you actually read the page. We attribute revenue to the preceding contacts according to a defined calculation model.
We process pseudonymous browser and session identifiers, times and events, cleaned page addresses, source and campaign details, browser, device and operating system families and, for reported orders or enquiries, the necessary transaction identifiers, values and currencies. Individual click and impression identifiers for advertising purposes are only processed if you have given the corresponding marketing consent. IP addresses are processed during technical transmission and to limit requests, but are not stored in the event records.
With your consent, the measurement script uses storage in your browser to assign visits and events and to transmit reports that are already permitted. The entries used and their lifetimes can be found at [direct link to our current storage table]. Consent to measurement is voluntary. The legal bases are Art. 6(1)(a) GDPR and, for storing and reading information on your device that requires consent, Section 25(1) TDDDG.
Kokolorum processes this data on our behalf. The main processing takes place at Google Cloud in Frankfurt. Service providers used may also process or access data outside the European Economic Area. Details of recipients and countries, the transfer mechanisms used in each case and how to obtain a copy of the safeguards can be found at [specific section of this privacy policy].
We keep personal measurement data for [actually configured and justified number of] days. After a withdrawal we end the measurement based on it and have the attributable data deleted, unless a separate legal basis requires its limited retention. You can change or withdraw your decision at any time via [directly accessible consent settings]. The lawfulness of processing up to the withdrawal remains unaffected. A withdrawal in the banner initially applies to the browser used; for requests across devices and your other rights, contact us at [privacy contact]. For remaining records of consent and withdrawal, the periods stated in [section] apply.
What you adapt
- The link to your storage table, with the entries and lifetimes that actually occur on your website. Which entries Metrunio uses is listed in the article “Do I need a cookie banner for Metrunio?”.
- The retention period as it is configured and justified for your website. Do not copy a number from another text if your setting is different.
- The references to your sections on recipients and countries, transfer mechanisms and records of consent. These sections must exist in your privacy policy.
- The consent settings and your privacy contact. Rights, controller and, where applicable, data protection officer belong in the full privacy policy of your shop.
Modules, if you use them
Country: If we use the country view, the country is derived from your IP address when the measurement arrives, using a locally operated database, and assigned to the pseudonymous visit. Your IP address is not transmitted to the provider of the database for this. The country code is stored; VPNs and similar services can affect the assignment.
Post-purchase question: With your analytics consent we may ask you after a purchase how you heard about us. Your voluntary answer is linked to the order and the pseudonymous visit history. It is therefore not an anonymous survey. The answer is not transmitted to advertising platforms and is subject to the retention periods of the measurement data.
Forms and CRM: With your analytics consent we add source and campaign details and an enquiry identifier to our forms. These details reach our system [specific CRM] together with your enquiry. Using the enquiry identifier, we can attribute a later deal to the preceding visit. We only use platform click identifiers for this with the corresponding marketing consent. The data in our CRM is subject to [its purposes and retention periods].
Conversions sent to advertising platforms: With your corresponding marketing consent we transmit details of completed transactions via Metrunio to [specific platforms and legal entities]. Per platform these include [actual fields]. Purpose, roles, further processing, transfers to third countries and withdrawal are described in the section [direct reference].
AI analysis and additional recipients: Where we use the data assistant, selected analysis data may reach the service used for it, Google Cloud Vertex AI. [Describe actual scope, safeguards, storage handling and third-country reference.] Tools and report recipients we connect in addition are named separately in [section]. These data flows are not anonymous merely because names are missing.
For revenue reconciliation without consent and attribution through the checkout, write sections of their own that match how you set them up; for revenue reconciliation there is the article “Privacy policy text block: revenue reconciliation”. If you measure seen ads (post-view), describe the ad placements included and the matching marketing purpose.
And your cookie banner?
The privacy policy informs; your banner obtains the consent. Its purpose has to name web analytics: use of the website, page views and visits, and time with the tab visible. If your text has so far only named advertising success, consent given with it does not cover web analytics. Add the purpose and obtain consent again, for example by raising the version of your banner. A note in your privacy policy does not extend consent that has already been given.
Legal note
The block is a draft and does not replace a review of your privacy policy. Whether it fits your shop, your settings and your other services is something to settle with your privacy counsel.
Revisado por última vez el 18 oct 2026
También se pregunta
- Shop privacy policy: Metrunio
- Privacy policy text block for web analytics
- Does web analytics belong in the privacy policy?
- Template privacy policy tracking
- What do I write about Metrunio in my privacy policy?
- Do I need to obtain consent again if I use web analytics?
Artículos relacionados
- 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.
- 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.
- What happens before consent?
Can I measure anonymously before consent?
The default is “block_all”: before consent the tracking script records, reads and sends nothing, and the page view is only created on consent. 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”.
- 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.
- Web analytics: page views, visits, time on site
What does web analytics in Metrunio show me?
Under “Web analytics” you see, on every plan, how many page views, visits and visitors your website has, how long visitors stay active and how many leave right away. You can view it per day or, for periods of up to 14 days, per hour, split by channel, page and technology. Only visitors who consented to analytics are counted; nothing is extrapolated.