Adobe Experience Platform Launch is a tag management system that enables your organization to deploy marketing and analytic tags on your properties. In this article, we will cover how to trigger a direct call to a rule configured in Adobe Experience Platform Launch when an end-user consents to a particular vendor.
- Prerequisites
- Configure Adobe Launch rule
- Configure Sourcepoint consent action/opt-in hook
- Test integration
Prerequisites
This article assumes that your organization already has the following implemented on a web property:
- Sourcepoint CMP campaign(s)
- Adobe Experience Platform Launch tags
Configure Adobe Launch rule
Navigate to the rules authoring section in the Adobe Launch platform and select an existing rule or create a new rule. Use the provided space to give your rule a name if it doesn't exist yet.
When finished, click + Add under the Events section.
Use the Event Type dropdown menu to select Direct Call. Add a unique direct call identifier in the provided identifier field.
Note: The unique direct call identifier will later be used within the Sourcepoint platform when configuring your consent action / opt-in hook.
Click Keep Changes when finished.
Next, click + Add under the Actions section to configure what action should be executed when your direct call event is triggered.
From the Action Configuration builder, select Custom Code from the Action Type dropdown menu. Use the provided space to enter the code snippet that should be executed. In our example, we will simply be logging a "Adobe Tag Fired" message to the browser console.
Click Keep Changes when finished.
Save your rule and publish the changes in accordance with your publishing flow.
Configure Sourcepoint consent action/opt-in hook
Instructions on how to configure a consent action/opt-in hook differs slightly by campaign type. Please select a tab below for more details for a specific campaign.
Navigate to the GDPR TCF or GDPR Standard vendor list associated with your property.
From the vendor list builder, select the purpose or vendor that when consented to will trigger your Adobe Launch rule.
From the subsequent modal, click the Consent Actions tab and use the Geolocation field to select the states/countries/regions that should be geo-targeted (i.e. only end-users from these states/countries/regions will trigger your Adobe Launch rule when they consent to the vendor or purpose).
Next, ensure the Custom JS tab is selected in the modal and add the following code snippet in the provided space. The snippet performs the following:
- Checks if the
_satellitefunction is available - If the function is available, call the
_satelliteevent using the track method - The code calls the direct call rule configured in Adobe Launch and logs a message to the browser console
if (typeof _satellite.track == 'function') {
console.log('Consent hook fired');
_satellite.track('cmpconsent'); // must match the identifier in Adobe Launch
} Click Apply changes to confirm your consent action configuration. Save your vendor list when finished.
Navigate to the U.S. Multi-State Privacy (GPP) or U.S. Multi-State Privacy (Standard) vendor list associated with your property.
Click Opt In/Out out Hooks tab on the navigation bar.
On the subsequent page, select whether you want your Adobe Launch rule to trigger when an end-user opts into a Vendor or Privacy Choice.
Click + Add Hook.
In the next modal select the specific vendor or privacy choice that when opted into will trigger your Adobe Launch rule.
Ensure that the Opt In Hooks tab is selected and use the Geolocation field to select the states/countries/regions that should be geo-targeted (i.e. only end-users from these states/countries/regions will trigger your Adobe Launch tags when they consent to the vendor or purpose).
Next, ensure the Custom JS tab is selected in the modal and add the following code snippet in the provided space. The snippet performs the following:
- Checks if the
_satellitefunction is available - If the function is available, call the
_satelliteevent using the track method - The code calls the direct call rule configured in Adobe Launch and logs a message to the browser console
if (typeof _satellite.track == 'function') {
console.log('Consent hook fired');
_satellite.track('cmpconsent'); // must match the identifier in Adobe Launch
} Click Apply changes to confirm your consent action configuration. Save your vendor list when finished.
Navigate to the Global Enterprise vendor list associated with your property.
Click Opt In/Out out Hooks tab on the navigation bar.
On the subsequent page, select whether you want your Adobe Launch rule to trigger when an end-user opts into a Vendor or Privacy Choice.
Click + Add Hook.
In the next modal select the specific vendor or privacy choice that when opted into will trigger your Adobe Launch rule.
Ensure that the Opt In Hooks tab is selected and use the Geolocation field to select the states/countries/regions that should be geo-targeted (i.e. only end-users from these states/countries/regions will trigger your Adobe Launch tags when they consent to the vendor or purpose).
Next, ensure the Custom JS tab is selected in the modal and add the following code snippet in the provided space. The snippet performs the following:
- Checks if the
_satellitefunction is available - If the function is available, call the
_satelliteevent using the track method - The code calls the direct call rule configured in Adobe Launch and logs a message to the browser console
if (typeof _satellite.track == 'function') {
console.log('Consent hook fired');
_satellite.track('cmpconsent'); // must match the identifier in Adobe Launch
} Click Apply changes to confirm your consent action configuration. Save your vendor list when finished.
Test integration
Navigate to the web property that has the Sourcepoint CMP implementation code and Adobe Launch tags implemented.
Refresh the page (or resurface the privacy manager) to consent/opt-into the vendor or purpose that will trigger your Adobe Launch rule. Click Save & Exit when finished.
Navigate to the browser console and confirm that the consent hook has fired and that the custom code you configured in the Adobe Launch rule has fired. In our example, the browser console should log:
- Consent hook fired (console log from the consent hook configuration)
- Adobe Tag Fired (console log from the the Adobe Launch rule)
Comments
0 comments