This is a new API for measuring conversions (e.g. purchases) and attributing them to clicked ads, without using cross-site persistent identifiers like third party cookies.
Link to “Intent to Prototype” blink-dev discussionhttps://groups.google.com/a/chromium.org/d/msg/blink-dev/7B0ldtZR_68/GjLBu0n4DgAJ
Link to “Intent to Experiment” blink-dev discussion
Goals for experimentation
For a continuation of the trial, we still hope to see that the measurement data made available through the API produces comparable results to existing click through measurement solutions on the web.
We would like to see that Chrome 94 addresses the reporting issue documented here:
We'd like to extend the origin trial for one additional milestone, continuing through M94. The experiment has been running since M86.
Any risks when the experiment finishes?
This API is only additive and does not affect any existing state. Current conversion measurement solutions will work as expected with and without the API, so we don’t believe there are any risks.
All web-visible names of the API were modified in Chrome 92 which mitigated burn in risk as developers needed to update their implementation to continue experimenting.
We have previously requested an exception to the .5% page load usage limit for Origin Trials. Page load usage is currently around .92% for the feature.
Reason this experiment is being extended
There are a number of new internal partners experimenting with the API. Chrome 93 has a shorter than normal Stable lifetime, with Stable starting on Aug 31st, and 93 OT tokens expiring on September 14th, only giving two weeks to experiment. We would like to allow a bit longer for experimentation.
Ongoing technical constraints
Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?
Link to entry on the feature dashboard