Before configuring DCM Floodlight as a destination in RudderStack, verify if the source platform is supported by DCM Floodlight by referring to the table below:
Once you have confirmed that the source platform supports sending events to DCM Floodlight, follow these steps:
- From your RudderStack dashboard, add a source. Then, from the list of destinations, select DCM Floodlight.
- Assign a name to the destination and click on Next.
To successfully configure DCM Floodlight as a destination, you will need to configure the following settings:
- DoubleClick Advertiser ID: Enter your Advertiser ID visible in the Campaigns or Activities tab in your dashboard.
- Activity Tag: Enter the Floodlight Activity Tag (
cat) to define the same parameter value across all the conversion events. Alternatively, you can define this value for each conversion event mapping in the Floodlight Activity Tag field below.
- Group Tag: Enter the Floodlight Group Tag (
type) to define the same parameter value across all the group conversion events. Alternatively, you can define this value for each conversion event in the Floodlight Group Tag field below.
typein your Campaign Manager dashboard, refer to the FAQ section below.
- RudderStack Event Name: Enter your RudderStack event name which will be mapped to the Floodlight tag.
- Floodlight Activity Tag: Enter the
catof your tag string. If left blank, RudderStack will pick the value from the Activity Tag field mentioned above.
- Floodlight Group Tag: Enter the
typeof your tag string. If left blank, RudderStack will pick the value from the Group Tag field mentioned above.
- Fire as Sales Tag: Enable the toggle button for Sales tag. Keep it disabled if it is a Counter tag.
- Counter tag: Used to count the number of conversions. It is supposed to be placed on the confirmation page after a sale with information about the
ordproperty passed to the tag.
- Sales tag: Used to count the number of conversions, the total number of sales that take place, and the total associated revenue. It is supposed to be placed on the confirmation page after a sale with information about the sales, like
ordproperties passed to the tag.
- Custom Floodlight variables: Enter the custom Floodlight variables to capture additional reporting data beyond the usual metrics (like visits and revenue).
- Use device mode to send events: Enable this setting to send events via the RudderStack device mode.
- Conversion Linker: Enabled by default, it sets the first-party cookies on your site’s domain.
- Allow ad personalization signals: Enabled by default, it lets the global site tag to collect remarketing data.
- DoubleClick Id: Enable this setting if you want to use the Google’s cookie matching functionality. Also, provide the below:
- Google Network Id: Enter the Google Network ID (NID) for the bidder account.
Finally, click on Next to enable DCM Floodlight as a destination in Rudderstack.
In your Campaign Manager dashboard, go to Floodlight > Activities. Here you can see all the activity names along with their Activity tag string (
cat) and Group tag string (
type), as shown:
To get the Advertiser ID, go to your Campaign Manager 360 account and navigate to the Campaigns or Activities tab in your dashboard to obtain the
To create custom Floodlight variables, refer to this Campaign Manager guide.
You can find the custom Floodlight variables for your activities by going to Floodlight > Activities. Then, click on any activity to view the custom variables associated with it, as shown:
In your Campaign Manager dashboard, you get two reporting options under Report Builder - Instant Reporting and Offline Reporting, as shown:
To generate an offline report of the events, follow these steps:
- Go to New > Floodlight.
- Select the Floodlight Configuration and other fields like Activities, Dimensions, and Metrics as per your requirement.
A conversion is said to be unattributed if the user has a DoubleClick cookie but it is converted without any exposure. This means that the user did not click or view any ad from the advertiser within Floodlight, or the interaction happened outside the lookback window.