Customize Floodlight reporting by column

With Floodlight column reporting, you have the power to select the level of Floodlight reporting you want to see, and you can see it an easy-to-read column format. You can:

  • Create and name a column for each Floodlight activity you want to report on.

  • Create a column that rolls up the data for a Floodlight group or any combination of Floodlight groups and activities of your choosing.

  • Select the metric you want to see in the column. This allows you to create the equivalent of a column (such as Actions, Cost/action, etc.) that’s filtered to the selected Floodlight activities. This includes historical data.
    To see data in the column, the type of metric needs to match the type of Floodlight activities you selected. For example, if you select Action Floodlight activities and the Transaction metric, the column will display 0.
  • Easily add, delete, or rearrange your Floodlight columns at any time.

  • Download the report as needed.

If you're tracking multiple activities on your site, this will allow you to easily pick and choose which Floodlight activities to analyze. For example, if you sell software on your site, you may want to see which keywords lead to free downloads vs. paid downloads to help optimize keyword landing pages. With Floodlight columns, you can add just the two activities to easily compare statistics. If you're just interested in any download, you can create a new column that combines the metric from both activities into one column.

As another example, you select a Floodlight activity named Email sign-up and select the Actions metric. The new column will display the count of email sign-ups. If you select Cost/action instead, you’ll see the cost per email sign-up.

Steps to set up your Floodlight reporting columns
  1. Click the Columns button in the toolbar above the performance summary graph.
    The column selection tool appears.

  2. Click Floodlight activities under the Available columns header.
    A list of your existing Floodlight columns appears.

  3. Click Create a new column.

  4. Name your column and select the Floodlight activities and/or Floodlight groups whose data you want to include in the column.

  5. Use the Metric dropdown to select the metric you want to report on.

  6. Click Save to add the column to your reporting table.

  7. Under Selected columns, drag and drop the new column to the desired location.

  8. Click Apply.
    The new column appears in your reporting table.

Notes and known issues
  • Advertiser-level columns: These are advertiser-level columns. In other words, you won’t see them at the agency level, but you will at the advertiser, campaign, ad group, ad, or keyword level.

  • No filter support: Floodlight columns are not supported in filters. They don't appear in the list of available filters.

  • Floodlight activity groups: In the column selection tool, selecting a Floodlight activity group is the same as selecting all of the Floodlight activities under the group at the time of column creation. If you later add a new Floodlight activity under the Floodlight activity group, the column will not automatically include data for that activity. If you do create new Floodlight activities, we recommend you review the definitions of your existing Floodlight columns and create new ones as necessary.

  • Bid strategy summary page: Floodlight columns do not appear on the bid strategy summary page.

  • Floodlight columns and Floodlight instructions:
    • Currently, the Floodlight column selection tool shows all Floodlight activities within the advertiser’s Floodlight configuration. In other words, if you filtered some Floodlight activities through Floodlight instructions, the filtered activities will still appear in the column selection tool.
    • If you create a Floodlight column with such a filtered Floodlight activity, the column will display stats of 0. The Floodlight instructions filter the data, even though the Floodlight activities still appear in the column selection tool. This is a known issue that we’ll fix in a future release.