Additional Bidding Strategy Fail Drop Reasons Added to Bid Decision Report

What is it? Detailed drop reasons for bidding strategy fails are now included in the Bid Decision Report to add more clarity to "no agent bid" drop results. The following drop reasons are being added:

• BIDDING_AGENT_THROTTLED
• BIDDING_AGENT_FAILED
• BIDDING_AGENT_TIMEOUT
• BIDDING_AGENT_BAD_RESPONSE
• BIDDING_AGENT_OK_NO_BODY
• BIDDING_AGENT_NO_BIDS
• BIDDING_AGENT_NOT_SELECTED

The NO_AGENT_BID drop reason has been renamed to BIDDING_AGENT_NOT_SELECTED. Including these additional details about bidding strategy fails will help those with a custom bidding agent to better troubleshoot..

How am I affected? This feature is automatically available for all accounts; no action is required.

Resource(s): Bid Decision Report

Internet Service Provider Targeting Included in Carrier Targeting

What is it? Carrier targeting now includes Internet Service Providers (ISPs) in addition to mobile carriers. This can be accessed in Line Item Targeting in Line Item > Targeting > Platform > Carrier. Additionally, ISP data is available in the platform_carrier field in auction, bid, and win logs.

How am I affected? This feature is automatically available for all accounts; no action is required.

Resource(s): Platform Targeting

OneStrata Digital and FreeWheel DSP Integration

What is it? An API integration between OneStrata Digital and FreeWheel DSP that allows for streamlined workflows between the two systems:

• Advertisers and Campaigns created in OneStrata Digital automatically sync with FreeWheel DSP
• FreeWheel DSP campaign delivery data is viewable within OneStrata Digital
• Invoices from FreeWheel DSP can be pulled into a centralized financial platform

A new field, Invoice ID, will appear on linked OneStrata Digital <> FreeWheel DSP campaigns, so customers can consolidate invoice details for a holistic view of campaign fees and reduce manual effort to match invoices from disparate sources.

How am I affected? This feature is automatically available for all customers using OneStrata to push campaigns to FreeWheel DSP; no action is required. Customers that do not use OneStrata will see no impact.

Resource(s): Link a Cost Line to a FreeWheel DSP Campaign, Map a FreeWheel DSP Advertiser

Sellers.json and Schain Added to Reporting

What is it? Sellers.json and the SupplyChain Object (schain) are available in reporting, to assist buyers in understanding who is selling the inventory their campaigns deliver on.

• Sellers.json is a set of new dimensions available in the App, Domain, and Inventory Reports, Metamarkets, as well as the following logs: auction, bid, win, ghost, antenna, and streaming joined win logs. The sellers.json fields include: 

  • Dimension	Definition
    Sellers.json Seller Status	Whether a match was found when looking up the Publisher ID in sellers.json files. Values include: Unknown: No Publisher ID was passed in the bid request to lookup against sellers.json Seller Not Found: No match was found to the Publisher ID passed in the bid request  Authorized: This seller is authorized based on the sellers.json table, but the seller type cannot be identified for various reasons.   Authorized - Publisher: A match was found to the Publisher ID and the Seller Type is "Publisher" Authorized - Intermediary: A match was found to the Publisher ID and the Seller Type is "Intermediary" Authorized - Both: A match was found to the Publisher ID and the Seller Type is "Both"
    Sellers.json Seller Name	Seller Name listed on the sellers.json file.
    Mapped Seller Name	The Seller Name listed in the in the sellers.json file mapped to a taxonomy to consolidate into a single standardized name. The taxonomy does not account for all sellers names. The most commonly passed seller names have been prioritized. It's recommended to use both the Seller Name and Mapped Seller Name dimensions.
    Sellers.json Seller Type	The value pulled from the sellers.json file. Options include: Publisher: The inventory sold through this account is owned by the named entity and the advertising system pays them directly. Intermediary: The inventory sold through this account is not owned by the named entity, or the advertising systems does not pay them directly. Both: Both publisher and intermediary inventory are transacted by this account.

• Schain fields allow users to view every entity involved in the selling and reselling of an ad opportunity. These fields are available in auction, win, bid, and antenna equivalents logs. The schain fields include:

  • Field Name	Definition
    SCHAIN_COMPLETE	Flag indicating whether the chain contains all nodes involved in the transaction leading back to the owner of the site, app or other medium of the inventory.
    SCHAIN_NODE_ASI	The canonical domain name of the SSP, Exchange, Header Wrapper, etc. system that bidders connect to. This should be the same value as used to identify sellers in an ads.txt file if one exists.
    SCHAIN_NODE_DOMAIN	Business domain name of the entity represented by this node. This value is optional and is not included if it exists in the advertising system’s sellers.json file.
    SCHAIN_NODE_HP	Indicates whether this node will be involved in the flow of payment for the inventory.
    SCHAIN_NODE_NAME	Name of the company (the legal entity) that is paid for inventory transacted under the given seller_id.
    SCHAIN_NODE_RID	OpenRTB RequestId of the request as issued by this seller.
    SCHAIN_NODE_SID	Identifier associated with the seller or reseller account within the advertising system. For example, 1234.
    SCHAIN_NODE_INTERNAL_SID	The SCHAIN_NODE_SID field augmented to include the exchange handle. For example, stv/1234.
    SCHAIN_VERSION	Version of the supply chain specification in use.

These features will help validate the legitimacy of sellers, give insight into where ads are serving, and increase campaign efficiency by providing insight into the most direct inventory paths.

How am I affected? This feature is automatically available for all accounts; no action is required.

Resource(s): Sellers.json and Schain Reporting, Logs

Updated Dimensions in Reporting

What is it? The following updates have been made to reporting:

• The Ads.txt dimension has been added to the Domain report. 
• The Open Market Bid Price dimension in the Bids & Wins dashboard in Metamarkets has been renamed to Bid Price, as it applies to both Open Market and Deal impressions.
• In Metamarkets, when data is unavailable in a bid request for the following fields, its value will now appear as "Not Available":
  • In the Auctions Dashboard:
    • VPAID
    • MRAID
    • App or Site
    • App/Site ID
    • Auction Type
    • Open Marketplace Bid Floor Bucket
    • Interstitial
    • Has Privacy Policy
    • DMA
  • In the Bids & Bids and Wins Dashboard:
    • Bid Floor Bucket 
    • Ad size
• The following dimensions have updated value names:
  • Video Playback Method:

    • Previous Value Name	Updated Value Name
      Auto-Play Sound On	Autoplay Sound On
      Auto-Play Sound Off	Autoplay Sound Off
      Viewport Auto-play Sound On	Viewport Sound On
      Viewport Auto-play Sound Off	Viewport Sound Off
      Click-to-Play	Click to Play
      Mouse-Over	Mouse Over

• • Video Placement:

    • Previous Value Name	Updated Value Name
      In-Stream	In-Stream Placement
      Interstitial	Interstitial/Slider/Floater
      In-Article	In-Article Placement
      In-Feed	In-Feed Placement
      In-Banner	In-Banner Placement

• Lastly, the following field names have been updated in Report Builder to provide more clarity:

  • Previous Field Name	Updated Field Name
    Ads txt	Ads.txt
    App ads txt	App-ads.txt
    Clickthrough Conversions	User ID and Postback Clickthrough Conversions
    Viewthrough Conversions	User ID and Postback Viewthrough Conversions

How am I affected? These features are automatically available for all accounts; no action is required.

Resource(s): Analytics Data Dictionary