How do I connect my consent tool?

1. 01Open “Setup” and the “Consent” area.
2. 02Select your consent tool; the standard categories are mapped automatically.
3. 03Adjust the mapping if you use your own category names.
4. 04Save under “Change the setting”; the rule check then shows six cases. Whether your website reports the decision correctly shows in the live test above it.

For every tool in the table except the generic CMP, the consent bridge takes the decision from your banner; the installation code contains it as soon as you have chosen the tool. Which services or categories it looks for is described in the article on the consent bridge. If you use another one, report the state yourself through metrunio.setConsent({ analytics, marketing }), as soon as your tool delivers a decision and again on every change.

For OneTrust, the table shows the IDs of the standard template. Older accounts list the same groups as 2 and 4. The consent bridge recognises those too, so there is nothing for you to change.

Marketing means the marketing category of your website, and in addition always marketing, ad_storage and advertising. This one rule applies in the script, when events are accepted and when conversions are reported back to advertising platforms. purpose_7 only counts when the decision comes from a TCF CMP through metrunio.useTcf(); choose the IAB TCF 2.2 preset for that. If you report your own IDs such as C0004 through setConsent, the installation code carries the category as marketingCategory. If you do not copy it again, add it to metrunio.init yourself, otherwise the debug panel shows marketing as not granted.

With TCF, analytics counts as granted when purpose 1 is granted together with purpose 8 or purpose 7. Purpose 1 alone is not enough: it allows storing on the device, but no measurement yet.

On WordPress, choose the tool itself if it is in the table, even if it also serves the WP Consent API. The WP Consent API is the fallback for tools without an entry of their own, such as WPConsent. A banner that only shows a notice and offers no choice is not a consent tool: nobody decides there, and Metrunio does not measure.

With the Shopify app you choose nothing here. The app reads the decision through Shopify’s Customer Privacy API, and the cookie banner Shopify itself offers is always connected to it; with Usercentrics, Consentmanager and Cookiebot it is the norm. The choice in this list applies to the embed code, not to the app (see “How do I set up Metrunio in Shopify?”).

IAB TCF 2.2

With a TCF CMP, call metrunio.useTcf() after loading. The tracking script then reads every decision from the CMP itself: purpose 1 (storing on the device) is required, purpose 8 stands for analytics, purpose 7 for marketing. Publisher consents count. Metrunio measures on your behalf, so your CMP must ask the person for publisher purposes; enabling them only in the CMP settings is not enough. If you list Metrunio as a vendor of its own in your CMP, pass its ID (metrunio.useTcf({ vendorId })); then purpose and vendor consent both count, and your restrictions for this vendor take precedence. Legitimate interest does not replace consent.