You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While doing a review of mobile tracking for the docs site, several gaps were discovered in the tracking implementation:
The "Prebid-Rendered" scenarios don't track either burl or nurl.
The mediation scenarios don't track either burl or nurl.
In PUC scenarios, there's a discrepancy between the handling of burl and the PBS win event. The burl uses MRAID to trigger on viewability, which can be quite different from the numbers reported by the PBS win event.
In addition, the Prebid.js team is discussing an expansion of tracking abilities in prebid/Prebid.js#12216 . Here's a multi-part proposal to address tracking:
Prebid SDK
Enhance the Prebid-Rendered and Mediation scenarios to support firing the nurl and burl. The notice URL (nurl) should be treated as a "win url" -- fired on the ad server choosing the Prebid ad. The billing URL (burl) should be fired when viewable by OMSDK's definition of "isViewable". (Someone needs to decide what percent viewable counts here.)
Enhance all tracking scenarios (Bidding-Only, Prebid-Rendered, Native, and Mediation) to support looking beyond burl and nurl. Loop through through the eventtrackers array:
If type: 500, treat it per the current PBS win event logic
If type: 1, treat it as a burl - add a pixel when in-view 10%
If type: 2, treat it as a burl - add a pixel when in-view 50%
If type: 3, treat it as a burl - add a pixel when in-view 100%
Prebid Server
PBS currently does the following:
For banners, when analytics is enabled for an account, it returns seatbid.bid.ext.prebid.events.{win,imp} in the ORTB
For banners and native when analytics is enabled and PBS is told to cache the bid (ext.prebid.cache.bids), it stores a field in the cache called wurl along with nurl. This wurl (win url) field is Prebid-specific and is utilized by the PUC when it retrieves bids from the cache.
For video, when analytics is enabled, it adds an tag to the VAST before returning or caching it.
A new account-level configuration will be added that will change the core tracking behavior. Suggested name is auction.events.eventtracker_support.
If auction.events.eventtracker_support:false (the default) the current tracking behavior continues.
If auction.events.eventtracker_support:true:
seatbid.bid.ext.prebid.events is no longer emitted
instead, the seatbid.bid.ext.eventtrackers array is created or appended. Example below.
wurl is no longer stored with other bid data
instead, all of the bid's eventtrackers (including any PBS-generated entries) are added to the cached bid as eventtrackers in the ORTB array-of-objects format.
video tracking does not change
When in the new tracking mode, PBS emits these ORTB objects instead of the existing seatbid.bid.ext.prebid.events:
Instead of just looking for wurl in the PBS response, the PUC should also look through the eventtrackers array:
If type: 500, treat it per the current wurl logic
If type: 1 and MRAID is present to determine viewability, treat this URL the same as the burl is currently treated in that scenario.
Prebid.js
Instead of just looking for seatbid.bid.ext.prebid.events.win in the PBS response, Prebid.js also looks through the eventtrackers array:
If type: 500, treat it per the current pbsWurl logic
If type: 1, the ideal would be to append a pixel to the iframe after injecting the creative body. Unclear whether this is as straightforward as it sounds.
The text was updated successfully, but these errors were encountered:
While doing a review of mobile tracking for the docs site, several gaps were discovered in the tracking implementation:
burl
ornurl
.burl
ornurl
.burl
and the PBS win event. The burl uses MRAID to trigger on viewability, which can be quite different from the numbers reported by the PBS win event.In addition, the Prebid.js team is discussing an expansion of tracking abilities in prebid/Prebid.js#12216 . Here's a multi-part proposal to address tracking:
Prebid SDK
type: 500
, treat it per the current PBS win event logictype: 1
, treat it as aburl
- add a pixel when in-view 10%type: 2
, treat it as aburl
- add a pixel when in-view 50%type: 3
, treat it as aburl
- add a pixel when in-view 100%Prebid Server
PBS currently does the following:
wurl
along withnurl
. Thiswurl
(win url) field is Prebid-specific and is utilized by the PUC when it retrieves bids from the cache.A new account-level configuration will be added that will change the core tracking behavior. Suggested name is
auction.events.eventtracker_support
.auction.events.eventtracker_support:false
(the default) the current tracking behavior continues.auction.events.eventtracker_support:true
:eventtrackers
in the ORTB array-of-objects format.When in the new tracking mode, PBS emits these ORTB objects instead of the existing seatbid.bid.ext.prebid.events:
The eventtrackers are cached in PBC along with other bid metadata:
PUC
Instead of just looking for
wurl
in the PBS response, the PUC should also look through the eventtrackers array:type: 500
, treat it per the currentwurl
logictype: 1
and MRAID is present to determine viewability, treat this URL the same as theburl
is currently treated in that scenario.Prebid.js
Instead of just looking for
seatbid.bid.ext.prebid.events.win
in the PBS response, Prebid.js also looks through the eventtrackers array:type: 500
, treat it per the current pbsWurl logictype: 1
, the ideal would be to append a pixel to the iframe after injecting the creative body. Unclear whether this is as straightforward as it sounds.The text was updated successfully, but these errors were encountered: