Tag Commander (Commanders Act)

   Permissions:

Vendor list-GDPR or Vendor list-U.S. Privacy or Vendor list - U.S. Multi-State

Commanders Act tag management system, Tag Commander, allows for the creation of custom triggers to fire tag containers. In this article, we will cover how to fire custom triggers configured in Tag Commander through the Sourcepoint platform.


Create custom trigger in Tag Commander

As part of the set up in Tag Commander you will create a custom trigger and define a custom trigger function. For more information on how to create a custom trigger in the Tag Commander platform, please read this article.

In this article, we will use a custom trigger called "fire custom consent" with a custom trigger function called tC.event.fire_custom_consent as an example.


Add trigger to vendor list

In this section, we will cover how to add the trigger to a vendor. Navigate to your Sourcepoint account and click Vendor Management on the left-hand panel and select a regulatory framework from the menu. 

Screenshot 2023-11-13 at 12.37.26 PM.png

Select a vendor list from the subsequent page.

landing page.png

GDPR / U.S. Privacy (Legacy) U.S. Multi-State Privacy

Click the appropriate vendor or purpose from the list.

Screenshot_2023-07-31_at_2_11_56_PM.jpg

Select either Consent Actions or Reject Actions from the subsequent modal. The action selected is dependent on the trigger being implemented. 

Screen_Shot_2022-01-11_at_10.25.58_AM.png

Input the custom trigger function set up in the the Tag Commander platform under the Custom JS tab. Below is an example of the custom function tC.event.fire_custom_consent.

Click Apply changes when finished.

Screen_Shot_2022-01-11_at_10.27.17_AM.png

With the trigger applied to the vendor/purpose, click Save to confirm the changes to the vendor list.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.