New Consent Management System Integrates with Key Digital Advertising Platforms
A recently implemented consent management system is now actively integrating with prominent digital advertising and marketing platforms, enabling granular control over user data permissions. This system, designed to comply with evolving privacy regulations, dynamically loads specific vendor scripts based on user consent choices.
The core functionality of the system revolves around it’s ability to listen for user consent events through the Transparency and Consent Framework (TCF). Upon confirmation of user consent, either at the initial loading of the consent manager or after a user has made their selections, the system retrieves a list of consented vendors. For each consented vendor identified by a unique ID, the system checks for a pre-defined JavaScript function associated with enabling that vendor’s service.
As an example, the system includes a specific integration for Cleverpush, a push notification service. The `loadCleverpush` function is designed to be executed when a user grants consent for the vendor identified by the ID ‘5e77928e9cb08971eb078f60’. this function, when called, dynamically creates and appends a script tag to the document’s body, pointing to the Cleverpush loader script located at `https://static.cleverpush.com/channel/loader/xwz3JQuJeCAG7AtQY.js`. This loading is contingent on a `displayCleverpush` flag and is further deferred until the page’s `load` event has fired, ensuring the main page content is ready.
another example within the system’s vendor configuration is an integration for Facebook Audiences Network, linked to the vendor ID ‘5f58a13f95e5ca5c38b2f0d1’.The associated `enable_call` is specified as `loadFacebookAudiencesNetwork`, indicating a similar mechanism for activating this service upon user consent.
The event listener for TCF events is set up to capture `tcloaded` and `useractioncomplete` statuses. Once these events are detected, the system requests custom vendor consents. If the retrieval is triumphant, it iterates through the list of consented vendors. For any vendor present in its internal `vendors` mapping, the system attempts to execute the corresponding `enable_call` function, provided it exists as a global function on the `window` object. After processing the consents, the TCF event listener is removed to prevent further redundant calls.