Back

This article describes how to configure Floodlight in your Tealium iQ account.

The Floodlight tag was previously branded as the Google DoubleClick Floodlight tag.

To learn how to configure Floodlight tags in bulk, see Configuring Multiple Floodlight Tags.

In this article:

Table of Contents Placeholder

Tag Configuration

First, go to Tealium's Tag Marketplace and add the Floodlight (gtag.js) tag to your profile (how to add a tag?).

After adding the tag, configure the following settings:

Setting Description

Advertiser ID

advertiser_id

  • Required
  • One or more Advertiser IDs separated by commas (e.g. DC-123456789)
  • Data will be sent to all IDs

Activity Group

activity_group

  • Required
  • One or more Activity Group names separated by commas
  • Must match the length of Advertiser ID

Activity

activity

  • Required
  • One or more Activity names separated by commas
  • Must match the length of Advertiser ID

Counting Method

counting_method

  • Required
  • One or more counting method names separated by commas
  • Must match the length of Advertiser ID
  • Converts to lowercase

Auto Fire Purchase Event

fire_purchase

  • Values are True or False
  • Fires purchase event when an Order ID is present.
  • If counting method is not set, it will be set to transactions.

Allow Custom Scripts

custom_scripts

  • Values are True or False
  • The default value is True
  • Enables Dynamic tags to integrate third-party tools for tracking website activity

 Global Object

 gtag

 
  • The name of the global object used for the event queue
  • If not specified, gtag is used
  • Not required for most implementations

Load Rules

Load Rules determine when and where to load an instance of this tag on your site.

Data Mappings

Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings.

The destination variables for the Floodlight (gtag.js) tag are built into its Data Mapping tab.

The following sections and accompanying tables describe available categories.

Standard

Destination Name Description

Advertiser ID

advertiser_id

  • Use to override the configuration value
  • Accepts either a comma separated string or an array

Activity Group

activity_group

  • Use to override the configuration value
  • Must match the length of Advertiser ID
  • Accepts either a comma separated string or an array

Activity

activity

  • Use to override the configuration value
  • Must match the length of Advertiser ID
  • Accepts either a comma separated string or an array

Counting Method

counting_method

  • Use to override the configuration value
  • Must match the length of Advertiser ID
  • Accepts either a comma separated string or an array
  • Converts to lowercase

Session ID

session_id

  • Map none, one, or a set of values matching the length of Advertiser ID
  • Place blanks where not needed
  • Accepts either a comma-separated string or an array

Event Name

event_action

The name of the current event

Auto Fire Purchase Event
fire_purchase

  • Values are True or False
  • Fires purchase event when an Order ID is present.
  • If counting method is not set, it will be set to transactions.

Allow Custom Scripts

custom_scripts

  • Values are True or False
  • Use to override the configuration value

Counting Methods

Floodlight supports the following counting methods by default.

Counting methods are automatically lower-cased.

Counting Method Name Description

Standard

standard

Counts every conversion

Unique

unique

Counts the first conversion for each unique user during each 24-hour day

Per Session

per_session

  • Counts one conversion per user per session
  • You can define the length of a session for your site within DCM

Transactions

transactions

Counts all conversions, plus the total number of sales that take place and the total associated revenue

Items sold

items_sold

Counts each conversion, plus the total number of items sold and the total associated revenue

Events

Map to these destinations for triggering specific events on a page. 

Use the following steps to trigger an event:

  1. Select Conversion or Purchase from the drop-down list.
  2. In the Trigger field, enter the value of the variable being mapped.
  3. To map more events, click + Add and repeat Steps 1 and 2.
  4. Click Apply.
    The event triggers when the supplied value is found in the data layer.
Destination Name Description

conversion

conversion

  • Map to trigger sending a conversion type event.
  • Conversion events are not sent by default.
  • Use the standard, unique or per_session counting method for this event.

purchase

purchase

  • Map to trigger sending a purchase type event.
  • Purchase events are sent automatically when an order ID is present.
  • Use the transactions or items_sold counting method with this event.

E-Commerce

As the Floodlight (gtag.js) tag is e-commerce enabled, it will automatically use the default E-Commerce extension mappings. Manually mapping in this category is generally not needed unless you want to override any extension mappings to your desired e-commerce variable is not offered in the extension.

Destination Name Description

Order ID

order_id

Use this to override the default e-commerce value _corder

Order Total

order_total

Use this to override the default e-commerce value _ctotal

List of IDs
product_id

Use this to override the default e-commerce value _cprod

List of Quantities

product_quantity

  • Use this to override the default e-commerce value _cquan
  • Accepts a single number override or an array of values

List of Prices
 product_unit_price

Use this to override the default e-commerce value _cprice

Custom

Destination Name Description

DoubleClick Custom Parameters

dc_custom_params.myvar

  • Use to send custom parameters as part of the dc_custom_params object
  • Replace myvar with the name of your parameter

Custom Variable 1

custom.u1

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u1
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 2

custom.u2

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u2
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 3

custom.u3

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u3.
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 4

custom.u4

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u4
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 5

custom.u5

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u5
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 6

custom.u6

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u6
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 7

custom.u7

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u7
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 8

custom.u8

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u8
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 9

custom.u9

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u9
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 10

custom.u10

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u10
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 11

custom.u11

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u11
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 12

custom.u12

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u12
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 13

custom.u13

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u13
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 14

custom.u14

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u14
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 15

custom.u15

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u15
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 16

custom.u16

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u16
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 17

custom.u17

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u17
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 18

custom.u18

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u18
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 19

custom.u19

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u19
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 20

custom.u20

  • Use to add custom metrics and dimensions
  • Associate with the custom Floodlight variable u20
  • Defaults to dimension or metric name if not provided in mapping

Custom Variable 21+

custom.u#

  • Use to add custom metrics and dimensions beyond 20 (not supported in Floodlight Search)
  • Associate with the custom Floodlight variable u#
  • Replace the # sign in mapping with the desired number

Additional Documentation

Tags (1)