Open mpisula opened 8 months ago
Hi @mpisula, we currently support attribution reporting in Chrome as well as WebView and Android. We're certainly interested in other environments and would be interested to understand how impactful each is to your business. For example for email - I imagine you mean supporting attribution for email-based marketing efforts (e.g. register a source for users that saw some email)?
Hi @jolynyao, sort of. Specifically, we deliver ads within publisher emails. That ad is dynamically delivered, based on the content of the email and the user reading the email. Today, we do a server-side passback to partners (including Google) to let them know that their ad was served. The email environment does not support any type of JS or other programming language -- it's all images & text. So we wouldn't have the ability to register a source.
Hi, just wanted to see if I could get some feedback on this. Thanks.
Hi, sorry for the delay. Thanks for the add'l detail on the email use-case. One question on that - you mention a server-side passback to partners, I assume so that they can attribute conversion events later. What is that passback / attribution based on (e.g. an identifier like device ID, the email, a click id, etc)?
We don't have any concrete plans to support additional environments, but would love to hear feedback on which ones are most impactful to you. For example, you mentioned email, CTV, and DOOH but could you help me understand relative priority to your business?
It's possible to register for attribution during a redirect if the first link doesn't have the attributionsrc?
For example the creativity is delivered via an adserver that doesn't support attribution api and generate a "classic" banner, the url in the href is of the third party adserver that do a redirect to an adserver that support these api and want to register it as an attribution sources. Is the second adserve able to register to the API or not because the first link doesn't have the attributionsrc? Is there any way to manage this scenario that is not so uncommon?
In reading the specification at https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#registering-attribution-sources, we have a question about if non-JS environments (such as email, CTV, DOOH, etc) have been considered? Or is this just an edge case that will be considered "later".
Thanks very much.