Skip to main content

Feature Request: Source Tracking for Traffic Acquisition on Segment

We would like to request a feature to enable source tracking for traffic acquisition within Segment. This feature would allow us to easily pass source attribution data (such as UTM parameters, referrer information, and campaign details) to connected destinations. By capturing the source of traffic (e.g., organic search, paid campaigns, social media, email newsletters) and sending this information to our destinations, we can gain deeper insights into the effectiveness of different acquisition channels, optimize our marketing efforts, and better attribute conversions. This would streamline our reporting and analysis across various platforms, ensuring data consistency and improving overall campaign performance.

It sounds like there’s some overlap between what you’re describing and the ‘context.campaign’ object, which the analytics.js library automatically collects UTM parameters into. Could you expand on what the difference is between that and what you mean?

Agree with Gray, if you are using utms in the incoming source traffic, those pass to the context campaign data.

Or in our business case, we store some trait values via computed traits (last, first) or retl → segment profiles (attribution values per data science team), and use insert function with calls to profile api for some events to enrich the payload.

Also with the new Event Based Journeys, you can add profile props to the event data, super slick.

Reply


Terms & Conditions