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.

Sign up for GitHub

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

Update guidance about first party identifier #187

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update guidance about first party identifier #187

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 7 additions & 8 deletions bidding-auction-services-payload-optimization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,12 +116,12 @@ compressed [`ProtectedAuctionInput`][5] request payload.

#### Step 1

**The buyer creates `interest groups` based on `first party advertiser cookie`**
**The buyer creates `interest groups`**

Buyers running B&A services must ensure that `trustedBiddingSignalKeys` in
each `interest group` only include a `first party (1p) advertiser cookie`. This
would facilitate fetching data required by generateBid() for the interest group in
`trustedBiddingSignals` from buyer's key / value service.
It is recommended to buyers running B&A services to use a first party identifier (for example `first party user ID for
advertiser site or app`) for `trustedBiddingSignalKeys` and / or `interest group name`.
This would facilitate fetching data required by generateBid() for the
interest group in `trustedBiddingSignals` from buyer's key / value service.

#### Step 2

Expand Down Expand Up @@ -182,7 +182,7 @@ The only information included in each interest group are the following. Note tha
browser will not include `adRenderId(s)` or `adComponentRenderId(s)` or `userBiddingSignals`
or any other information in interest groups.
* interest group `name`
* `trustedBiddingSignalKeys`: Note that this must be a first party advertiser cookie
* `trustedBiddingSignalKeys`: It is recommended to be an identifier such as `first party user identifier per advertiser site (or app)`
* [browserSignals][18]

##### Specification for browser signals
Expand Down Expand Up @@ -246,8 +246,7 @@ The browser will not include `userBiddingSignals` information in `interest group
are sent in `ProtectedAuctionInput` request payload.

The `userBiddingSignals` information per `interest group` can be made available in
`trustedBiddingSignals`, if `first party advertiser cookie` is used as
`trustedBiddingSignalKeys`.
`trustedBiddingSignals`.


#### Step 8
Expand Down