CookieRay
Adobe Experience Platform with CookieRay Pro
CookieRay Pro can add the Adobe Experience Platform Web SDK (also known as Alloy) to your site and send it the visitor’s consent decision. You provide two IDs; CookieRay outputs the SDK code in the page head.
The card in the admin is labeled Adobe Analytics. What CookieRay loads is the Experience Platform Web SDK, configured with your Organization ID and Datastream ID.
Set it up
- Make sure your Pro license is active.
- Open CookieRay → Settings → Integrations.
- Switch on the Adobe card.
- Enter your Organization ID and your Datastream ID. Both are required.
- Click Save Integrations.
The SDK is output only when the card is switched on and both IDs are filled in.
How consent is handled
CookieRay configures the SDK with a default consent of pending. Events your site sends to the SDK are queued until the visitor decides, rather than being sent or discarded.
| Consent mode | What happens |
|---|---|
| Strict (Block Until Consent) | The SDK configuration stub is output straight away so alloy() calls queue safely. The SDK script itself is held back until the visitor grants analytical consent. |
| Log Only (Log Consent Only) | The SDK script loads asynchronously without waiting. The default is still pending until a decision is saved. |
When the visitor makes a choice, and on every later page load for a returning visitor, CookieRay calls alloy('setConsent', …) with the Adobe standard:
- Analytical allowed → consent value
in - Analytical not allowed → consent value
out
Where the IDs come from
Both IDs come from your Adobe account: the Organization ID is your Adobe IMS organization, and the Datastream ID is the datastream you created for your web property in Adobe Experience Platform Data Collection. CookieRay only stores the values you enter and does not contact Adobe from the admin.
Avoid loading the SDK twice
If your theme, a tag manager, or hard-coded code already adds the Web SDK, turn that off or leave this integration switched off. Two copies can load and send duplicate events.
Test it
- Open your site in a private window and the Network tab.
- In Strict mode, confirm the Adobe SDK script (
alloy.min.js) is not requested before you click the banner. - Click Accept All. The script loads and events begin to flow.
- Repeat with Decline All. In Strict mode the script should not load.
If the banner is hidden for a visitor’s country by Geo Targeting, or switched off, the SDK code is still printed but no consent decision is sent. In Strict mode the SDK never loads for those visitors. In Log Only mode it loads with consent left pending.