DoubleVerify (DV) Integration

General

The DoubleVerify (DV) API integration allows clients to activate DoubleVerify’s services on ads served by Clinch. The services include monitoring and blocking services on Display and Video campaigns in a simple and expedited manner within Flight Control. This integration and set-up process removes the manual aspect of tag wrapping and reduces the trafficking time required for campaign activation.

This document provides step by step instructions on how to create and manage an account integration and enablement between DoubleVerify [DV] and Clinch Ad Tags within Flight Control.

Step 1: Obtain your DV Client ID

• To get started, a Client/Advertiser must connect the Clinch team with their DoubleVerify contact.
• Obtain your DoubleVerify Client ID (CTX) - required for next step 

Step 2: Connect a DV Advertiser Account in Flight Control

1. On the left main menu, click Account > Integrations
2. Click Add > select DoubleVerify Integration
3. Enter the DV Client ID under the field ‘DV customer id (CTX)’ > click Add Integration

Note: The integrated account is listed as a row under the Integration page.  Should you need to delete an integration, select the account to delete, click Actions, and select Delete

Step 3: Enable DV Services in a Campaign 

The following steps will walk you through enabling DoubleVerify as a service in a Flight Control campaign.

1. Go to the campaign's Homepage.
2. Toggle the DoubleVerify Service.
3. Select a DV Account > select a Service (Monitoring or both Monitoring + Blocking)
   • Display Campaigns: 
     • Universal Monitoring Tag is set as the default.
     • Click Enable Blocking Service to include this service as well (optional)
   • Video Campaigns: 
     • Select between Video OmniTag (default) or Universal Monitoring Tag.
       • Video OmniTag allows for monitoring and blocking. Flight Control can generate DoubleVerify Video OmniTags through the use of the API
         • Filtering services can also be included (optional) 
       • Universal Monitoring Tag enables a monitoring pixel without a wrapper. This option is mainly used in cases where the publisher does not support the OmniTag wrapper, or in cases where we want to apply monitoring to existing ad tags and do not want to retraffick the tags to add the wrapper.
     • Media Filter: Select the type that will best suit the media the campaign is going to be served on.
       • All: The VAST tag will support both VPAID and non-VPAID inventory.
       • VPAID only
       • Non-VPAID only

About the DoubleVerify Blueprint

The DoubleVerify Blueprint is a collection of essential campaign information with the DoubleVerify settings applied, and it needs to include the ad server information in order to map data. The purpose of sending the Blueprint is to mirror the structure on the DoubleVerify end so that reporting between the systems is aligned. 

1. If CM360 is the source of truth for the advertiser, you can export a DoubleVerify Blueprint from your Flight Control campaign's Placements step by using the Export DoubleVerify Blueprint action (requires prior enablement of the campaign's DoubleVerify Service). Then, you can upload it to DoubleVerify to create the "Blueprint" with CM360 as the ad server.
   • In Flight Control, these IDs can be added as Custom Parameters at the placement level. Select and enter the DoubleVerify External Campaign ID, DoubleVerify External Site ID, and DoubleVerify External Placement ID.
2. If Flight Control is the source of truth for the advertiser, Clinch will send an export template of just Clinch's placement IDs to upload into DoubleVerify to create the "Blueprint" with Flight Control as the Ad Server.

Important: Clients/Advertisers should be aware of which set of IDs the Clinch team uses (either Clinch’s own IDs or the ID values from their primary Ad Server) and add the relevant campaign ID to the DoubleVerify Blueprints.

About Monitoring and Blocking Services

Monitoring 

• DoubleVerify’s monitoring service can be applied to ad tags as described above.
• Flight Control can also pass external third-party ad server details.
  • For example, CM360 placement IDs and campaign IDs can be passed through Flight Control, allowing clients to supply placement translations as they would do if CM360 were the primary Ad Server. 
  • To enable this feature, you will need to enter these IDs in each placement in Flight Control as described in the About the DoubleVerify Blueprint section.

Blocking

• After applying DoubleVerify monitoring services from within an ad campaign in Flight Control, DoubleVerify’s display blocking feature can also be enabled, if necessary. Flight Control automatically appends a JavaScript Wrapper Tag to block based on settings set in DoubleVerify.
• Blocking applies to Display/In-Banner Video, Video, and Interactive Video. (VPAID/VAST).
• The DV Blocking Service isn't supported for CTV campaigns since the service requires JavaScript, which isn't allowed in CTV environments.

DV "IQ Programmatic Advanced" (IQPA) Service

1. When trafficking Display tags to TTD that utilize DV blocking service, an additional IQPA script is appended.
2. This script is inserted whether the advertiser uses DV IQPA or not, and causes no harm in case the service is not in use.