Skip to main content
Solved

Passing UTM parameters cross-domain

  • January 19, 2024
  • 1 reply
  • 813 views

We are trying to set up tracking between our standard marketing website and our product which lives in a web app. Because these live on two different domains we are trying to figure out how to pass back the UTM parameters from the landing page on our marketing site into the User data when they sign up on our web app.

We were thinking of passing back the device_id from the marketing site (example.com) to the web app (app.example.com). Is it possible to associate UTM parameters to that device_id so that when they fill out the form on the web app we can keep the parameters on the user’s data?

Best answer by rox.chang

Hi @Seth Anderson, passing the device_id from your marketing site to the web app would be the ideal approach. We recommend also capturing UTM parameters as user properties so that the UTM parameter values will persist on all events for the same device cross domain. Unlike event properties, user properties persist on all subsequent events until overwritten. If you are using our Browser SDK, the SDK will automatically capture UTM parameters (as well as referrer urls) as user properties on a set of first touch and a set of last touch user properties. See the Marketing Attribution section of our Browser SDK to see how the logic works on our own SDKs.

View original
Did this topic help you find an answer to your question?

1 reply

rox.chang
Team Member
Forum|alt.badge.img+1
  • Team Member
  • 5 replies
  • Answer
  • February 5, 2024

Hi @Seth Anderson, passing the device_id from your marketing site to the web app would be the ideal approach. We recommend also capturing UTM parameters as user properties so that the UTM parameter values will persist on all events for the same device cross domain. Unlike event properties, user properties persist on all subsequent events until overwritten. If you are using our Browser SDK, the SDK will automatically capture UTM parameters (as well as referrer urls) as user properties on a set of first touch and a set of last touch user properties. See the Marketing Attribution section of our Browser SDK to see how the logic works on our own SDKs.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings