Questions on Attribution Reporting API Origin Trial

[lbdvt]

Hi,

Could you please confirm that the components of the Attribution Reporting API that are available as of today for Origin Trial are those listed here:
https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting-introduction/#status ?

In that table, "Attribution model: priority-based Explainer" links to Attribution Reporting for View-Through Measurement.
Could you please confirm that it should actually link to: Multiple sources for the same trigger (Multi-touch) ?

The corresponding OT is https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721 ?

And lastly, is there any restriction on the OT (e.g. geo, like there was for FLoC OT) ?

Thanks!

[lbdvt]

@maudnals maybe?

Thanks

[maudnals]

Hi @lbdvt,
Thanks for your questions and the ping!
I've replied below.

[maudnals]

Hi @lbdvt,

Thanks for your questions!

Could you please confirm that the components of the Attribution Reporting API that are available as of today for Origin Trial are those listed here:
https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting-introduction/#status ?

The components of the Attribution Reporting API that are available as of today for Origin Trial are those listed in that Status list and that have a status of 🧪 Experiment.

In that table, "Attribution model: priority-based Explainer" links to Attribution Reporting for View-Through Measurement.
Could you please confirm that it should actually link to: Multiple sources for the same trigger (Multi-touch) ?

Indeed, "Attribution model: priority-based Explainer" could now link to Multiple sources for the same trigger. We'll fix this, thanks for flagging!

The corresponding OT is https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721 ?

Yes, you can use source-side priorities to define custom attribution rules in the currently running OT.

And lastly, is there any restriction on the OT (e.g. geo, like there was for FLoC OT) ?

There is no geo restriction for this OT, and no additional restriction.

💡 Noteworthy:

• If you're looking for a quick way to see how the priority feature behaves, head over to the deployed demo and corresponding code that's linked from the demo page. The demo uses priorities in a basic way, to define a first-click attribution model.
• Check out the newly published API guide for an explanation of how to use the priority feature (and all API features).
• You can use priorities by leveraging the currently running OT, but you can also see it in action by just turning on flags in your browser to activate the API locally; this is handy for local experimentation. See how. (This is also how the demo linked above works)
• Just in case you're not already in there, feel free to join the mailing list for devs. [EDIT: The reason I'm suggesting this is that we use that list as one of the first places to post developers updates, including new API guides like the one I've linked above; so in case that API guide is interesting to you, join the mailing list if you wish to be notified as soon as we publish such guides.]

Let me know if you have any follow-up questions!

[lbdvt]

Very clear, thanks!