The JS tracker attaches the domain_userid to the querystring when navigating to an AMP page, but if that page is hosted on the AMP CDN, it isn't successfully captured.
I believe this to be down to cookies - currently we first set a cookie, then grab that value to send.
This has two problems: 1. on the AMP domain, we can't always set the cookie, and 2. the order of operations isn't deterministic, so a changing value isn't guaranteed to change in time.
Can easily be resolved by reordering priority of the value to take from querystring before grabbing from cookie.
colmsnowplow
commented
3 years ago
The JS tracker attaches the domain_userid to the querystring when navigating to an AMP page, but if that page is hosted on the AMP CDN, it isn't successfully captured.
I believe this to be down to cookies - currently we first set a cookie, then grab that value to send.
This has two problems: 1. on the AMP domain, we can't always set the cookie, and 2. the order of operations isn't deterministic, so a changing value isn't guaranteed to change in time.
Can easily be resolved by reordering priority of the value to take from querystring before grabbing from cookie.