Notification

Only available in Google Ad Manager 360.

Stream data logs (Alpha)

Ad server interaction log structure

This is an alpha feature and may not be available for your network.

Jump to: Log record structure | VMAP response with inline VAST | VMAP response without inline VAST | standalone VAST requests

DAI ad server interaction logs provide information about interactions with an ad server to get ads. This article outlines the log record structure and provides specific examples of how VMAP requests are represented in the log output files.

VMAP requests and log record structure

VMAP requests can return ad pods with inline VAST responses, without inline VAST responses, or with standalone VAST requests. The log record structure varies depending on the VMAP response.

It's not necessary for all pods in a given VMAP request to have either all inline VAST or all VAST redirect URLs. It's possible to have some with inline VAST and others with VAST redirect URLs.

Log record fields

All the ad server interaction logs records contain the following fields, in the mentioned order. However, some of the fields could be empty. You can learn more about the ad server interaction log fields.

"timestamp","entry_id","stream_id","network_code","content","vid","asset_key","pod_id","ad_server_host_name","response_time","response_type",
"response_code","row_type","vast_error_code","prefetch_stage","ad_position","ad_id","ad_system","ad_title","creative_id","creative_ad_id","universal_ad_id_registry","universal_ad_id_value","creative_duration"

Interaction log structure and fields

Fields may change with new releases. The client should always parse CSV files based on their header in case new fields are added or old fields are removed.

VMAP response with inline VAST

The tree structure for a sample VMAP response that returns inline VAST responses is shown here. The ad server interaction logs contain a record for each node in the above request/response tree.

The workflow for DAI ad sever interaction logs
  • P represents the primary VMAP request to the ad server. In this example, the primary VMAP request resulted in 2 inline ad pods (Pod-1 and Pod-2):

    • Pod-1 VAST has 2 wrapper ads (W-1 and W-2), and an inline ad (Ad-3):

      • Wrapper W-1 resulted in another wrapper (W-1-2), which returned an inline ad (Ad-1)
      • Wrapper W-2 resulted in an inline ad (Ad-2)
    • Pod-2 VAST has 2 wrapper ads (W-3 and W-4):

      • The request to wrapper W-3 timed out
      • Wrapper W-4 resulted in an inline ad (Ad-4)

Overall, Pod-1 resulted in 3 inline ads (Ad-1, Ad-2, and Ad-3); and Pod-2 resulted in 1 inline ad (Ad-4). If no errors are encountered, all of these leaf nodes should result in inline ads.

Leaf nodes always come from their ancestor responses.

For example, if a wrapper node contained an inline ad, the wrapper node record would show values in the ad_server_host_name, response_time, ad_system, and optionally the ad_position and ad_id fields. Each leaf node below the wrapper node will contain ad and creative information for each inline ad in the wrapper, specifically the ad_position, ad_id, ad_system, ad_title, creative_id, creative_ad_id, universal_ad_id_registry, universal_ad_id_value, and creative_duration fields.

Sample log records for a VMAP response with inline VAST

Given the sample stream:

  • Stream ID: 12345abc-0abc-1234-5678-9abc12345def
  • Network code: 12345678
  • CMS ID: 12345
  • Video ID: sample-vid

The node records might contain the following information:

Node: P

"1629979322398140","ZmMyNmUwMTAtOGU2Ni00ZjFkLTgzYmUtNTMxNDA3NGExMDgx","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","","pubads.g.doubleclick.net","0.058311558","VMAP","200","PRIMARY_REQUEST","","PREFETCH_STAGE_NONE","","","","","","","","",""

See the log record fields  

In the log record for the P node:

  • pod_id is empty ("") because it is a primary VMAP request
  • row_type is set to PRIMARY_REQUEST
  • ad_position is empty ("")
  • All ad and creative related information is empty ("")

Node: Pod-1

"1629979322398140","YTZlMjY5OTUtODliMy00MmI0LWE3OTUtMzc0NjAwZWViMjFm","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","midroll-1","","","","","AD_POD","","PREFETCH_STAGE_NONE","","","","","","","","",""

See the log record fields  

In the log record for the Pod-1 node:

  • pod_id is set to midroll-1 as provided by the ad server
  • row_type is set to AD_POD
  • ad_server_host_name field is empty ("") because the pod information is sent as inline VAST in the primary request
  • ad_position is empty ("")
  • All ad and creative related information is empty ("")

Node: W-1

"1629979322398140","MTRmN2YxNzgtNTY2NS00NGYyLWI5NDMtNGYzYjU5NGNhNTIz","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","midroll-1","pubads.g.doubleclick.net","0.048344558","VAST","200","WRAPPER","","PREFETCH_STAGE_NONE","1","4617730256","GDFP","","138228457230","","GDFP","138228457232",""

See the log record fields  

Node: W-1-2

"1629979322398140","YTFkYTA5YTItYzgxMC00NTUwLTlmZDctZjU0NjhjY2E5YWRm","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","midroll-1","pubads.g.doubleclck.net","0.042344558","VAST","200","WRAPPER","","PREFETCH_STAGE_NONE","1","4617730126","GDFP","","138228457230","","GDFP","138228457232",""

See the log record fields  

In the log record for the W-1-2 node:

  • ad_server_host_name is set to pubads.g.doubleclick.net
  • response_time is set to 0.042344558

Node: Ad-1

"1629979322398140","NTYyMDc4ZWYtODRkOS00MjFkLWI0NDEtNTY3OTEwZWVmZDQ0","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","midroll-1","","","","","INLINE","","PREFETCH_STAGE_NONE","1","4617730730","GDFP","LI first position in midroll","138228457232","","GDFP","138228457232","30.000000000"

See the log record fields  

Ad-1 is the inline ad contained in wrapper W-1-2. The log record for the Ad-1 node:

  • pod_id is set to midroll-1
  • row_type is set to INLINE
  • ad_server_host_name field is empty ("")
  • ad_position is set to 1

Node: W-2

"1629979322398140","MmEzNjAwMTUtZTE1MS00ZTA0LTlhNWYtYmJmMzFkY2Y3YmJi","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","midroll-1","pubads.g.doubleclick.net","0.034534558","VAST","200","WRAPPER","","PREFETCH_STAGE_NONE","2","4617730256","GDFP","","138228457230","","GDFP","138228457232",""

See the log record fields  

Node: Ad-2

"1629979322398140","MjIzYzYyNzItZWU0Zi00NGM2LWIxYWYtZTdiYjkxMzZmYWFl","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","midroll-1","","","","","INLINE","","PREFETCH_STAGE_NONE","2","4617858678","GDFP","LI second position in midroll","138228457232","","GDFP","138228457232","30.000000000"

See the log record fields  

Node: Ad-3

"1629979322398140","ZTgwMWVkYzYtMmNkMS00NmUyLTk1ZDMtMTA3ZTM0ODQ5Yjhj","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","midroll-1","","","","","INLINE","","PREFETCH_STAGE_NONE","3","4617858678","GDFP","LI third position in midroll","138228457232","","GDFP","138228457232","30.000000000"

See the log record fields  

Node: Pod-2

"1629979322398140","NTg1ZjMwZDQtYWY5Mi00ZjA0LWI0YTMtZWYxNmIwZTNkYWZj","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","preroll","","","","","AD_POD","","PREFETCH_STAGE_NONE","","","","","","","",""

See the log record fields  

Node: W-3

"1629979322398140","MGFmZTE4ZGYtZGZiYS00NTU1LWIzOWQtZjAyY2FhZmY4ZmM0","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","preroll","pubads.g.doubleclick.net","5.000000000","","","WRAPPER","301","PREFETCH_STAGE_NONE","0","","","","","","","",""

See the log record fields  

In the log record for the W-3 node:

  • vast_error_code is 301 because the request timed out
  • ad_position is set to 0
  • response_type is empty ("") because the request timed out

Node: W-4

"1629979322398140","MzI3NTg1Y2UtNGQyMy00NGE4LTg3YTItNGI2ZWJiMjM1YTQ1","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","preroll","pubads.g.doubleclick.net","0.042344558","VAST","200","WRAPPER","","PREFETCH_STAGE_NONE","1","4617730126","GDFP","","138228457230","","GDFP","138228457232",""

See the log record fields  

Node: Ad-4

"1629979322398140","MmEwZTU2YmMtOGQ4NS00NjgxLTlhMzEtMGQ2MmRhZTZhZjc0","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","preroll","","","","","INLINE","","PREFETCH_STAGE_NONE","1","4617731672","GDFP","LI first position in midroll","138228457232","","GDFP","138228457232","30.000000000"

See the log record fields  

In the log record for the Ad-4 node:

  • ad_position is set to 1

VMAP response without inline VAST (with VAST redirect URLs)

The VMAP response tree structure might not return inline VAST responses, but instead return VAST redirect URLs. Regardless of how a response is obtained (either through inline or redirect URLs), the overall nodes of the tree remain very similar.

The workflow for DAI ad server interaction logs without inline VAST

The only difference is when a response is obtained through a redirect, the corresponding AD_POD record would show values for the ad_server_host_name, response_time, and response_type fields to signify that an extra redirect was followed.

The following sample records have this additional information highlighted.

Sample log records for a VMAP response without inline VAST

Given the sample stream:

  • Stream ID : 12345abc-0abc-1234-5678-9abc12345def
  • Network code: 12345678
  • CMS ID: 12345
  • Video ID: sample-vid

The node records might contain the following information:

Node: Pod-1

"1629979322398140","Nzg0MDczZGMtNzA5Yy00ODllLTgxZTAtNDBlZmMyMmU5OTE5","12345abc-0abc-1234-5678-9abc12345def","12345678","12345","sample-vid","","midroll-1","adpodreq1.example.com","0.234231433","VAST","200","AD_POD","","PREFETCH_STAGE_NONE","","","","","","","",""

See the log record fields  

The child wrapper and ads nodes for VMAP responses without inline VAST have the same behavior as those with inline VAST

Standalone VAST requests

The workflow for DAI ad server interaction logs

Because most VAST ad requests are done on behalf of the DAI linear/live system, the cms_id and vid fields are not set on these records. Instead, the asset_key is set.

Sample log records for a standalone VAST request

Given the sample stream:

  • Stream ID : d07258a5-0abc-47e8-954d-e61fdaeb739c
  • Network code: 51636543
  • Asset key: asset_key

The node records might contain the following information:

Node: P

"1629979322398140","Nzg0MDczZGMtNzA5Yy00ODllLTgxZTAtNDBlZmMyMmU5OTE5","d07258a5-0abc-47e8-954d-e61fdaeb739c","51636543","","","asset_key","363","pubads.g.doubleclick.net","0.058311558","VAST","200","PRIMARY_REQUEST","","PREFETCH_STAGE_NONE","","","","","","","","",""

See the log record fields  

In the log record for the P node:

  • pod_id is empty ("") because it is a primary VMAP request
  • row_type is set to PRIMARY_REQUEST
  • ad_position is empty ("")
  • All ad and creative related information is empty ("")

Node: Pod-1

"1629979322398140","ZmMwYzA4N2ItNmUxOC00OTgxLWE4OTYtZmUxZTc1NGJlYThk","d07258a5-0abc-47e8-954d-e61fdaeb739c","51636543","","","asset_key","363","","","","","AD_POD","","PREFETCH_STAGE_NONE","","","","","","","","",""

See the log record fields  

In the log record for the P-1 node:

  • pod_id is set to 363 as per ad break notification
  • row_type is set to AD_POD
  • ad_server_host_name, response_time, and response_type fields are empty ("") because the pod information is obtained via the primary request
  • ad_position is empty ("")
  • All ad and creative-related info are empty ("")

Node: W-1

"1629979322398140","NWY4YTM0YTYtZTgwMy00YWYyLWE3N2UtNTVmMzA0ZDNhYzQ4","d07258a5-0abc-47e8-954d-e61fdaeb739c","51636543","","","asset_key","363","pubads.g.doubleclick.net","0.048344558","VAST","200","WRAPPER","","PREFETCH_STAGE_NONE","1","4617730256","GDFP","","138228457230","","GDFP","138228457232",""

See the log record fields  

Node: W-1-2

"1629979322398140","ZTY3ZWViZmUtNzg1Ny00MmFhLWE0ZTctNjE2YzQyNjA3NmQx","d07258a5-0abc-47e8-954d-e61fdaeb739c","51636543","","","asset_key","363","pubads.g.doubleclick.net","0.042344558","VAST","200","WRAPPER","","PREFETCH_STAGE_NONE","1","4617730126","GDFP","","138228457230","","GDFP","138228457232",""

See the log record fields  

Node: Ad-1

"1629979322398140","MGRjMzg3OTctM2U3NS00NWE4LWFkMWEtNzg4YTg1ZmE0NTI2","d07258a5-0abc-47e8-954d-e61fdaeb739c","51636543","","","asset_key","363","","","","","INLINE","","PREFETCH_STAGE_NONE","1","4617730730","GDFP","LI Sponsorship - CT External_Home - CH DFP - first position in midroll","138228457232","","GDFP","138228457232","30.000000000"

See the log record fields  

In the log record for the Ad-1 node:

  • pod_id is set to 363 as per ad break notification
  • row_type is set to INLINE
  • ad_server_host_name field is empty ("")
  • ad_position is set to 1

Node W-2

"1629979322398140","ZjcxMWYyOTYtMmI4ZC00NDYxLTg4NDUtZmFhNGUxM2NlZThl","d07258a5-0abc-47e8-954d-e61fdaeb739c","51636543","","","asset_key","363","pubads.g.doubleclick.net","0.034534558","VAST","200","WRAPPER","","PREFETCH_STAGE_NONE","2","4617730256","GDFP","","138228457230","","GDFP","138228457232",""

See the log record fields  

Node Ad-2

"1629979322398140","NjEyY2QxNWQtNDQ3NS00MzRiLWI2YTAtNTU5NDI5MDZiZTR","d07258a5-0abc-47e8-954hd-e61fdaeb739c","51636543","","","asset_key","363","","","","","INLINE","","PREFETCH_STAGE_NONE","2","4617858678","GDFP","LI Sponsorship - CT External_Home - CH DFP - first position in midroll","138228457232","","GDFP","138228457232","30.000000000"

See the log record fields  

Node Ad-3

"1629979322398140","NWJlMTQzY2EtOTI4NS00OWY0LThlZjYtODU1ZDk2YjU4Nzlm","d07258a5-0abc-47e8-954d-e61fdaeb739c","51636543","","","asset_key","363","","","","","INLINE","","PREFETCH_STAGE_NONE","3","4617858678","GDFP","LI Sponsorship - CT External_Home - CH DFP - first position in midroll","138228457232","","GDFP","138228457232","30.000000000"

See the log record fields  

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Main menu
18247650802629236707
true
Search Help Center
true
true
true
true
true
148
false
false
false
false