Celebrate Year 1 of Segment Community! Engage & Earn Merch this Month
Recently active
Feature Request: Source Tracking for Traffic Acquisition on SegmentWe 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.
Hello!Has anyone used Segment together with a PWA Source? My current set up has a React based website as Source and the Team is looking at offering an app-like experience in 2025. From what I understand, Page calls need some attention. And then there is offline activities that need looking into.Can events from both regular website and PWA flow to the same single Javascript Source? If I do that, how can I tell regular web usage apart from PWA?Another option would be to add a second Javascript Source. Prefer not to go down this path as I'll have to manage 2 copies of all the Destinations
Hello,I am currently tracking almost all the important events on our e-commerce website. Now, I want to use this data to send an abandoned cart email to the customer.How can I filter out the abandoned carts?I was thinking if the customer didn’t purchase anything in the next two hours then I can trigger it but if customer has removed an item from cart before that it can be empty.So what will be a good strategy?I am saving cart id but i am unable to compare last cart id of item added to cart and item purchased with each other.
Hi everyone,We're integrating a new destination into Segment that requires us to change the groupId in our Group API calls. Currently, the groupId is set to customer_name (e.g., "CUSTOMERNAME"), which is a recognized unique identifier in our business. However, the new destination requires the groupId to be customer_key, a different unique identifier that maps 1:1 with customer_name but is represented as a string like "c9r0239nfoe".The issue is that we also use Mixpanel and Intercom as destinations, both of which receive data from our existing Segment API calls. I’m trying to understand:What impact will changing the groupId upstream have on these existing destinations? Will the data in Mixpanel or Intercom become fragmented (e.g., old data linked to customer_name and new data linked to customer_key)? Are there best practices for managing such a transition to ensure data consistency across all destinations?If anyone has experience with this or similar scenarios, I’d greatly appreciate yo
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
