Given the discussions on #30 and #56, would make sense to update the URL endpoint naming to reflect the same principles? Namely, the other attributes have dropped the "ad" nomenclature.

For the Event-level Conversion Measurement API we are proposing using the following URL endpoints:

/.well-known/trigger-attribution for the path used to trigger attribution for a click.

/.well-known/report-attribution for the path where the report will be sent.

Currently, the same path is used for both triggering attribution and sending reports, /.well-known/ad-click-attribution. Assigning separate paths for these would make their usage/meaning more straightforward when being used across different context.

cc @johnwilander @csharrison