Skip to content
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

[DSP] Frequency Capping using Shared Storage API in Generate Bid #133

Open
vanshika0812 opened this issue Feb 1, 2024 · 1 comment
Open

Comments

@vanshika0812
Copy link

As a Buyer (DSP), the browserSignals sent as part of the generateBid function currently include prevWinsMs data, which can be utilised for on-device frequency capping at the IG level only.

Regarding implementing on-device frequency capping using cross-site data , I have the following questions:

Q1: Since Shared Storage enables us to make informed decisions based on cross-site data, can I read from shared storage within the generateBid (which is already running in a worklet) to apply ad-decision/business logic (such as Frequency Capping) based on cross-site information and select a subset of ads?

Q2: Additionally, can I write to the Shared Storage upon ad rendering?

@jkarlin
Copy link
Collaborator

jkarlin commented Feb 1, 2024

Hi, thanks for asking.

Q1: Since Shared Storage enables us to make informed decisions based on cross-site data, can I read from shared storage within the generateBid (which is already running in a worklet) to apply ad-decision/business logic (such as Frequency Capping) based on cross-site information and select a subset of ads?

No, it is not possible to read from shared storage within bidding worklets.

Q2: Additionally, can I write to the Shared Storage upon ad rendering?

Yes, you can write to Shared Storage from virtually anywhere, including bidding worklets, reporting worklets, and from the rendered creative.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants