DOCSEARCHbyAlgolia
Submit Docs

Usercentrics Adobe Launch Extension Documentation

website·Indexed 30 days ago

https://diva-e.github.io/usercentrics-adobe-launch-extension-documentation/

Documentation for the Usercentrics Adobe Launch Extension, including installation guides, configuration for Data Processing Services (DPS), and details on events, conditions, and actions. Supports versions 1.0.6, 1.0.7, and Next, providing integration for the Usercentrics (V2) CMP with Adobe Audience Manager and Adobe Target.

Tokens
4.3K
Snippets
2
Records
40
Agent score
73%

What's inside Usercentrics Adobe Launch Extension

  1. Reload the website after consent changes using the Usercentrics Adobe Launch extension

    The 'Reload Website' action (Version 1.0.6) is a simple utility used to refresh the current page. This is specifically useful when implementing third-party tags that cannot dynamically react to consent changes and require a full page reload to read the new consent state. This action is optional and may not be required depending on the specific Data Privacy Solution (DPS) implementation being used.

  2. Access version-specific documentation for the Usercentrics Adobe Launch Extension

    The Usercentrics Adobe Launch Extension documentation supports versioning to ensure compatibility with the version of the extension installed in Adobe Launch. Users can switch between documentation versions using the version dropdown located in the navigation bar. By default, the documentation displays the current released version. The 'Next' version option provides a preview of the work-in-progress state for upcoming extension releases.

  3. Trigger Adobe Launch rules using the Usercentrics Consent Update event

    The Consent Update event triggers when the configured Window Event fires. To prevent infinite loops (such as when a page reload is configured as an action), this update is not called during the initial Window Event.

    For scenarios where consent is already granted for a new user's initial page view (e.g., technically required Data Processing Services/DPS), it is recommended to add the 'Cookie Consent Management by Usercentrics CMP v2 - Initialized' event to the rule to ensure the action triggers correctly.

  4. Prerequisites for Usercentrics Adobe Launch Extension

    To use the Usercentrics Adobe Launch extension (Version 1.0.7), ensure the following requirements are met:

    1. The website must use Usercentrics CMP Version 2.
    2. The account plan must support the 'Window Event Name' function.
    3. If consent management is handled externally rather than through the extension, the extension can still be used solely to load the Usercentrics CMP Version 2 on the website.

  5. Implement Smart Data Protector with Adobe Tag Manager

    The Smart Data Protector is not integrated into the Adobe Launch extension. To implement this feature, the Usercentrics ScriptTag must be placed directly on the website and executed before Adobe Tag Manager. This sequence prevents the CMP from being hidden from the user and ensures the Tag Manager is not blocked by the Smart Data Protector.

  6. Trigger Adobe Launch rules using the Usercentrics Consent Update event

    The Consent Update event (Version 1.0.7) triggers when the configured Window Event fires. To prevent infinite loops (such as when a page reload is configured as an action), this event is specifically designed not to fire on the initial Window Event.

    For scenarios where consent is already granted for a new user on the initial page view (e.g., technically required Data Processing Services/DPS), it is recommended to add the 'Cookie Consent Management by Usercentrics CMP v2 - Initialized' event to the rule to ensure coverage.

  8. Load the Usercentrics (V2) CMP in Adobe Launch

    The 'Load Usercentrics' action initializes the Usercentrics (V2) Consent Management Platform (CMP). If enabled in the extension's configuration page, it automatically applies Usercentrics consents to the ECID opt-in framework. To ensure the CMP loads before other scripts, set the loading order to 1 and associate it with the 'Library Loaded (Page Top)' event.

  9. Trigger the Consent Update event in Adobe Launch

    The 'Consent Update' event triggers when the configured Window Event fires. To prevent infinite loops (such as when a page reload is configured as an action), this update is specifically designed not to be called on the initial Window Event.

    For scenarios where consent is already granted for a new user's initial page view (e.g., for technically required Data Processing Services/DPS), it is recommended to add the 'Cookie Consent Management by Usercentrics CMP v2 - Initialized' event to the rule.

  10. Reload the website after consent changes in Adobe Launch

    The 'Reload Website' action is a simple utility used within Adobe Launch rules to refresh the browser page. This is specifically useful when implementing third-party tags that cannot dynamically update their behavior and require a full page reload to read a newly updated consent state from the Usercentrics Consent Management Platform (CMP). This action is optional and may not be required depending on the specific DPS (Data Protection Suite) implementation being used.

  11. Load the Usercentrics (V2) CMP via Adobe Launch

    The 'Load Usercentrics' action (Version 1.0.7) loads the Usercentrics (V2) Consent Management Platform (CMP). If enabled in the extension's configuration page, it automatically applies Usercentrics consents to the ECID Opt-In framework. To ensure the CMP loads before other scripts, set the action's order to 1 within the 'Library Loaded (Page Top)' event.

  12. Reload the website after consent changes using the Usercentrics Adobe Launch extension

    The 'Reload Website' action (Version 1.0.7) is a simple utility used to refresh the browser page. This is specifically useful when implementing third-party tags that require a full page reload to recognize and apply a new consent state. This action is optional and may not be required for all DPS (Data Protection Suite) implementations.