• Expand/CollapseMenu
Help

DCM Floodlight Connector Setup Guide

Google DCM Floodlight connector allows inserting offline conversions into Floodlight Conversion Tracking and Attribution system through the DoubleClick Campaign Manager API.

This article describes how to configure DCM Floodlight in your Customer 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.

DS vs DCM

Use DoubleClick Search (DS) if you do not run paid search reports in Report Builder or do not 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:

Requirements

  • 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 with the Insert offline conversions permission.
  • 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.

Floodlight is the conversion tracking system for the DoubleClick Digital Marketing (DDM) platform. This article describes how to set up the Google DCM Floodlight connector in your Customer Data Hub account.

Table of Contents Placeholder

API Information

This connector uses the following vendor API:

Batch Limits

This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met:

  • Max number of requests: 1000
  • Max time since oldest request: 60 minutes
  • Max size of requests: 1 MB

Connector Actions

Action Name AudienceStream EventStream
Track Floodlight Conversion ✓ ✓

Configure Settings

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

When you add this connector you are prompted to accept the vendor's data platform policy.

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Track Floodlight Conversion

Parameters

Parameter Description
Profile ID
  • The Floodlight Profile ID that is given to you by DCM, after adding the "api@tealium.com" user to your DCM account.
  • If configured here, the value will overwrite the value defined in the Configuration.
Floodlight Configuration ID
  • Required.
  • The Floodlight configuration ID of this conversion.
Floodlight Activity ID
  • Required.
  • The Floodlight activity ID of this conversion.
Encrypted User ID
  • If one or more Encrypted User IDs are specified, then Encryption Entity Type, ID and Source sections are required.
Google Click ID
  • Specify either a single device ID, a single click ID, a single user ID, or multiple user candidate IDs.
  • It is acceptable to use a list with candidate IDs for a single user candidate ID parameter).
Mobile Device ID
  • Specify either a single device ID, a single click ID, a single user ID, or multiple user candidate IDs.
  • It is acceptable to use a list with candidate IDs for a single user candidate ID parameter).
Encryption Entity Type
  • Required if Encrypted User ID is specified.
  • Must match the encryption configuration for ad serving or data transfer.
Encryption Entity ID
  • Required if Encrypted User ID is specified.
  • Must match the encryption configuration for ad serving or data transfer.
Encryption Source
  • Required if Encrypted User ID is specified.
  • Describes whether the encrypted cookie was received from ad serving or from data transfer.
Timestamp in micros
  • The timestamp of conversion, in Unix epoch microseconds.
  • If not provided, it will be auto-generated.
Treatment For Underage
  • Set to true if the request may come from an underage user (see GDPR).
Limit Ad Tracking
  • Set to true to use the conversion for reporting only, not for targeting.
Ordinal
  • Required.
  • The ordinal of the conversion.
  • Used to de-duplicate conversions of the same user and day.
Child Directed Treatment
  • Set as true for conversions directed toward children.
Non-Personalized Ad
  • Set as true if the conversion was for a non-personalized ad.
Conversion Quantity
  • The quantity of the conversion.
Conversion Value
  • The value of the conversion.
Custom Variable Values
  • A collection of custom values.
  • Each value must not exceed 50 characters.
Custom Variable Types
  • A collection of strings, each having a form of 'Uxxx' where xxx is a number from 1 to 100.

Vendor Documentation

Version history
Last update:
2 weeks ago
Updated by:

Copyright All Rights Reserved © 2008-2021

Public