How does Metrunio take the decision from my consent tool?

Analytics means: visits, basket and purchase may be measured and linked. Marketing adds ad contacts and the report back to advertising platforms. The bridge reports both separately.

Adding it

If you choose a tool from the table in the consent step of the portal, the line is already in the installation code. By hand it looks like this, right after the Metrunio code:

<script async src="https://YOUR-MEASUREMENT-ADDRESS/v1/consent-bridge.js" data-source="usercentrics" data-cookieconsent="ignore" data-uc-allowed="true" data-cmp-ab="1" data-ot-ignore consent-skip-blocker="1"></script>

If your service, purpose or category has a different name, name it yourself: data-analytics="Web analytics" data-marketing="Advertising". Separate several names with commas; each of them must be granted. Separate spellings of the same entry with a vertical bar, such as “Messung|Measurement”. The bridge finds an entry by its ID or its name, regardless of upper and lower case.

In a tag manager, set window.metrunioConsentBridgeConfig = { source: "usercentrics" } before loading, then load the same file. With data-source="auto" or no setting, the bridge looks for the tool itself: first the tools with their own interface, then the Shopware cookie manager, then the WP Consent API, and last TCF and Google Consent Mode.

Notes on individual tools

• OneTrust: the bridge looks for the groups of the standard template, C0002 and C0004, and also recognises the IDs of older accounts, 2 and 4. You do not need to enter anything for this. If your account lists both IDs as separate groups, a direction only counts as granted when both are granted. If your groups have entirely different IDs, enter their ID or their name, such as data-analytics="Performance Cookies".
• Complianz: if Complianz enables statistics without consent (statistics set up as privacy friendly), Metrunio does not measure statistics there, because nobody chose. Set Complianz to require consent for statistics.
• Real Cookie Banner and Borlabs Cookie ask per service. Add a service “Metrunio” with the unique name or ID metrunio, plus metrunio-marketing for marketing.
• The bridge reads Borlabs Cookie according to the vendor’s documentation. Use the consent check below to see whether your choice arrives.
• WP Consent API: choose it only if your tool is not in the table, such as WPConsent. Complianz and CookieYes serve it as well, but CookieYes writes its defaults there before any choice; so choose the tool itself.

What the bridge does not do

• It never assumes consent. As long as the banner reports no decision, Metrunio sends nothing.
• If it cannot find a service, purpose or category in the tool, that direction counts as refused. So add Metrunio to your tool.
• Consent that arises without a click does not count: implicit consent from Usercentrics and Cookiebot, the Google Consent Mode default (“consent default”), a TCF response saying the GDPR does not apply, OneTrust templates without consent, the Country Bypass of Real Cookie Banner and categories a tool enables by itself.
• With TCF, the purposes your tool collects for your own website (publisher purposes) count, not the consents for vendors. Set them up in your tool, otherwise Metrunio does not measure.
• If it cannot find the tool for ten seconds, it writes a warning to the browser console and keeps looking, less often, until a minute has passed since loading. In the portal this shows as “no events”.

Automatic blocking

Some tools hold back third-party scripts until consent. If they held back Metrunio, the page views before the choice and a later withdrawal would be lost. The installation code therefore carries the exemptions these tools know on its script tags: data-cookieconsent="ignore" (Cookiebot), data-uc-allowed="true" (Usercentrics), data-cmp-ab="1" (consentmanager), data-ot-ignore (OneTrust) and consent-skip-blocker="1" (Real Cookie Banner). The script then loads right away, but until the choice in the banner it stores nothing on the device and sends no events.

Complianz and CookieYes know no such exemption. Complianz only blocks Metrunio if you add it in the Script Center; then allow the measurement address and metrunio.init (whitelist). CookieYes only holds back the script if a cookie entry carries an address pattern of the measurement address and the installation code comes after the CookieYes script. Leave the pattern empty and place the installation code high up in the head of the page.

Checking it

Open your website with ?metrunio-consent-check=1 at the end of the address, for example https://your-shop.com/?metrunio-consent-check=1. The bridge then shows a small panel at the top right: which tool is configured and which one is detected, which services or categories it looks for, whether your tool knows them and which decision is present. Only you see the panel, it sends nothing, and it updates as soon as you choose in the banner.

The browser console shows the same under metrunioConsentBridge.status(). In the portal, the live test shows the page views with their consent status; withdraw consent and the next view is missing.