Skip to main content

Hi Fellow Segmenters, 

 

We use segment to route the events from backend to all internal tools. I have a marketing data attribution issue with utm paramters values are not passed from root domain to a sub domain that loads after users signups up for a trial (with Google Account / OneTapgmail signin method). 

 

Examples:

Root domain: example.com

Subdomain after signing up: app.example.com

There is an option for users to use google sign or google on tap sign with gmail to signup for the account. Whenever the users chooses to use google account signin or google onetap sign-in, we are loosing the utm paramters and all the data is attributed as direct. 

The question: how can I pass utm paramters and their values from example.com?utm_source=google  to app.example.com?utm_source=google after the google account login method is used  via Segment?

 

Any help or solution on this is much appreciated. 

 

Best regards

Mahender

Hi @Mahender Chintalapally! We’d love to hear a bit more about your end goal in capturing utm parameters in the subdomain / why capturing utms at the root domain isn’t helpful for your use case.


@Mahender Chintalapally I don’t know if you are still looking for a solution for this, but if you have Segment Unify you may want to consider using a computed trait for first touch source based on the context→ campaign attributes in the page view event.  This is how we make sure that both first and last touch information is available in our customer records. 

If you don’t have unify, there is some creative coding that could fire an identify call when a page loads with UTM parameters that you would be able to send to down stream destinations.  This would require development work and be dependent on your web environment. 


Reply