Log level reporting provides advertisers with detailed bid request data for purchased inventory, with IP addresses and IFAs encrypted for privacy. Reports are delivered daily in UTC for the previous day’s activity. The user time zone offset is included in these reports and can be utilized to adjust the report time zone if needed. To receive log level reports, you must have either an AWS or Google Cloud account and have a scheduled report configured for delivery to s3 or Google Storage. Additionally, certain bid request fields contain numerical values that correspond to specific descriptions. The tables below provide mappings for device type, device connection type, geo type, video placement, video start delay, video protocol, and livestream values. For additional information can be found regarding the fields in the bid requests and bid responses in the Open RTB Specs. For bcat, refer to page 39, section 5.1 for a list of all IAB content categories.
Device Type
Value
Description
1
Mobile/Tablet
2
Personal Computer
3
Connected TV
4
Phone
5
Tablet
6
Connected Device
7
Set Top Box
Device Connection Type
Value
Description
0
Unknown
1
Ethernet
2
WIFI
3
Cellular Network – Unknown Generation
4
Cellular Network – 2G
5
Cellular Network – 3G
6
Cellular Network – 4G
Geo Type
Value
Description
1
GPS/Location Services
2
IP Address
3
User Provided (e.g. Registration data)
Video Placement
Value
Description
1
In-Stream
2
In-Banner
3
In-Article
4
In-Feed
5
Interstitial/Slider/Floating
Video Start Delay
Value
Description
> 0
Mid-Roll (Value indicates start delay in second)
0
Pre-Roll
-1
Generic Mid-Roll
-2
Generic Post-Roll
Video Protocol
Value
Description
1
VAST 1.0
2
VAST 2.0
3
VAST 3.0
4
VAST 1.0 Wrapper
5
VAST 2.0 Wrapper
6
VAST 3.0 Wrapper
7
VAST 4.0
8
VAST 4.0 Wrapper
9
DAAST 1.0
10
DAAST 1.0 Wrapper
Livestream
Value
Description
0
Non-live Content
1
Live Content
Create a Log Level Report:
Navigate to the Reporting tab and open the Custom Reporting dropdown section.
Click ‘New Custom Report’.
Select ‘Log Level’ as the Type.
Fill out the required report details.
Click ‘Save’.
To receive log level reports you must have either an AWS or Google Cloud account and have a scheduled report configured for delivery to s3 or Google Storage.
Below are the fields available to select when creating the report:
exchange: The SSP through which the auction or ad request is processed (e.g., Magnite, Index, etc).
auction_id: A unique identifier for the auction event, used to track the auction’s lifecycle.
imp_id: The impression id with in the context of the bid reques (several requests are sometimes sent at once)
imp_tagid: A unique identifier for the specific ad tag used to serve the impression.
imp_bidfloor: The minimum bid price set for the impression during the auction.
imp_bidfloorcur: The currency of the bid floor for the impression (e.g., USD, EUR).
seat_id: A unique identifier for the demand-side platform (DSP) or seat participating in the auction.
advertiser_id: A unique identifier for the advertiser in the ad ecosystem.
advertiser_code: A code associated with the advertiser for identification within the system.
campaign_id: A unique identifier for the specific advertising campaign.
campaign_code: A code used to identify and track the campaign.
line_id: A unique identifier for the line item within the campaign.
line_code: A code associated with the line item, often used for internal line management.
creative_id: A unique identifier for the creative or ad asset being served.
bid_price_millicents: The price the bidder is willing to pay for the impression, represented in millicents (1/1000 of a cent).
win_price_millicents: The price at which the impression was won, represented in millicents.
bid_timestamp: The timestamp indicating when the bid was placed in the auction.
win_timestamp: The timestamp indicating when the impression was won.
imp_timestamp: The timestamp indicating when the impression was served or displayed.
source_fd: Entity responsible for the final impression sale decision, where 0 = exchange, 1 = upstream source.
source_pchain: A chain or path of the sources involved in the bidding process for an impression.
creative_type: The type of creative, such as a display ad, video ad, audio ad, etc.
creative_categories: The IAB categories associated with the creative (e.g., “Comedy”, “Lifestyle”).
creative_duration: The duration of the creative (e.g., in seconds for an audio or video ad).
creative_domain: The domain that represents the brands website.
width: The width of the ad, typically for display or video creatives, in pixels.
height: The height of the ad, typically for display or video creatives, in pixels.
video_placement: placement type as specified in the open rtb 2.5 docs. 1:In-Stream, 2: In-Banner,3: In-Article,4: In-Feed,5: Interstitial/Slider/Floating
video_startdelay: Where in the feed the video plays . Specified in the open RTB 2.5 docs in the start delay section.
video_protocols: The vast protocol used for the imporessoin. Specified in the “Protocols” section in the open rtb 2.5 docs.
device_type: Integer that indicates the type of device used to view the ad (e.g., mobile, tablet, desktop). Specified in the open RTB 2.5 docs in the section “Device type”
device_connectiontype: The type of internet connection used by the device (e.g., Wi-Fi, 4G, 5G). Specified in the open RTB 2.5 docs in the section “Connection type”
device_ifa: A unique identifier for the device used for advertising purposes (e.g., Apple’s IDFA or Android’s AAID), hashed for privacy.
device_make: The manufacturer or brand of the device (e.g., Apple, Samsung).
device_model: The model of the device (e.g., iPhone 13, Galaxy S21).
geo_country: The country of the user or device (e.g., US, Canada).
geo_region: The region or state where the user or device is located.
geo_zip: The postal or ZIP code of the user or device.
geo_metro: The metropolitan area the user or device is located in.
geo_lat: The latitude of the user’s or device’s location.
geo_long: The longitude of the user’s or device’s location.
utc_offset: The difference between the local time and UTC time, used for time-based targeting.
geo_type: integer indicating how the geographic information was determined. This is specified in the open rtb 2.5 docs under “Location Type”
geo_ipservice: An identifier for the service used to determine the geographic location based on the IP address.
ip: The IP address of the user or device (sometimes anonymized for privacy).
ip_hashed: The hashed version of the IP address for privacy.
device_language: The language setting of the device (e.g., “en-US” for English – United States).
os: The operating system running on the device (e.g., iOS, Android).
os_version: The version of the operating system (e.g., iOS 14.4).
hw_version: The hardware version of the device, identifying the physical capabilities (e.g., model revision).
auction_type: The type of auction being used (e.g., first-price, second-price auction).
bcat: Blocked iab categories as specified by the publisher. The categories can be found in the open rtb 2.5 docs.
currency: The currency used in the ad transaction (e.g., USD, EUR).
user_agent: The user agent string sent by the browser or app, identifying the device and software.
browser: The browser used by the device to interact with the content (e.g., Chrome, Safari).
site_domain: The domain name of the website where the ad is being displayed.
app_bundle: The unique bundle ID of the mobile app where the ad is served.
app_id: The unique identifier for the mobile app.
app_domain: The domain of the site representing the app.
app_name: The name of the mobile app.
app_cat: The IAB category of the mobile app.
app_storeurl: The URL link to the app’s store page (e.g., Google Play Store or Apple App Store).
content_id: A unique identifier for the specific audio or video content being served.
content_livestream: Indicates if the content is part of a live stream (1 = live stream, 0 = not).
content_context: Additional context or metadata about the content (e.g., episode, special).
content_len: The length of the content (in seconds).
content_genre: The genre of the content (e.g., comedy, music, news).
content_episode: The specific episode number or identifier if the content is episodic (e.g., podcast episode).
content_season: The season number if the content is part of a series.
content_title: The title of the content (e.g., the name of the podcast episode, song, or show).
content_series: The broader series name or identifier for episodic content.
content_url: The URL where the content can be accessed or streamed.
content_cat: The category of the content (e.g., “music”, “talk show”, “news”).
content_network: The network that distributes the content.
content_channel: The specific channel through which the content is served.
content_contentrating: The content rating (e.g., PG, R, suitable for children, etc.).
content_producer_name: The name of the producer or creator of the content.
publisher_id: A unique identifier for the publisher or content provider.
publisher_name: The name of the publisher or content provider.
publisher_domain: The domain of the publisher’s website or content platform.
private_auction: Indicates whether the auction is private (1 = private, 0 = public).
deal_id: A unique identifier for the specific deal in a private auction.
deal_at: bid type for the deal (first or second price).
deal_bidfloor: The bid floor set for the deal in the private auction.
deal_bidfloorcur: The currency of the bid floor in the deal (e.g., USD, EUR).
data_cost: The cost of the data used for the campaign.
revenue: The total revenue generated from the ad.
total_cost: The total cost incurred in serving the ad.
fees: Fees associated with the ad transaction (e.g., platform or network fees).
chrome_conv: Conversion data specific to Chrome browser users (if applicable).
conv_pix_id: A unique identifier for the conversion pixel used to track the ad’s performance.
site_page: The specific page on the website where the ad was displayed.
foot_traffic_fee: Fees associated with generating foot traffic via the ad campaign.
data_comm: Commissions associated with data use or sharing in the campaign.
art_fee: Fees related to usage of ART custom audiences.
contextual_fee: Fees related to contextual targeting.
dcm_hosting_fee: Fees associated with hosting the ad via google’s ad server.
cc_fee: Credit card fees for processing transactions related to the campaign.
chalice_fee: Fees associated with Chalice (a platform or service used for campaign tracking or delivery).
campaign_name: The name of the campaign being tracked.
line_name: The name of the specific line item within the campaign.
creative_name: The name of the specific creative or ad asset used in the campaign.
advertiser_name: The name of the advertiser running the campaign.
Download the CTV log level report schema for a full list of available fields.
