---
title: "Adobe Experience Platform"
description: "Send consent to the Adobe Web SDK (alloy) for collection and marketing preferences."
url: "https://cookiebeam.com/docs/integrations/adobe-experience-platform"
lang: "en"
---

# Adobe Experience Platform

Send consent to the Adobe Web SDK (alloy) for collection and marketing preferences.

**What it does.** Passes consent to the Adobe Experience Platform Web SDK so Adobe applies it across the products behind it.

**Consent category.** `analytics` for collection, `marketing` for marketing preferences.

## How it works

Adobe's SDK takes a structured consent payload rather than a single flag:

```js
alloy('setConsent', {
  consent: [{
    standard: 'Adobe',
    version: '2.0',
    value: {
      collect: { val: 'y' },
      marketing: { preferred: 'y' }
    }
  }]
});
```

`collect` reflects the analytics category and `marketing` reflects the marketing category. Each is `y` or `n`.

Like Pardot, calls that arrive before `alloy` is a function are queued, and only the latest queued payload is replayed once the SDK is available.

## Setup

On by default. Toggle it under **Vendor Consent Signals**, then publish.

Your Adobe datastream needs to be configured to honour the Adobe 2.0 consent standard. If it's set to ignore consent, the call goes through and changes nothing on Adobe's side.

## Testing

Confirm the SDK is loaded:

```js
typeof window.alloy
```

Then make a choice and check the network request to your Adobe edge endpoint. The consent payload rides in the request body, so you can confirm `collect` and `marketing` match what the visitor chose.