Frequency Capping Discovery
Type of issue
This issue will server as a sounding board for members of the Identity PMC to discuss Publisher controlled frequency capping.
Description
The high level concept here is, publishers could store in local storage or cookies a count of impressions they have delivered to a given browser using a 1pc. The count can be further broken out by brand, campaign, etc. These dimensions are TBD, but almost any value in the bid response could be used. The counts could then be broadcast back to DSPs in subsequent bid requests.
Steps to reproduce
NA
Test page
NA
Expected results
From pub.com the below cookie is written:
Cookie: total_imps=116; nike=25; GMC=15; campaign_123=76;
Prebid.js would add the below to outbound bid requests
pbjs.setConfig({
"imps":{
"total_imps":116,
"nike":25,
"GMC":15,
"campaign_123":76
}
});
Actual results
NA
Platform details
NA
Other information
NA
Should we avoid indicating a storage medium preference at this point so we don't get buried by initial implementation concepts?
Looks like pretty nice fingerprint data - can we scope it by DSP in some way? You can only get out what you put in? We don't want and need to make frequency capping work across DSP/buyers. And sorry if I am missing some core understanding on how this should work.
Notes from Privacy and Identity committee August:
- Possible preqs?
- Inclusion of Adomain
- (potentially provides some mechanism for campaign tracking)
- Unlocks universal programmatic rule sets?
- Mechanism for knowing who wins in real time
- Campaign ID?
@komplettsystem at the moment this is mostly acknowledgement that there is a significant problem that we would like to try and solve, and we're looking to discuss ideas and options for methods to solve it.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
How to transmit these data securely to only the advertiser in question appears to be an open encryption and standards issue. Technology such as ( https://mice.cs.columbia.edu/getTechreport.php?techreportID=483 ) would seem to be required. Perhaps we close this issue until a different forum (eg IAB PET group) selects that technology? Or does someone in these forums want to build out a POC?
@jdwieland8282 do you think we should close this for housekeeping until progress on this happens or we're unblocked for development?
WICG Shared Storage proposals seem quite relevant
WICG Shared Storage proposals seem quite relevant
WICG Shared Storage Explainer: https://github.com/WICG/shared-storage#shared-storage-api-explainer
Section of the explainer focused on frequency capping: https://github.com/WICG/shared-storage#frequency-capping
And Shared Storage demo: https://shared-storage-demo.web.app/
@jdwieland8282 it doesnt appear there is much momentum here? Should we close in favor of specific proposals. It doesnt seem we want to put seen adomains on the open market request