Hi,
Asking this on behalf of a client:"I know Google recommends setting up a separate GA property for AMP which they note in a few places:https://developers.google.com/analytics/devguides/collection/amp-analytics/https://support.google.com/analytics/answer/6343176?hl=en
From what we can tell this is because the tracking for AMP will measure things differently than the current analytics.js library. I also think it's related to the GA cookie and how it's set differently for AMP pages.But won't this cause drop-off in user journey information? For example, if a user views an AMP blog article but then clicks to our site from a link within the article. I think we would then track this as two separate users and the pages/visit would be off. I found this article which explains a tech way to connect AMP to the same website GA property but it seems a little too much of a work-around:https://www.simoahava.com/analytics/google-analytics-client-id-amp-pages/
Do you think we should just do what Google recommends and set up AMP as a separate property in GA?"
--> Does anyone know if there could be any issues with this workaround?Thanks,