こんにちはTAG!

I'm requesting a TAG review of:

• Name: Event-Level Click Conversion Measurement API
• Specification URL: N/A
• Explainer (containing user needs and example code)¹: url
• GitHub issues (if you prefer feedback filed there): url
• Tests: N/A
• Primary contacts (and their relationship to the specification): @csharrison, @michaelkleber, @johnivdel

Further details:

• Relevant time constraints or deadlines: We’d like to discuss this at TPAC (Sept 16, 2019). Other than that no hard time constraints.
• I have read and filled out the Self-Review Questionnare on Security and Privacy. The assessment is here.
• I have reviewed the TAG's API Design Principles
• The group where the work on this specification is: No group yet

We recommend the explainer to be in Markdown. On top of the usual information expected in the explainer, it is strongly recommended to add:

• Links to major pieces of multi-stakeholder review or discussion of this specification: N/A
• Links to major unresolved issues or opposition with this specification:
  • https://github.com/csharrison/conversion-measurement-api/issues/6

You should also know that...

We’re still very early stage here, just looking to get TAG review earlier rather than later. We also have some nascent ideas in https://github.com/csharrison/conversion-measurement-api/blob/master/AGGREGATE.md but those should be reviewed separately since it’s definitely not ready yet.

We'd prefer the TAG provide feedback as (please select one):

• open issues in our GitHub repo for each point of feedback
• open a single issue in our GitHub repo for the entire review
• leave review feedback as a comment in this issue and @-notify [github usernames]

---

Please preview the issue and check that the links work before submitting. In particular, if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document.

¹ For background, see our explanation of how to write a good explainer.