attribution-reporting-api icon indicating copy to clipboard operation
attribution-reporting-api copied to clipboard

Source Event ID Usage

Open aroy-nextdoor opened this issue 1 year ago • 5 comments

Is it permissible for an adtech/platform to pass creative id inside source_event_id so that it can be used an aggregatable dimension via event level reports?

aroy-nextdoor avatar Apr 05 '24 18:04 aroy-nextdoor

@aroy-nextdoor The source_event_id is allowed to encode an arbitrary information about the ad impression, including things like creative id. Just to clarify, are you asking about collecting event-level reports to get aggregated data on a per creative id level? Thanks.

linnan-github avatar Apr 08 '24 14:04 linnan-github

Yes to collecting event-level reports to get aggregated data. Because there's not much other information you can get from the event level besides destination url and event type

aroy-nextdoor avatar Apr 08 '24 15:04 aroy-nextdoor

Thanks for the feedback. One question though, even if you choose to aggregate event-level reports by creative id, what additional information would you expect to get besides the total number of reports?

linnan-github avatar Apr 10 '24 14:04 linnan-github

Hi, an explicit advertiser id / pixel id would be nice, but we can always get that from creative id. Date the conversion occurred without giving an explicit timestamp, but maybe it's possible to encode that into the source event id.

aroy-nextdoor avatar Apr 10 '24 15:04 aroy-nextdoor

@aroy-nextdoor The event-level data contains limited information in order to limit trigger bits to prevent re-identification. Could clarify further what an event-level report in aggregate means for you and how do you plan to achieve that?

arpanah avatar Apr 15 '24 18:04 arpanah

Closing due to inactivity. Feel free to reopen if this is still an issue.

apasel422 avatar Aug 09 '24 15:08 apasel422