AMP Session Stitching - How to deal with Google's Client ID AMP Policy

[MargaritaS]

Hello,

I recently attended SMX East and the concept of 'session stitching' for AMP was brought up (https://www.stonetemple.com/amp-tech-guide/). I reached out to my development team and they told me they could do it, but that we would need to agree to the new TOS changes and making users aware of then... https://support.google.com/analytics/answer/7486055

Has anyone here done something like this? And if so how did you deal with the Google's Client ID AMP policy?

Thank you all!

-Margarita

[EricEnge]

I just found this by accident ... Looking at the policy, for purposes of the US, disclosing the use of the client ID to combine your sessions that start with AMP sessions in the Google cache with sessions that continue on your main site, requires only that you disclose that in your privacy policy.

The EU issue is the trickier one I think, and I'm no lawyer, and can't therefore give legal advice. What I've noticed though, is that lots of sites now put a message on the bottom of the browser window telling you something like "By using this site you are consenting to the use of cookies" or something along those lines. I wonder if they are doing that to meet the spirit of the EU regulations? I'd be interested to see if you learned anything since you posted the question above.