How do I add Metrunio as a service in my consent tool?

The consent bridge takes the decision from your banner and looks for an entry with a fixed name in your tool: “Metrunio” in Usercentrics and CCM19, the identifier metrunio in Borlabs Cookie and Real Cookie Banner. Tools that ask by category, such as Cookiebot, OneTrust, Complianz or CookieYes, do not need a separate service for the bridge; add Metrunio there anyway, so your visitors see what they agree to.

Why “Accept all” is not enough without the service

Usercentrics, CCM19, Borlabs Cookie and Real Cookie Banner ask per service. “Accept all” grants consent for every service listed in the tool, and only for those. Without “Metrunio” there is nothing the consent could apply to: the bridge does not find the service, reports consent as not granted, and Metrunio does not measure, not even after the click. The consent check shows this as “not found in the tool”.

Is “Metrunio” enough, or do I also need “Metrunio Marketing”?

• “Metrunio” (analytics) is enough for visits, page views, cart, orders or leads and their attribution to campaigns through UTM parameters and origin.
• You also need “Metrunio Marketing” if Metrunio is to link ads that were seen with later visits (post-view through the view identifier metrunio_view), if the click IDs of advertising platforms such as gclid or fbclid are to be kept, or if you report conversions back to advertising platforms. With analytics alone, Metrunio keeps only the source of a click ID.
• If someone agrees to analytics only, Metrunio still measures, just without these parts.

Usercentrics

1. 01In the Usercentrics admin interface, open your settings (Settings-ID) and then “Service Settings”.
2. 02If “Categories” has no category for analytics yet, create one, for example “Analytics”. Usercentrics only comes with “Essential”, “Functional” and “Marketing”; Metrunio does not belong in “Essential”.
3. 03Go to “Data Processing Services” and create your own service with “Create Service”. Enter exactly Metrunio as the “Service Name” and choose the analytics category.
4. 04Fill in the fields from the table below and save with “Save DPS”. Only then does the “Storage” tab appear, with cookie duration, Non-Cookie Storage and Stored Information.
5. 05If you need marketing, add “Metrunio Marketing” the same way in the “Marketing” category.
6. 06Publish with “Save Draft” and “Publish”. Browsers keep the configuration for up to 30 minutes, and a new service can show the banner again to returning visitors.

Enter the cookie duration in days; Usercentrics does not take months. Without your own measurement domain, “Metrunio” sets no cookie, so 0. With your own measurement domain it is 395 days for metrunio_aid (Safari shortens it to 7 days), and for “Metrunio Marketing” 30 days for metrunio_view. “Non-Cookie Storage” is Yes for “Metrunio”, because Metrunio mainly uses localStorage and sessionStorage.

You fill in the category, “Retention Period Description”, “Cookie Policy URL” and “Opt-Out URL” yourself: the period is your setting in Metrunio under Settings › Raw data retention, the cookie policy URL is the address of your own storage table, and the opt-out URL stays empty because withdrawal works through your banner. “Data Transfer to Third Countries” and “Cookie Policy URL” may have other names in your version of Usercentrics; the content stays the same.

The storage entries

Name these entries in every tool that keeps a cookie or storage list. They are the same as in the article “Which data is stored?”.

CCM19

1. 01Open “Integrations & Cookies” and choose “Create New Entry”.
2. 02Name of the integration: Metrunio, purpose: Analytics/Statistics. The bridge looks for the integration under exactly this name.
3. 03For each language, fill in description, privacy link, data processed, purpose, legal basis and location of processing with the values from the table above, and add the storage entries to the cookie list.
4. 04Do not enter the installation code as the source code of the integration. It sits in the head of your page and waits for the decision by itself.
5. 05Save; the entry then appears in the banner. For marketing, add a second integration “Metrunio Marketing” with the purpose Ads.

Borlabs Cookie (version 3 and later)

1. 01In WordPress, open “Borlabs Cookie” › “Consent Management” › “Services”.
2. 02Add a new service in the Statistics group. Name: Metrunio, ID: metrunio. The bridge looks for exactly this ID.
3. 03Enter description, provider and the storage entries, and save with “Save Settings”.
4. 04For marketing, a second service “Metrunio Marketing” with the ID metrunio-marketing in the Marketing group.

Real Cookie Banner

1. 01In WordPress, open “Cookies”, the “Services (Cookies)” tab, and choose “Add service” › “Create from scratch”.
2. 02Name: Metrunio, group: Statistics, Unique Identifier: metrunio. The bridge looks for exactly this identifier.
3. 03Enter provider, purpose, the provider’s privacy policy, third countries and, under the technical cookie information, the storage entries. Real Cookie Banner takes the duration with a unit, for example 395 days.
4. 04Leave the opt-in code empty; the installation code already sits in the head of your page. Save.
5. 05For marketing, a second service “Metrunio Marketing” in the Marketing group with the unique identifier metrunio-marketing.

Cookiebot

Cookiebot asks by category. The bridge reads Statistics (statistics) for analytics and Marketing for marketing; it needs no service, and “Accept all” grants both categories. Add Metrunio to your cookie declaration anyway:

1. 01In the Cookiebot Manager, open the “Cookies” tab and choose “Add cookie”; in the new interface it is “Cookies & Reports” › “+ Add cookie / tracker”.
2. 02Add one entry per storage entry: name, category Statistics (metrunio_view: Marketing), type HTML5 Local storage for the page storage and HTTP for cookies, expiry according to the duration.
3. 03Save and start a new scan under “Cookies” (“Scan domain now”). Only then does the entry appear in the banner.

OneTrust

OneTrust asks by category. The bridge reads the group C0002 (Performance Cookies, 2 in older accounts) for analytics and C0004 (4 in older accounts) for marketing.

1. 01Open “Categorizations” and its “Cookies” tab.
2. 02Add the storage entries and assign them to C0002, metrunio_view to C0004.
3. 03Publish under “Scripts” with “Publish”, first to the test CDN, then to production. This is needed above all when a category is new on your domain.

Complianz

Complianz asks by category. The bridge reads Statistics (statistics) and Marketing.

1. 01In WordPress, open “Complianz” › “Wizard” › “Consent” and the step with services and cookies (Cookiedatabase.org).
2. 02Add Metrunio as a service. To edit a service the scan found, untick “Sync service with Cookiedatabase.org”.
3. 03Assign the storage entries to the Statistics purpose, metrunio_view to Marketing, and go on with “Continue”.
4. 04Set statistics to require consent. If Complianz releases statistics without consent, nobody has chosen, and Metrunio does not measure there.

consentmanager

consentmanager asks by purpose. The bridge reads the purpose “Measurement” (also Messung, Analytics or Statistics) and “Marketing” (also Advertising or Werbung).

1. 01Add Metrunio as your own vendor: in the “Cookies” menu, through the pen icon on an entry and “Add a new vendor”.
2. 02In the vendor list, assign the Measurement purpose with “+ Use”, and Marketing as well for marketing.
3. 03Add the storage entries with the type Measurement, metrunio_view with Marketing, and save your changes.

CookieYes

CookieYes asks by category. The bridge reads Analytics (analytics) and Advertisement (advertisement).

1. 01Open “Cookie Manager” › “Cookie List” and the Analytics category.
2. 02Add one entry per storage entry with “+Add Cookie”: the Cookie ID is the name, plus Domain, Duration and Description. metrunio_view belongs under Advertisement.
3. 03Leave “Script URL Pattern” empty, otherwise CookieYes holds back the Metrunio script.
4. 04Save with “Save Draft” and publish with “Publish changes”.

Other tools, Google Consent Mode and TCF

• WP Consent API (for example with WPConsent): the bridge reads the categories statistics and marketing. Add Metrunio as a service under Statistics in your tool, the way the tool provides for it.
• Shopware cookie manager: the Shopware plugin adds Metrunio itself, “Metrunio Messung” under Statistics and “Metrunio Werbemessung” under Marketing. You do not need to add anything.
• Google Consent Mode: you add nothing in Google. The bridge reads analytics_storage and ad_storage as set by your consent tool. Add Metrunio there as a service in the group that controls analytics_storage.
• IAB TCF: the publisher purposes 1 and 8 count, 1 and 7 for marketing. Set them up in your CMP and name Metrunio there as a service of your website.

Metrunio already has another name in your tool

If your tool lists Metrunio under another name, you do not need to rename it. Enter the existing name in the installation code: data-analytics="Web analytics" data-marketing="Advertising" on the script tag of the consent bridge, or in Tag Manager as analytics and marketing in window.metrunioConsentBridgeConfig.

Check

Open your website with ?metrunio-consent-check=1&metrunio-lang=en at the end of the address and choose “Accept all” in the banner. If the service shows “found, granted” under “Looking for”, everything is right. “not found in the tool” means the service is missing, has another name or has not been published yet. With Usercentrics this can take up to 30 minutes after publishing. metrunio-lang sets the language of the check, whatever language your page has.