Floodlight (gtag.js) Tag Setup Guide
This article describes how to configure Floodlight in your Tealium iQ Tag Management account.
Tag tips
- Activate the conversion API before beginning. For more information, see Google: Create a Google tag for a new Floodlight conversion action.
- Supports the ecommerce extension for:
- Order ID (
_corder
) - Order Total (
_ctotal
) - List of Product IDs (
_cprod
) - List of Quantities (
_cquan
) - List of Prices (
_cprice
)
- Order ID (
- Use mappings to:
- Set up event triggers
- Dynamically override standard config values
- Dynamically override ecommerce extension values
- Pass custom event parameters by mapping to “DoubleClick Custom Parameters” and replacing
myvar
with your custom variable name. - If you do not need a Session ID while using a list, set SessionID to an empty space or empty string.
- For additional information, see the Google: Floodlight documentation.
Tag configuration
Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag.
When adding the tag, configure the following settings:
- Advertiser ID
- A single or comma separated list of advertiser identifiers that are the source of the Floodlight activity, or example,
DC-123456789
.
- A single or comma separated list of advertiser identifiers that are the source of the Floodlight activity, or example,
- Group Tag String
- A single or comma-separated list of group tag strings.
- Must match the number of Advertiser IDs.
- Activity Tag String
- A single or comma-separated list of activity tag strings.
- Must match the number of Advertiser IDs.
- Counting Method
- A single or comma-separated list of counting methods.
- Must match the number of Advertiser IDs.
- Auto Fire Purchase Event
- Fires purchase event when an Order ID is present.
- If counting method is not set it will be set to transactions.
- Allow Custom Scripts
- Enables Dynamic tags to integrate third-party tools for tracking website activity.
- Global Object
- This value is the name of the Global Object used for the event queue.
- If not specified,
gtag
is used. - Not required for most implementations.
- Data Layer Name
- By default, the data layer initiated and referenced by the global site tag is named
dataLayer
. - Rename the data layer only if your project requires a separate name.
- By default, the data layer initiated and referenced by the global site tag is named
- Cross-Tracking Domains
- A comma-separated list of domains to use with Cross-Domain Tracking (
setAllowLinker
). - This value should be the top-level domain, for example,
tealiumiq.com
.
- A comma-separated list of domains to use with Cross-Domain Tracking (
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 available categories are:
Standard
Setting | Description |
---|---|
Advertiser ID advertiser_id |
|
Group Tag String activity_group |
|
Activity Tag String activity |
|
Counting Method counting_method |
|
Session ID session_id |
|
Event Name event_name |
|
Auto Fire Purchase Event fire_purchase |
|
Allow Custom Scripts custom_scripts |
|
Cross-Tracking Domains cross_track_domains |
|
Match ID dc_custom_params.match_id |
|
Ordinal dc_custom_params.ord |
|
Events
Map to these destinations for triggering specific events on a page.
Use the following steps to trigger an event:
- Select the
tealium_event
variable. - Click + Add Mapping.
- In the left sidebar, click Event.
- In the Trigger field, enter the value of the variable being mapped.
- Select Conversion or Purchase from the drop-down list.
- Click + Add.
- To map additional variables, repeat Steps 4, 5, and 6.
- Click Done.
The event triggers when the supplied value is found in the data layer.
Destination Name | Description |
---|---|
conversion conversion |
|
purchase purchase |
|
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 |
|
Order Total order_total |
|
List of IDs product_id |
|
List of Quantities product_quantity |
|
List of Prices product_unit_price |
|
Custom
Destination Name | Description |
---|---|
DoubleClick Custom Parameters dc_custom_params.myvar |
|
Custom Variable 1 custom.u1 |
|
Custom Variable 2 custom.u2 |
|
Custom Variable 3 custom.u3 |
|
Custom Variable 4 custom.u4 |
|
Custom Variable 5 custom.u5 |
|
Custom Variable 6 custom.u6 |
|
Custom Variable 7 custom.u7 |
|
Custom Variable 8 custom.u8 |
|
Custom Variable 9 custom.u9 |
|
Custom Variable 10 custom.u10 |
|
Custom Variable 11 custom.u11 |
|
Custom Variable 12 custom.u12 |
|
Custom Variable 13 custom.u13 |
|
Custom Variable 14 custom.u14 |
|
Custom Variable 15 custom.u15 |
|
Custom Variable 16 custom.u16 |
|
Custom Variable 17 custom.u17 |
|
Custom Variable 18 custom.u18 |
|
Custom Variable 19 custom.u19 |
|
Custom Variable 20 custom.u20 |
|
Custom Variable 21+ custom.u# |
|
IAB Transparency and Consent Framework v2
Variable | Description |
---|---|
Enable TCF Support tag_enable_tcf_support |
|
Enhanced Conversions
Variable | Type | Description |
---|---|---|
user_data.email |
String | Email Address |
user_data.phone_number |
String | Phone Number |
user_data.address.first_name |
String | First Name |
user_data.address.last_name |
String | Last Name |
user_data.address.street |
String | Street Address |
user_data.address.city |
String | City |
user_data.address.region |
String | Region |
user_data.address.postal_code |
String | Postal Code |
user_data.address.country |
String | Country |
Additional documentation
This page was last updated: June 6, 2024