Floodlight Counter tags

The Floodlight Counter tag allows you to count the number of times that users have visited a web page after those users have seen or clicked on one of your ads. There are two ways to add Floodlight tags to a container:

  • Accept a tag that has been pushed from the Campaign Manager user interface.
  • Add the tag from the Google Tag Manager user interface.

Accept a pushed Floodlight tag

A Floodlight Counter tag can be pushed directly to your container from the Campaign Manager user interface. When a Floodlight tag is pushed to Tag Manager, you need to approve the link request and pushed tags.

To accept a pushed Floodlight tag:

  1. Navigate to Approval Queue and then Tags.
  2. Click the activity name. Some parameters (e.g. the values for "src= ", "type= ", and "cat= ") will be pre-set.
  3. Make desired modifications to the tag, then click Approve.

Floodlight custom variables are key-values that can be used to track data that you collect about your users. Custom Floodlight variables use the keys u1=, u2=, etc. For pushed tags, Tag Manager variable names will be pre-populated in the custom variable fields To configure these variables to pass the appropriate data, map them to Tag Manager variables.

Important: To ensure proper tracking in all browsers, ensure that a Conversion Linker is enabled.

Learn more about Floodlight approvals.

Create a new Floodlight Counter tag

To create a new Floodlight Counter tag from scratch:

  1. In Tag Manager, click Tags and then New.
  2. Click Tag Configuration and select the Floodlight Counter tag type.
  3. To and gather the values required for tag configuration, open another browser window and sign in to Campaign Manager. Click Advertisers, and then click the name of the advertiser. Enter these values in your new Tag Manager Floodlight Counter tag:
    • Advertiser ID: The Advertiser ID will appear on the advertiser details page just below the advertiser's name. This value is also found as the value of src= in a generated Floodlight tag snippet.
    • Group Tag String: In the Activity table, identify the activity you want to work with and find the group tag string listed in a column to the right. This is also found as the value of type= in a generated Floodlight tag snippet.
    • Activity Tag String: In the Activity table, identify the activity you want to work with and find the activity tag string listed in a column to the right. This is also found as the value of cat= in a generated Floodlight tag snippet.
  4. Set the desired Counting Method:
    1. Standard: Counts every conversion.
    2. Unique: Counts the first conversion for each unique user during each 24-hour day, from midnight to midnight, Eastern Time (US).
    3. Per session: Counts one conversion per user per session. Session length is set by the site where the Floodlight tag is deployed.
  5. For legacy implementations that use them, enter values for the U and Tran variables.
  6. Enter any Custom Variables that you need for your implementation. Floodlight custom variables are key-value pairs that can be used to track additional data about your users. The keys are formatted as "u1=", "u2=", etc. Click +Custom Variable to add a new key value pair. For each custom variable, select a Tag Manager variable that contains the value that you would like to pass to the Floodlight custom variable.
  7. Click Triggering and select a trigger that corresponds to the landing page for your campaign where you would like the tag to fire.
  8. Important: To ensure proper tracking in all browsers, ensure that a Conversion Linker is enabled.
  9. Save and publish your container.

Mobile Floodlight activities

The process for receiving mobile Floodlight activities is similar to the process for regular Floodlight activities, with some small changes.

You’ll need to create a container specifically for mobile activities and use this container to link to Campaign Manager. If you’ve already created a container to fire your regular Floodlight tags, note that you’ll need to create and maintain a separate mobile container specifically for mobile Floodlight tags.

When you receive the tags, you may also receive specific instructions with conditions for how they should fire. There are two mobile-specific settings you may have to configure:

  • Unrepeatable: Check this box if you want your Floodlight tag to fire only once over the lifetime of the app (for example, when a user downloads or installs an app).
  • Triggers: The activity must be tied to a trigger in Tag Manager so that the tag fires.
Was this article helpful?
How can we improve it?