Hello,

We have use cases where we think of leveraging Shared Storage by writing to it during a call to generateBid in Protected Audience, and read from it later.

Calling sharedStorage.set seems possible in generateBid, but we are not sure to which origin Shared Storage writes to in this case, could you please clarify it?

According to the documentation: “the data is written to the origin of the browsing context that the call was made from”, but for generateBid it is unclear what the context is.

We think it’s either the publisher origin or the generateBid script origin. When we tested on a publisher page with the same origin as the bidding script, we see a write to Shared Storage. However, when the publisher origin differs from the script origin, we see no write at all to shared storage. Is this normal? Must the publisher page and bidding script have the same origin for generateBid to be able to write to shared storage?