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
It will be useful to have “aggregated” and privacy safe data about interest groups to be accessed by DSP’s. These signals can be consumed by buyers offline for audience modelling and Similar Audiences with buyer specific utility.
How?
Suppose, per_buyer_signals contains certain information about the webpage making a contextual adrequest. For example it could be some embeddings derived from the publisher website and supplied via per_buyer_signals for each ad-query. If Buyers can use AggregatedReporting API within generate_bid() function then they can create a model of an IG by implementing generate_bid(interest_group, auction_signals, per_buyer_signals, trusted_bidding_signals, browser_signals) in the following fashion.
generate_bid(interest_group, auction_signals, per_buyer_signals, trusted_bidding_signals, browser_signals) {
...
...
// Call Aggregate Reporting API with IG as key and DSP provided page embeddings as value
const entryHandle = window.writeOnlyReport.get(interest_group.name);
entryHandle.set('embedding_index_0', per_buyer_signals["mydsp.com"].embedding_float_from_per_buyer_signals_0);
entryHandle.set('embedding_index_1', per_buyer_signals["mydsp.com"].embedding_float_from_per_buyer_signals_1);
…
entryHandle.set('embedding_index_n', per_buyer_signals["mydsp.com"].embedding_float_from_per_buyer_signals_n);
// Entries can be configured to report after a given time.
entryHandle.reportAfter(kMsecPerHour);
return {'ad': ad_object, 'bid': bid_value, 'render': render_url};
}
Thus, the final reports would contain an aggregated embedding for interest groups based on ad-impression events.
Questions
Can you clarify if usage of AggregateReporting() in this fashion will be allowed by the API?
The text was updated successfully, but these errors were encountered:
Private Aggregation API is accessible from Protected Audience bidding, scoring and reporting scripts. I'm closing this issue as I think the concern was addressed. Feel free to reopen or file another if you have further concerns.
Aim
It will be useful to have “aggregated” and privacy safe data about interest groups to be accessed by DSP’s. These signals can be consumed by buyers offline for audience modelling and Similar Audiences with buyer specific utility.
How?
Suppose, per_buyer_signals contains certain information about the webpage making a contextual adrequest. For example it could be some embeddings derived from the publisher website and supplied via per_buyer_signals for each ad-query. If Buyers can use AggregatedReporting API within generate_bid() function then they can create a model of an IG by implementing generate_bid(interest_group, auction_signals, per_buyer_signals, trusted_bidding_signals, browser_signals) in the following fashion.
Thus, the final reports would contain an aggregated embedding for interest groups based on ad-impression events.
Questions
Can you clarify if usage of AggregateReporting() in this fashion will be allowed by the API?
The text was updated successfully, but these errors were encountered: