-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attribution reporting api and email marketing #1142
Comments
See privacysandbox/privacy-sandbox-dev-support#184 which is a related issue. Right now there is no direct support for this use-case within ARA (if you don't control the email hosting site). Regarding the best practices around click IDs in links, this is probably not the right forum to ask since this repo is devoted to the Attribution Reporting API specification. cc @jolynyao |
We do not have control over the email hosting site, and the use case revolves around the ability to track post-click conversions when a person clicks on the advertising inside an email message. Currently, when someone clicks on the advertisement, a 3rd party cookie allows us to track the conversion. However, with the deprecation of cookies, this process no longer functions, making it impossible to track conversions. Our requirement is to maintain the tracking of post-click conversions from users who open an email message (via various platforms such as an app, webmail, or mail client). We are exploring ARA solutions to find a way to continue tracking conversions. After reviewing another issue you suggest (#184) and API documentation, it seems that achieving this may not be possible in the future. |
Hi @csharrison but the publisher can use the permission policy to manage who can use the API and then track the user. He can do the opt out of specific third party, all or none and the default is that all are allowed to use the API. So the publisher know that adv could track user and if it doesn't want he can use this to do the optout. Blocking the possibility to register to the API on redirect without starting with one with the attributionsrc parameter, other than prevent the registration to the API for link that are served by third party tool that doesn't support the parameter will also cut off from using this API for email marketing, as per @Refalb first concern, and in all the scenarios where the first click is not inside a chrome browser but the browser is opened in response to the click action on the link like on a mail client or application. Is there any other way to enable attrbution API on these scenario? |
Currently the permission policy is opt-out only, whereas We don't currently have plans to address this but we appreciate the feedback on use-cases, and we do use the feedback on github to inform our roadmap. |
Hi @csharrison , thanks for the clarification, but I have a doubt: with this alternative solutions, you exclude the possibility to track conversion from email marketing for example, where now with 3rd party cookie you can easily track conversion and compare this marketing channels with other strategy: not supporting this case you are excluding the possibility to easily track the results in some ecosystem creating a distorsion in comparing results from different channels |
Hi,
Is there any support in attribution reporting API for email marketing ? Since it's not possible to use JavaScript in email marketing, does Google offer a solution to support this business case and enable tracking conversions for clicks originating from email marketing campaigns? This is analogous to creating tracking with click URLs and image URLs from the campaign manager, as opposed to using a redirect tag.
We are aware that a solution for tracking post-click conversions from traffic originating in email marketing involves the use of first-party cookies, utilizing the Google Click ID. However, a challenge arises when partners use different ad servers and incorporate click ID parameters, as sometimes various redirects can disrupt the process of appending different click IDs to the URL.
Is there a best practice to ensure the consistent addition of these parameters to the click URL? For instance, allowing third-party ad servers to append their click ID to Google's link. To accurately track conversions, it is crucial that Google, during the redirect to the landing page, includes not only its click ID but also the click ID from other ad servers.
Do you have some suggestion?
The text was updated successfully, but these errors were encountered: