Floodlight conversion counting methods

Floodlight activities correspond to specific events you’d like to track, such as the completion of a purchase or a visit to a webpage. When a user performs the action after seeing one of your ads, that's a conversion. For example, you set up an activity in Campaign Manager to track how many users visit your promotional website after viewing or clicking on an ad. When a user views an ad, then visits the page, that's a conversion.

Counting methods

For every Floodlight activity you create, you'll need to pick a counting method. This specifies exactly how Floodlight should measure conversions on your site.

There are two conversion counting methods, each with their own options:

  • Counter activities count the number of conversions associated with an event. This could be the number of times that users have visited a particular webpage after seeing or clicking on one of your ads. There are three ways to define a conversion for counter activities:

    • Standard: Counts every conversion.

    • Unique: Counts the first conversion for each unique user during each 24-hour day. 

    • Per session: Counts one conversion per user per session. You can define the length of a session for your site. 

  • Sales activities track the number of sales made or the number of items purchased. You can also capture the total value of each sale. There are two ways to define a conversion for sales activities: 

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

    • Items sold: Counts each conversion, plus the total number of items sold and the total associated revenue.

You can track both visits and sales data on the same webpage or app by setting up two different Floodlight activities. Alternatively, you can use a single Floodlight counter activity and use custom Floodlight variables to track sales data.

How conversions are counted

A conversion takes place when a user sees or interacts with an ad, then performs another action, such as visiting the advertiser's webpage or completing a purchase. A conversion can be recorded on the basis of a click, an impression, or a Rich Media event.

Whenever anyone visits a webpage with Floodlight tags, a Floodlight impression is generated. Campaign Manager checks each Floodlight impression to see whether the user had seen or clicked on one of your ads within the specified lookback window. A lookback window is a period of days for which an impression or click is considered relevant for Floodlight reporting.

A conversion is counted whenever a Floodlight impression is triggered by a user who falls within the specified lookback window. (For sales activities, Floodlight might count more than one conversion per event. For example, you can set up Floodlight to count the number of items purchased as the number of conversions for a single event.)

View-through and click-through conversions

In reports, conversions are divided into view-through and click-through conversions, depending on the user action that led to the conversion. But obviously you can't click an ad without first viewing it. How does Floodlight deal with conversions that are click-through and view-through?

Floodlight considers clicks to be more significant than impressions. Therefore, to avoid double-counting conversions, Floodlight counts a conversion as click-through if the user has clicked on one of your ads within the lookback window for clicks, even though the activity is also view-through.

Post-Rich Media event conversions

Along with view-through and click-through conversions, Floodlight can be used to track conversions that take place after a user triggers an exit event within a Rich Media creative. ( Exits are the events that take place when a user clicks on or otherwise interacts with the creative in a way that takes the user to a new webpage.) Rich media interactions are viewable in the path to conversion report.

Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue