Veracity DV360 / CM360 Integration
Veracities new tag manager integration allows the customer to fire any tag when a session is a bot.
When the Veracity Tracker detects a bot it pushes an event to the Tag Manager data layer.
{
event: 'veracity',
veracity_status: 'bot',
}
A. Tag Manager Variable
- Go to the Google Tag Manager Workspace for your website –
https://tagmanager.google.com/#/home - Select Variables in the left navigation, then New under User-Defined Variables
- Name the variable “veracity_status”
- Click the Variable Configuration box and select the “Data Layer Variable” type
- Ensure that the Data Layer Variable Name is set to “veracity_status” and the Data Layer Version is set to “Version 2”
- Save the Variable
B. Tag Manager Trigger
Now we have configured the variable we can use it to active a Tag Manager Trigger. This Trigger can be used to fire any tag when a bot is detected.
- Go to the Google Tag Manager Workspace for your website –
https://tagmanager.google.com/#/home - Select Triggers in the left navigation, then New
- Name the trigger “Veracity Bot Traffic Event”
- Click the Trigger Configuration box and select the “Custom Event” type
- Set the Event name to “veracity”, This trigger fires on to “Some Custom Events” and Fire this trigger when an event occurs and all of these conditions are true to “veracity_status” “equals” “bot”
- Click Save
Part 2 – Configure your DV360/CM360 Audience
In this part, we will configure a floodlight tag to tag bots in DV360/CM360, trigger that tag using Tag Manager, and then add bots flagged by that tag to an exclusion audience.
A. Create a Floodlight Audience
- Go to your Campaign Manager 360 account
- Navigate to your advertiser – make a note of its Advertiser ID
- Click Floodlight then Activities in the left navigation, then select New
- Name your activity “Veracity_Bot_Traffic”
- Set Type as “Counter”
- If you’ve already set up an Activity Group for Veracity Bots select that group, otherwise create a new group called “Veracity”
a. Set the Tag String to “Veracity”
b. Click Create - Under Advanced Properties define the Activity Tag String as “bot”
B. Trigger Floodlight from Tag Manager
- Go to the Google Tag Manager Workspace for your website
– https://tagmanager.google.com/#/home - Select Tags in the left navigation, then New
- Name the tag we recommend “Veracity Floodlight Tag – ADVERTISER NAME”
- Click on Tag Configuration and select “Floodlight” then “Floodlight Counter”
- Input the data below:
– Advertiser ID: The ID of the advertiser selected in 2A
– Group Tag String: “Veracity”
– Activity Tag String: “bot”
- Set Counting Method to “Standard”
- Click into the Triggering section and select “Veracity Bot Traffic Event”
- Click Save
Part 3 – Excluding Bots from your Advertising
In this section we will use the audience created above to exclude bots from our advertising, and give details on how to add important tracking data for full functionality.
A. Excluding the bot audience
You can exclude this audience from any line item
- In a Line Item, under Line Item Details then Audience Lists click the edit button
- Under Exclude select Add Audience to Expand
- Select the “Veracity Bot Exclusion Audience”
- Click Apply
- The bot audience is now excluded from this Line Item
B. Identifying new bots and reporting
In order to give the Veracity Tracker all of the details it needs to identify bots and add them to your audience, you must include the following tracking on all DV360/CM360 ads:
bcndyn=1&dvadid=${CAMPAIGN_ID}&cmadid=%ebuy!
Connecting DV360 to Veracity
For how to connect DV360 to Veracity see here;
https://go.veracitytrustnetwork.com/resource/connecting-dv360-to-veracity/
If you would like some help with this then please contact our customer support team.