Use cases for log-level files

Log-level files are granular data reports containing details for lost bids and impressions, associated with an agency's activity. 

There are a number of reasons why log-level files are useful:

  • Facilitate industry studies: Log-level files provide necessary granular data when an advertiser is participating in audits which require log-level data from SSPs. These studies often provide advertisers a view into their working media and total supply chain fees, which can be used to confirm fees are within an expected range.
  • Support agency audits: They enable access to data required when a holding company is undergoing a formal audit.
  • Fee transparency: Their use ensures fees are within a reasonable and expected range.
  • Performance optimization: They enable bidding history analysis to improve performance.

On this page:

Log-level files in Google Cloud Storage

Google adds log-level files to a Google Cloud Storage (GCS) bucket daily with a 2-month look back window. They then give  the bucket name to the agency and provide access to agency users by adding admin users in the Agency Seat user interface.

If an agency finds corrupt data in the file, it must be reported to Google within 30 days to ensure we can correct the data.

How to pull files from GCS

In the Google Cloud console, go to the Cloud Storage Buckets page.

  1. Go to Buckets.

  2. In the list of buckets, click the name of the bucket that contains the object you want to download.

  3. The bucket details page opens, with the "Objects" tab selected.

  4. Navigate to the object, which may be located in a folder.

  5. Click the download iconA picture of the download icon for Google Ads and Merchant Center associated with the object.

Your browser settings control the download location for the object.

Contents of GCS files

GCS files contain the following fields:

File type Field
Demand dimensions
  • DSP seat ID

  • DSP name

  • Deal ID

  • Transaction type

  • adomain

  • Creative ID

  • Technical Creative Format

Inventory dimensions
  • Pub code

  • Pub name

  • Environment (web vs. app) 

  • Inventory creative format: display vs. video

  • Platform: CTV, desktop, high end mobile device, tablets, other, uknown

  • URL (same level as what we share on bid requests)

  • App ID

  • Seller type

  • Country Code: Country code of bid request origin

  • Region

  • Metro

  • City

  • ZIP

  • Auction type

  • Supply Chain Object

  • Ads.txt validation

  • Floor price

  • Device type

  • OS type

  • Browser type

  • Placement_id in Google’s ID space

  • Ad size

Video specific
  • Pod Number (ad break position)
  • Pod Position. This will be shown only for won impressions
  • Video type
Price
  • Bid price
  • Minimum Bid to Win
  • Billed Price
  • Floor price
  • Post Auction Discount Applied
  • Publisher net revenue (only for won impressions and for publishers opted in)
Curation
  • Curation fee
  • Curation partner
Other
  • Time stamp (level of accuracy: seconds)
  • Bidder currency
  • Buyer exchange rate in USD
  • Bid request ID
  • Loss reason
  • Loss reason ID
  • Buyer Won the Auction (true/false)
Notes: 
  • There’s a 2-day delay for data to populate the files.

  • Files refer to all Google sell-side platform (SSP) spend on Ad Manager inventory.

  • Files are at the L1 Agency Seat level but there is a dimension for L1, L2, and L3 sub-accounts. The agency can download the daily files at the L1 level, filter the data to only a specific L2/L3 account, then share client-specific data with their client. 

  • Files are in a CSV format.

Was this helpful?

How can we improve it?

Need more help?

Try these next steps:

Search
Clear search
Close search
Main menu
13272644063343224894
true
Search Help Center
false
true
true
true
true
true
71030
false
false
false
false