|
|
|
|
|
by jchw
2555 days ago
|
|
Email tracking in AMP is, as far as I know, roughly identical to without AMP. To quote the official AMP documentation: https://amp.dev/documentation/guides-and-tutorials/learn/ema... >AMPHTML allows tracking email opens with pixel tracking techniques, same as regular HTML emails. Any user-initiated requests for data from external services will also indicate the user is interacting with the message. Email clients may offer their users the ability to disable loading remote images, and other external requests. While I can understand some concern regarding allowing email to do more, I don’t understand the adtech bits. If you could explain that in more concrete detail, I’d be appreciative. To be particular: what AMP elements or functionality would compromise user’s privacy? |
|
> The request is always made from the client, even if the document was served from the AMP Cache.
My naive reading of `amp-list` is that it's a tracking pixel that basically can't be blocked if you have AMP enabled and expect your emails to render reliably.
I suppose you could disable `amp-list`, the same way you could disable AMP in general. But it's trivial for me to make an email that won't render if the request fails. So you'll either accept my "tracking pixel" or you'll be okay with (effectively) not using AMP.
Am I'm missing something? I didn't see anything to this effect, but I guess Google could require fallback data to be coded into the email if the request fails?
[0]: https://amp.dev/documentation/components/amp-list?format=ema...