Skip to main content
Question

Impact of Changing groupId on Existing Segment Destinations (Mixpanel & Intercom)

  • November 22, 2024
  • 1 reply
  • 55 views
T
Forum|alt.badge.img

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:

  1. What impact will changing the groupId upstream have on these existing destinations?
  2. Will the data in Mixpanel or Intercom become fragmented (e.g., old data linked to customer_name and new data linked to customer_key)?
  3. 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 your advice! Thanks in advance. 😊

1 reply

Chris Carrel
Forum|alt.badge.img+4

It can be very problematic to change the value of an identifier especially if you are using Segment Unify because it doesn’t really allow you to change the value.  Have you considered using an Insert function https://segment.com/docs/connections/functions/insert-functions/ for just the new destination that would swap the groupID value only for your new destination? 

T
Terms & ConditionsAccessibility statement