-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prebid.js should provide event timelogs #30
Labels
Comments
mkendall07
added a commit
that referenced
this issue
Sep 15, 2015
bid responses now have the following: -requestTimestamp -responseTimestamp -timeToRespond (in ms)
marian-r
added a commit
to aol/Prebid.js
that referenced
this issue
Sep 23, 2016
…pport to release/1.2.0 * commit '149bf30f4fab51906fbb91bb629b958547bb4833': Fixed ES6 features which require a polyfill
kd-appier
added a commit
to appier/Prebid.js
that referenced
this issue
May 30, 2019
…rebid#30) [PMP-4591] Refined appier analytics testing Approved-by: Jen-Yee Hong <pcman.hong@appier.com>
ChrisHuie
pushed a commit
that referenced
this issue
Apr 15, 2024
* refactors interpretResponse * updates comment * simpler * removes unnecessary comment * removes more unnecessary comments * revert ttl * reverts ttl test values * revert some || changes * removes comments --------- Co-authored-by: “Nick <“nick.llerandi”@kargo.com>
DecayConstant
pushed a commit
to mediavine/Prebid.js
that referenced
this issue
Jul 18, 2024
* refactors interpretResponse * updates comment * simpler * removes unnecessary comment * removes more unnecessary comments * revert ttl * reverts ttl test values * revert some || changes * removes comments --------- Co-authored-by: “Nick <“nick.llerandi”@kargo.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a reporting service, I'd like to track all data used in the below analysis, so that I can help the publisher understand the performance of header bidding.
http://prebid.org/blog/how-many-bidders-for-header-bidding/
The text was updated successfully, but these errors were encountered: