Open MattMenke2 opened 1 year ago
@MattMenke2, thanks for the feedback, we’ll try to make that section more clear. To your questions, IPA really begins before gathering reports when a Match Key Provider (MKP) sets a matchkey on the user agent. For gathering reports there are three steps:
get_encrypted_matchkey()
API and get back encrypted secret shares of the matchkey. This is done for both source and trigger events.The one other path than can happen instead of 1) for generating an encrypted matchkey is when a MKP creates reports for the events that happened on its own site. If a MKP knows who a user is, it could just create a report with the user's matchkey entirely serve-side and not need to call get_encrypted_matchkey()
.
Let me know if that still doesn't answer any of your questions.
For more details on how get_encrypted_matchkey()
might be implemented for browsers, see issue #25
The first sentence "collecting information on important events". It's unclear what events these are (source events, trigger events, both, something else?) and where information is being collected - is this a page's JS collecting source (trigger?) event information and passing it to the browser, the browser collecting this information (provided by sites) in a database, or this information being collected by a sever after reports have been triggered? The sentence does being with "IPA begins", but I don't know what the authors considered the "start" of IPA - is it the start of data being actually aggregated by a server, the start of one or both types of events, or what?
The section also mentions collecting information, collecting events, and collecting reports. It's not clear if these are one, two, or three distinct concepts.