DCM Floodlight Connector Setup Guide

DCM Floodlight Connector Setup Guide

by adapowers on ‎08-13-2018 10:18 AM - edited on ‎12-11-2018 11:47 AM by (650 Views)

Google DCM Floodlight connector allows inserting offline conversions into Floodlight Conversion Tracking & Attribution system through the DoubleClick Campaign Manager API. This article describes how to configure DCM Floodlight in your Universal Data Hub account.

Floodlight is the conversion tracking system for the DoubleClick Digital Marketing (DDM) platform. All properties within the DDM platform—Campaign Manager (DCM), Bid Manager, and DoubleClick Search (DS)—can use Floodlight.

In Google's documents, the DCM-based API is called DCM/DFA Reporting and Trafficking API to emphasize the role of DCM as a successor of DFA (DoubleClick for Advertisers). The latter was phased out in 2014.


Use DoubleClick Search (DS) if you don't run paid search reports in Report Builder or don't need to see search-driven offline conversions in your DDM platform—Campaign Manager (DCM) reports.

Use DCM if you run Paid Search reports in Report Builder and can identify conversions by encrypted user ID, mobile device ID, or Google click ID.

It's important that you use either DS or DCM, but not both: conversions you upload from both products are not de-duplicated and may cause data discrepancies.

Do not confuse Floodlight Conversion Tracking System with Floodlight tag, which is a tracking tag for DoubleClick platforms.

In this article:

Table of Contents Placeholder


  • You must have a DCM account.
  • Your DCM account must be enabled for API access.
  • You must have a user profile with access to this account.
  • Grant access to conversion data within your DCM account by enabling the https://www.googleapis.com/auth/ddmconversions scope for your DCM account.
  • Add user api@tealium.com to your account and grant it access to your DCM account.
  • Once user api@tealium.com is added to your DCM account, use the generated profile ID in the connector, either on the configuration page or on an action page. If defined in both locations, the profile ID defined on an action page takes precedence.

Supported Actions

Action Name Trigger on Audience Trigger on Streams
Track Conversion

Configure Settings

Go to the Connector Marketplace and add a new Google DCM Floodlight connector. Read the Connector Overview article for general instructions on how to add a connector.

To configure your vendor, select the Configure tab, then follow these steps:

  • Provide a title for the connector instance.
  • Provide a profile ID.
  • Note: the connector will be accessing your account on behalf of api@tealium.com. For this to work properly, you need to grant user api@tealium.com access to your DCM account.

Action Settings: Parameters and Options

Select the Actions tab to set up actions and their triggers. Choose Track Floodlight conversion action and click Create Action.

The following section describes parameters and options for the action.

Action: Track Floodlight conversion

Configuration IDs

The connector requires three IDs to access DCM Floodlight API.

  • Profile ID: The Floodlight Profile ID. Specify the Profile ID on the action page if not provided on the Configuration page.
  • Floodlight Configuration ID: The Floodlight Configuration ID of this conversion.
  • Floodlight Activity ID: The Floodlight Activity ID of this conversion.

User/Device ID

A conversion must be attributed to a specific user or device. This is achieved by providing one of the following (the properties are mutually exclusive):

  • Encrypted User ID: The single alphanumeric encrypted user ID or a list of encrypted user IDs.
  • Mobile Device ID: The mobile device ID.
  • Google Click ID: The Google click ID.

Encryption Options

The following parameters are required if a single or multiple encrypted user IDs are specified to identify the conversion. These parameters are not needed if the conversion is identified with device ID or Google Click ID.

Encryption Entity Type

This should match the encryption configuration for ad serving or data transfer.

Select one of the following:


Encryption Entity ID

This should match the encryption configuration for ad serving or data transfer.

Encryption Source

Describes whether the encrypted cookie was received from ad serving (the %m macro) or from data transfer. Choose one of the following:


Additional Parameters

  • Ordinal (REQUIRED): The ordinal of the conversion. Use this field to control how conversions of the same user and day are de-duplicated.
  • Timestamp: The timestamp of conversion, in Unix epoch microseconds. If not provided, it will be generated by the connector.
  • Limit Ad Tracking: Whether Limit Ad tracking is enabled. When set to true, the conversion will be used for reporting but not targeting. This will prevent remarketing.
  • Child Directed Treatment: Whether the conversion was directed toward children.

Quantity and Value

  • Quantity: The quantity of the conversion.
  • Value: The value of the conversion.

Custom Data

Custom Floodlight variables and their values map to the "u[1-20]=" in the Floodlight tag. Only array type attributes with identical number of elements are permitted.

  • Type: A collection of strings, each having a form of 'Uxxx' where xxx is a number from 1 to 100. For example: ["U1", "U2", "U3"].
  • Value: A collection of custom values. Each value must not exceed 50 characters.

Vendor Documentation