Thanks for the feedback report. It's great!! LGTM1 to extend the OT to M97
On Sat, Oct 30, 2021, 00:37 John Delaney <johni...@chromium.org> wrote: > > We're inclined to extend this OT, but wanted to quickly check in to see > if y'all have any interim results from the trial thus far. Are you > surveying developers? Is there some feedback you could perhaps aggregate to > give us a sense for how it's going? > > Most definitely! We have received a lot of great feedback from people > testing the API. In general we have been receiving two categories of > feedback from the Origin Trial: accuracy of API reports, feedback on > whether certain use-cases are met. > > See https://github.com/WICG/conversion-measurement-api/issues/201 for > some exemplary feedback. > > Feedback on accuracy: > > Testers have identified some differences between our API and cookie based > conversions, where the browser either doesn't send a report when expected / > or sends an unexpected. We are continuing to explore this space and are > making progress. > > See > https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting-data-clearing/ > which deep dives into learnings regarding data clearing from the OT. > > In Chrome 94 we changed the way that Chrome retries reports, and have > marked improvement in the accuracy of API reports as seen by some testers. > > In general, we are hearing that integrating/verifying the API comes with > its own set of challenges due to how different it is from the status quo. > We are actively collaborating to improve the API in this regard ( > https://github.com/WICG/conversion-measurement-api/issues/174) > > Use-case feedback: > > The other key area of feedback we are receiving is use-cases not > recoverable in the API. As developers have dug into the API, they have > raised changes the API will need to work as expected. > > Some examples: > > > - Adding coverage for ads which navigate using window.open > - https://github.com/WICG/conversion-measurement-api/issues/77 > - Allowing attribution to be scoped more granularly than "site" > - https://github.com/WICG/conversion-measurement-api/issues/115 > - Adding more ergonomic ways to provide data to the API > - https://github.com/WICG/conversion-measurement-api/issues/261 > > We still have active development to cover cases like these which come up > in practice. > > Please let me know if there is anything specific you would like us to > speak to! > > John > > On Thursday, October 28, 2021 at 3:34:33 PM UTC-4 Alex Russell wrote: > >> hey John, >> >> In line with the policy we adopted earlier regarding trials in this >> bucket of features [1], I appreciate the reporting around total page loads. >> >> We're inclined to extend this OT, but wanted to quickly check in to see >> if y'all have any interim results from the trial thus far. Are you >> surveying developers? Is there some feedback you could perhaps aggregate to >> give us a sense for how it's going? >> >> Thanks, >> >> Alex >> >> [1]: >> https://groups.google.com/a/chromium.org/g/blink-dev/c/c4noVavt-uM/m/OhB3cd0EAgAJ >> >> On Thursday, October 21, 2021 at 6:45:39 AM UTC-7 John Delaney wrote: >> >>> *Contact emails* >>> johni...@chromium.org, csharri...@chromium.org >>> >>> *Explainer* >>> >>> https://github.com/WICG/conversion-measurement-api/blob/main/event_attribution_reporting_clicks.md >>> >>> *Design docs/spec* >>> https://wicg.github.io/conversion-measurement-api/ >>> >>> *Summary* >>> 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 discussion* >>> >>> https://groups.google.com/a/chromium.org/d/msg/blink-dev/7B0ldtZR_68/GjLBu0n4DgAJ >>> >>> *Link to “Intent to Experiment” blink-dev discussion* >>> >>> https://groups.google.com/a/chromium.org/d/msg/blink-dev/Ib9-tDFitns/Sm9RXTNaBwAJ >>> >>> First extension: >>> https://groups.google.com/a/chromium.org/g/blink-dev/c/C0P7ePjITJQ/m/ZYFmn30SDQAJ >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/C0P7ePjITJQ/m/ZYFmn30SDQAJ> >>> Second extension: >>> https://groups.google.com/a/chromium.org/g/blink-dev/c/xCWP1ltlAgw/m/acwN0GIRBQAJ >>> Third extension: >>> >>> https://groups.google.com/a/chromium.org/g/blink-dev/c/DmsUL3KHqMk/m/J2v3I_aEBAAJ >>> >>> *Goals for experimentation* >>> We hope to see that the data produced by the API is comparable to >>> existing cookie-based mechanisms. >>> >>> *Experimental timeline* >>> We'd like to extend the origin trial for 3 milestones, continuing >>> through Chrome 97 (95/96/97). The experiment has been running from Chrome >>> 86-94. >>> >>> *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. >>> >>> The Origin Trial tokens for Chrome 94 expired on October 12th. The API >>> has been effectively disabled since then, so there will be a gap in >>> availability. >>> >>> We have previously requested an exception to the .5% page load usage >>> limit for Origin Trials. Page load usage is currently around .48% in >>> October, and was at .5% on average in September. >>> https://chromestatus.com/metrics/feature/timeline/popularity/3365 >>> >>> *Reason this experiment is being extended* >>> We have two more non-google testers interested in experimenting with the >>> API who have not yet been able to start experiments. The proposed API is >>> fundamentally different in a number of ways from cookie-based mechanisms, >>> which can make setting up experiments time consuming. >>> >>> Given the wide range of environments where this API will be used, we >>> expect new testers to produce different learnings and feedback on the API, >>> even without changes to the API. >>> >>> *Ongoing technical constraints* >>> None. >>> >>> *Will this feature be supported on all five Blink platforms supported by >>> Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?* >>> Yes. >>> >>> *Link to entry on the feature dashboard* >>> *https://chromestatus.com/feature/6412002824028160 >>> <https://chromestatus.com/feature/6412002824028160>* >>> >>> -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/937eefcb-a3bc-4d95-8240-c1eeb4a927den%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/937eefcb-a3bc-4d95-8240-c1eeb4a927den%40chromium.org?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfXpzbEt2evF67qu6Qn_OQ%2BgvAbWd-UGQfYv%3DrL97j9TOQ%40mail.gmail.com.
