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

Source Event ID Usage #1237

Open
aroy-nextdoor opened this issue Apr 5, 2024 · 5 comments
Open

Source Event ID Usage #1237

aroy-nextdoor opened this issue Apr 5, 2024 · 5 comments
Assignees
Labels
aggregate developer-input Question/feedback raised by a developer and posted here on their behalf for public discussion

Comments

@aroy-nextdoor
Copy link

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?

@apasel422 apasel422 added the developer-input Question/feedback raised by a developer and posted here on their behalf for public discussion label Apr 6, 2024
@linnan-github
Copy link
Collaborator

linnan-github commented Apr 8, 2024

@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.

@aroy-nextdoor
Copy link
Author

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

@linnan-github
Copy link
Collaborator

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?

@aroy-nextdoor
Copy link
Author

aroy-nextdoor commented Apr 10, 2024

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.

@arpanah
Copy link
Collaborator

arpanah commented Apr 15, 2024

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aggregate developer-input Question/feedback raised by a developer and posted here on their behalf for public discussion
Projects
None yet
Development

No branches or pull requests

4 participants