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
This issue is to provide scoping around a new feature to capture the "view time" for a particular ad when it's viewed. This would require the server to store how long an ad has been viewed and the client to send updates on how long an ad was viewed for. We think that advertisers may find this valuable and might even pay more when ads are viewed for longer times (static ads providing revenue similar to video ads). Likewise, publishers with more "view time" per view should be compensated more than just a straight CPM number. This might also enable a change to where ads change periodically (eg. readthedocs/ethical-ad-client#24) for SPAs or long-viewed pages.
Changes to the server
The server would need a place to record the view time for a particular "view". This could probably just be a positive integer field (seconds? milliseonds?) on the Offer model.
The server would need an API to increment/set the view time for a particular "view". We should probably cap any particular view at a maximum of 30s.
Our reporting interface could show aggregated view time for advertisers and "view time per view" or some other similar metric to allow comparing across advertisers.
For publishers, we should show the average view time in the reporting and overview screens. This would allow comparing publishers.
Changes to the client
The client will need to start a timer once the ad is in the viewport. Whenever the ad leaves the viewport, the timer stops.
The client will need to send one or more updates about how much an ad has been viewed. Ideally, this would be onunload but it could send it "periodically" (exponential backoff up to a max of maybe 30s) if that isn't reliable. We want to be very careful of performance here. Ads have historically been bad for web performance and we don't want to make it worse.
The text was updated successfully, but these errors were encountered:
This issue is to provide scoping around a new feature to capture the "view time" for a particular ad when it's viewed. This would require the server to store how long an ad has been viewed and the client to send updates on how long an ad was viewed for. We think that advertisers may find this valuable and might even pay more when ads are viewed for longer times (static ads providing revenue similar to video ads). Likewise, publishers with more "view time" per view should be compensated more than just a straight CPM number. This might also enable a change to where ads change periodically (eg. readthedocs/ethical-ad-client#24) for SPAs or long-viewed pages.
Changes to the server
Changes to the client
onunload
but it could send it "periodically" (exponential backoff up to a max of maybe 30s) if that isn't reliable. We want to be very careful of performance here. Ads have historically been bad for web performance and we don't want to make it worse.The text was updated successfully, but these errors were encountered: