It seems that the Header Bid Expert shows way to high measurements when a delivery through yieldlab is done.
The measurement is correct as long, as only the header bidding call is done, but when the delivery call is added and the counting pixels are fired it seems, that they are all included in the measurements, ending in a way to high time span.
To reproduce it:
open the developer tool bar of your browser and go to the network tab
If you only see a /yp call than the given time span will most likely be ok. But once an actual ad is delivered with a /d call, than the timespan will be far to wide.
It seems that the Header Bid Expert shows way to high measurements when a delivery through yieldlab is done.
The measurement is correct as long, as only the header bidding call is done, but when the delivery call is added and the counting pixels are fired it seems, that they are all included in the measurements, ending in a way to high time span.
To reproduce it:
If you only see a /yp call than the given time span will most likely be ok. But once an actual ad is delivered with a /d call, than the timespan will be far to wide.
If you got problems getting a delivery, I recommend visiting https://www.otto.de/ or https://www.zalando.de/herren-home/. Just look at some items of these stores and you will hopefully get their ads.