Profiles Frequently Asked Questions

Does your identity model support multiple external ID types?

Yes, Identity Graph supports multiple external IDs.

Identity Graph automatically collects a rich set of external IDs without any additional code:

1. Device level IDs (ex: anonymous_id, ios.idfa and android.id)
2. Device token IDs (ex: ios.push_token and android_push_token)
3. User level IDs (ex: user_id)
4. Common external IDs (email)
5. Cross domain analytics IDs (cross_domain_id)

If you want Identity Graph to operate on a different custom ID, you can pass it in using context.externalIds on an identify() or track(). If you’re interested in this feature, contact your CSM to discuss the best way to implement this feature.

Is all matching deterministic, or is there any support for probabilistic matching?

All Profile matching is deterministic and based on first-party data that you’ve collected.

Segment doesn’t support probabilistic matching. Most marketing automation use cases require 100% confidence that a user is who you think they are (sending an email, delivering a recommendation, and so on). The best way to support this is through a deterministic identity algorithm.

What happens to conflicting and non-conflicting profile attributes?

If two merged user profiles contain conflicting profile attributes, Segment selects the newest, or last updated, attributes when querying the profile.

What identifiers can the merged profile be queried/updated with?

Any of the external IDs can be used to query a profile. When a profile is requested, Segment traverses the merge graph and resolves all merged profiles. The result is a single profile, with the latest state of all traits, events, and identifiers.