RudderStack lets you send your event data to DCM Floodlight destination via the device mode using the native web SDK. RudderStack uses global site tagging in device mode.

Track

The track call lets you capture user events along with the properties associated with them.

A sample track call is as shown below:

Copy
rudderanalytics.track('tshirt', {
  countingMethod: "transactions",
  revenue: "2605846",
  orderId: "2605847"
});

The countingMethod is a required property that specifies how to count the conversions for a Floodlight activity. The methods to count conversions depend on whether you are creating or editing a counter or sales tag activity. Refer to the FAQ section for more information on counting methods for these tags.

The following table details the integrations object mapping for DCM Floodlight:

The following table details the mapping between the optional RudderStack and DCM Floodlight properties:

There are some slight variations in terms of the mapped DCM Floodlight parameters when you use the Iframe tag, as opposed to the global site tag. However, RudderStack handles this variation internally.

The following table details the mapping between the optional RudderStack and DCM Floodlight properties when using the Iframe tag:

The following table provides a brief description of the above DCM Floodlight properties:

Custom parameters

You can also send data to DCM Floodlight using the below-mentioned custom fields:

Page

The page call lets you record your website's page views with any additional relevant information about the viewed page.

Based on the presence of name and category fields in the page call, RudderStack transforms the event in the following format:

A sample page call is as shown below:

Copy
rudderanalytics.page('landing', {
  countingMethod: "standard"
});

FAQ

What are the counting methods for sales and counter tag?

For the Sales tag, the counting methods are as shown:

For the Counter tag, the counting methods are shown below: