WICG / attribution-reporting-api

Attribution Reporting API
https://wicg.github.io/attribution-reporting-api/
Other
359 stars 171 forks source link

event_attribution_reporting_clicks.md is very hard to follow. #188

Open MattMenke2 opened 3 years ago

MattMenke2 commented 3 years ago

I'm trying to read this doc, and find it very hard to understand.

It talks a lot about "triggering attributions" without first defining "triggering" There is a "triggering attribution" section...which doesn't define the term.. The doc also talks about "sources" - it's unclear what a source is. I think the doc needs a high level overview, so it's clearer how things plug in. As-is, I'd probably to read the doc 3 or 4 times to make sense of it.

This is up for security review this week, and I just don't have the time to repeatedly wade through the doc to understand it.

csharrison commented 3 years ago

@apasel422 do you think you could take a look at this? I know you were discussing simplifying this doc given a lot of information is in the spec now.

apasel422 commented 3 years ago

I'll take a look.

apasel422 commented 3 years ago

CC @maudnals.

maudnals commented 3 years ago

@apasel422 Below is an (unreviewed) paragraph taken from a developer doc I'm drafting now.

Maybe some of it could be reused here, with one caveat: the terms are defined in the context of advertising, and IIRC the explainers here in this repo aim at remaining generic / to some extent use-case-agnostic.

The fix for this may be to add "for example, in an advertising context" or so at relevant places in the text below.


Terminology

Aleksei-Gorbushin-at-Walmart commented 2 years ago

It looks a little clumsy to me anyway.

Could we use "impression" and "click" instead of "event" and "navigation"?

maudnals commented 2 years ago

+1 to this, this was flagged in https://github.com/WICG/attribution-reporting-api/issues/374 in the past as well.