You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We send contacts to HubSpot via the API, so they will always come up as original source = Offline. This means that all app signups don't have original source attribution in HubSpot, which affects tracking and ad performance for our paid ads.
Can we either:
Implement tracking in the app domain so that their source can send across (right now when users reach the app they become "invisible" to HubSpot) OR
Capture and send their GCLID and their UTM values to HubSpot
@annaredbond are you able to provide us with a way that we can test this out? i.e. some user journeys where we expect the UTM / GCLID parameters to be set?
The UTM/GLCID parameters should be set for things like ads, third-party published content, newsletters etc. e.g. Someone clicks on a paid ad, gets sent to the app signup and then signs up for a free account. Currently, tracking data is not being sent to HubSpot when users sign up so we can't track the effectiveness of our campaigns and efforts.
So, when someone creates an account, the contact in HubSpot needs to be created or updated.
We send contacts to HubSpot via the API, so they will always come up as original source = Offline. This means that all app signups don't have original source attribution in HubSpot, which affects tracking and ad performance for our paid ads.
Can we either:
More info and a Slack thread: https://flagsmith.slack.com/archives/C06D7F82WF7/p1714390077596589?thread_ts=1714058518.960549&cid=C06D7F82WF7
Another Slack thread for more info:
https://flagsmith.slack.com/archives/C06D7F82WF7/p1713357279287279
The text was updated successfully, but these errors were encountered: