Google Campaign Manager 360 Floodlight Connector Setup Guide | Server-Side Connectors

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. For more information, see Google: About Floodlight conversion tracking.

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.

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.
After 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.

API Information

This connector uses the following vendor API:

API Name: Google Campaign Manager 360 API
API Version: v4
API Endpoint: https://www.googleapis.com/dfareporting/
Documentation: Google: Campaign Manager 360 API

Batch Limits

This connector uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:

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

Delayed Actions

Actions are delayed for 30 minutes to accommodate uploading offline conversions, as per Google’s best practices. For more information about delayed actions using the Google Campaign Manager 360 Floodlight connector, see Google: Best practices for uploading offline conversions.

Actions are not delayed when using trace in EventSream or AudienceStream.

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.

After adding the connector, configure the following settings:

Floodlight Profile ID
- The Floodlight Profile ID that is given to you by Campaign Manager 360, after adding the api@tealium.com user to your Campaign Manager 360 account.

When you add this connector, you will be 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

Configuration ID Parameters

Parameter	Description
Floodlight Configuration ID	Required. The Floodlight configuration ID of this conversion.
Floodlight Activity ID	Required. The Floodlight activity ID of this conversion.
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 overwrites the value defined in the Configuration.

User/Device ID

If multiple attributes are mapped, the first non-empty value will be sent.
All the conversions are sent after a 30 minute delay.

Parameter	Description
Encrypted User ID	If one or more Encrypted User IDs are specified, then Encryption Entity Type, ID and Source sections are required.
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.
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.
Display Click ID	The unique identifier for ad clicks.
Match ID	A unique advertiser-created identifier assigned to each conversion event.
Impression ID	A unique identifier assigned to each impression.

Encryption Source

Parameter	Description
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.

Quantity and Value

Parameter	Description
Ordinal	Required. The ordinal of the conversion. Used to de-duplicate conversions of the same user and day.
Limit Ad Tracking	Set to `true` to use the conversion for reporting only, not for targeting.
Timestamp in micros	The timestamp of conversion, in Unix epoch microseconds. If not provided, it will be auto-generated.
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.
Treatment For Underage	Set to `true` if the request may come from an underage user (see GDPR).

Custom Data

Map attributes to U custom variables as needed. Only populated values are sent. Use of the mapping destinations in this section supersede any mappings in the Custom Data Arrays - Legacy section.

Custom Data Arrays - Legacy

Parameter	Description
Custom Variable Values	An array of custom values. Each value must not exceed 50 characters.
Custom Variable Types	An array of strings matching the pattern “U1” through “U100”. Any string that does not match this pattern will be excluded.