Tracking User Sessions Across Domains

When a user lands on a page, such as a landing page, and is subsequently redirected to another page on a different domain, the marketing identifiers stored as cookies may differ. This discrepancy makes it challenging to track user sessions consistently across domains and hinders accurate conversion tracking. To address this issue, we can enhance user identification by sending key identifiers as query parameters during redirects between different domains.

For example, if the the user lands on this page from an ad:

https://mylandingpage.com/age-gate-21-br?utm_source=XYZ&utm_medium=ABC&utm_campaign=123&utm_term=LMN&utm_content=DEF&fbclid=GHI

and is redirected to

https://mybrand.com/product-blue-razz

we can append the identifiers in the query string like this:

https://mybrand.com/product-blue-razz?utm_source=XYZ&utm_medium=ABC&utm_campaign=123&utm_term=LMN&utm_content=DEF&fbclid=GHI&aid=JKL&&fbp=MNO&&fbc=PQR&&ga=STU&&gclid=VWX

The values (url encoded if needed) we would need to add (if available) are:

Key	Value
utm_source	utm_source from query if present.
utm_medium	utm_medium from query if present.
utm_campaign	utm_campaign from query if present.
utm_term	utm_term from query if present.
utm_content	utm_content from query if present.
fbclid	fbclid from query query if present. It may also be present in the cookie named aa_fbclid
fbp	The value from cookie named _fbp if present.
fbc	The value from cookie named _fbc if present.
ga	The value from cookie named _ga if present.
gclid	gclid from query query if present. It may also be present in the cookie named aa_gclid
aid	The value from cookie named _aid if present.

References