Adobe Experience Platform Tags

Adobe Experience Platform Tags is a tag management system that fires tags based on rules you author. When you publish DataGrail Consent to an Adobe property, DataGrail adds a data element for each of your consent categories. Each element answers granted or denied for that category, so you can gate any rule on consent by adding a single condition to it.

Formerly Adobe Launch

Adobe Experience Platform Tags was previously known as Adobe Launch. If you are searching for Adobe Launch, you are in the right place.

Adobe has no per-tag consent field, so gating happens through a rule condition rather than a setting on the tag itself. You add the condition to your own rules — DataGrail never modifies the rules you author.

Prerequisites

Before you can gate rules on consent, confirm the following:

• You have connected Adobe Experience Platform Tags to DataGrail.
• You have added the Adobe property as a container in Consent Management > Settings > Containers.
• You have published DataGrail Consent to that property at least once.
• You have edit permissions on the Adobe property.

Available Data Elements

Every publish creates or updates one data element per consent category, named after the category's key. The elements DataGrail creates for the default categories are listed below.

Data Element	Category	Returns
DG Consent - Category dg-category-essential	Essential	granted — essential categories cannot be switched off
DG Consent - Category dg-category-performance	Performance	granted or denied
DG Consent - Category dg-category-functional	Functional	granted or denied
DG Consent - Category dg-category-marketing	Marketing	granted or denied

If you have created your own categories, each one gets an element too, following the same DG Consent - Category dg-category-<name> pattern. DataGrail also publishes DG Consent - GPC Signal and DG Consent - DNT Signal, which report the browser-level Global Privacy Control and Do Not Track signals.

Do Not Rename These Elements

DataGrail matches these elements by name on every publish. If you rename one, the next publish creates a second element under the original name and your condition keeps reading the renamed copy, which no longer updates.

Gate a Rule on Consent

Add a Value Comparison condition to any rule that should only fire with consent. The condition references the data element with percent signs, which is how Adobe resolves a data element inside a rule.

1. In Adobe Experience Platform Tags, open your property and navigate to Rules.
2. Select the rule you want to gate, or select Add Rule to create one.
3. Under Conditions, select Add.
4. Set Extension to Core and Condition Type to Value Comparison.
5. In the Left operand field, enter the data element name wrapped in percent signs — for example, %DG Consent - Category dg-category-marketing%.
6. Set the operator to Equals.
7. In the Right operand field, enter granted.
8. Select Keep Changes, then Save the rule.

The rule now fires only when the visitor has granted consent for that category. Categorize the tag in DataGrail as well, so your reporting and consent records match what the property actually enforces.

Publish the Rule

Conditions you add in Adobe are not live until you build them through your own library. Adobe requires a library to move through Development, Staging, and Production in order, so a change published to development is not yet enforced in production.

1. In Adobe Experience Platform Tags, navigate to Publishing Flow.
2. Add your modified rule to a library.
3. Build the library and promote it through each environment to production.

When you publish DataGrail Consent from the publish window, you choose the starting environment and, optionally, a stage to promote to. The data elements reach whichever stage you select.

Multiple Categories on One Rule

A rule with several conditions requires all of them to pass. To fire a tag when any of several categories is granted, use one condition with a custom code condition instead of stacking Value Comparison conditions.

Custom code condition for multiple categories

Set the condition type to Custom Code and return true when any of the categories you care about is granted:

return _satellite.getVar('DG Consent - Category dg-category-marketing') === 'granted'
    || _satellite.getVar('DG Consent - Category dg-category-performance') === 'granted';

Behavior Before a Choice Is Made

Each element reports your configured default for its category until the visitor makes a choice, which is the same answer the banner itself acts on. Under an opt-in configuration the default is denied, so gated rules do not fire until consent is granted. Under an opt-out configuration the default is granted.

The element fails closed. If the banner cannot load at all, every category except essential returns denied, so a gated rule is blocked rather than fired without a consent record.

Consent Changes Mid-Page

The element re-reads consent on every evaluation rather than caching it for the page, so a rule evaluated after the visitor changes their preferences sees the new answer. Rules that already fired are not undone — Adobe has no mechanism to retract a tag that has executed. For tags that must stop collecting immediately, pair the condition with a callback that tells the vendor about the change.

Web SDK Customers

If your property uses the Adobe Web SDK, DataGrail also sends consent to Adobe directly through setConsent, which covers Adobe's own products. The data elements complement that rather than replacing it: they reach the tags setConsent cannot, such as rules that fire legacy AppMeasurement or third-party pixels in custom code.

Troubleshooting

If a gated rule does not behave as expected, review the following.

The condition never passes

Confirm the data element name in your condition matches the element in the property exactly, including the dg-category- prefix and the spaces around the dashes. In Adobe, navigate to Data Elements and copy the name directly. A name that does not resolve returns the element's default value of denied, so the rule never fires.

The condition always passes

Check whether the category is essential. Essential categories cannot be switched off, so their element always returns granted. Also confirm your policy uses an opt-in configuration if you expect the rule to be blocked before the visitor decides — under an opt-out configuration the default is granted.

A duplicate data element appeared

DataGrail matches its elements by name. If an element was renamed or deleted, the next publish creates a new one under the original name. Delete the copy you are not referencing and point your conditions at the element DataGrail maintains.

The rule fires in development but not production

Your library has not been promoted all the way through. Adobe requires each library to pass through development and staging before production. Check Publishing Flow to confirm the library containing both your rule and the DataGrail data elements reached the production environment.

DataGrail Privacy Inspector

Install the DataGrail Privacy Inspector Chrome extension to confirm a gated tag does not load until consent is granted.