Integrations (GTM, Meta Pixel, Adobe)

CookieRay Team
•
3 min read

Integrations: Google Tag Manager, Meta Pixel and Adobe

CookieRay Pro can add three marketing and analytics tools to your site and connect each one to the visitor’s consent choice. You enter IDs; CookieRay outputs the tag code in your page head. Find them under Settings → Integrations.

Step-by-step guides for each tool: Google Tag Manager, Meta Pixel, and Adobe Experience Platform. Something not loading? See Pro troubleshooting.

Setup

  1. Open Settings → Integrations.
  2. Switch on the tool you use and fill in the ID fields (below).
  3. Click Save Integrations.
ToolFields
Google Tag ManagerContainer ID (for example GTM-XXXXXXX)
Meta PixelPixel ID
AdobeOrganization ID and Datastream ID (both required)

The Adobe card is labeled Adobe Analytics in the admin. What CookieRay loads is the Adobe Experience Platform Web SDK.

An integration only outputs code when it is switched on and its ID fields are filled in.

These behaviors depend on your consent mode in Settings: Block Until Consent is called Strict here, and Log Consent Only is called Log Only.

Google Tag Manager

  • In Strict mode, CookieRay creates the dataLayer and holds back the GTM script until the visitor grants analytical consent.
  • In Log Only mode, GTM loads immediately.
  • When consent is saved, CookieRay pushes the consent state to the dataLayer.

Meta Pixel

  • The pixel starts with consent revoked before it initializes, so no tracking happens until the visitor grants marketing consent. CookieRay then grants or revokes consent in the pixel based on the visitor’s choice.

Adobe Experience Platform Web SDK

  • The SDK is configured with a “pending” default consent, so events queue until a decision is made.
  • In Strict mode, the SDK script is held back until analytical consent is granted.
  • CookieRay sends the visitor’s consent decision to the SDK.

Avoid duplicate tags

If you already add the same GTM container, Meta Pixel, or Adobe SDK another way (a theme, another plugin, or hard-coded), turn that off or don’t enable the CookieRay integration for it. Two copies can load twice.

Consent Mode v2 is a free feature and works independently. See Google Consent Mode v2 and the tutorial Set up Consent Mode v2 with GA4 and GTM.

Hidden countries and a disabled banner

The integration tags are printed by the Pro add-on, separately from the banner. They are still added to the page when the banner is hidden for a visitor’s country with Geo Targeting, and also when the banner is switched off. The consent signals come from the banner script, so in those cases they never arrive:

  • GTM: in Strict mode gtm.js never loads. In Log Only mode it loads, with no consent push.
  • Meta Pixel: the script loads but stays revoked, so it never tracks.
  • Adobe: in Strict mode the SDK never loads. In Log Only mode it loads with consent left pending.

So turn the banner on before you rely on these tags.

Without a license

Without a valid Pro license the Integrations settings show disabled Connect buttons, and CookieRay stops adding the tags to your pages.

Was this article helpful?

Your response is saved on this device.