Thanks to visit codestin.com
Credit goes to www.twilio.com

Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
Codestin Search App
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Unify Settings


Identity resolution

Codestin Search App

For information about Unify Identity Resolution Settings, see Identity Resolution Settings


Sources provide the data that Unify uses to perform Identity Resolution. You can add multiple sources to a single Unify space. Unify supports the following Source types:

TypeUnify Compatibility
WebSupported ✅
MobileSupported ✅
ServerSupported ✅
Object Cloud Unsupported ❌
Event CloudSupported ✅

Standardization settings for phone numbers

Codestin Search App

With standardization settings for phone numbers, you can ensure that all of your phone numbers are normalized into a consistent E.164 format.

(new)

Standardization settings are currently in public beta

Standardization settings are currently in public beta and is governed by Segment's First Access and Beta Preview TermsCodestin Search App. This feature is only available for identifiers in Unify spaces created after January 14, 2026.

Phone number normalization has the following benefits:

  • Improves data quality: When you standardize phone numbers to E.164 format, your foundational data is consistent and reliable.
  • Builds a single, accurate record for each customer: This reduces duplicate and fragmented profiles.
  • Boosts marketing effectiveness: More accurate profiles lead to better audience building and activation, improving campaign performance as a result.
  • Improves Profile API lookup accuracy: This eliminates the need to build custom standardization layers for querying.

Getting started

Codestin Search App

To enable standardization settings for phone numbers:

  1. Navigate to Unify > Unify settings and select Standardize identifiers.
  2. On the Standardization settings page, click Add standardization settings and click Phone number standardization.
  3. Select an identifier that you'd like to standardize, in this case, phone.
  4. Under Default country code, select the country code you'd like Segment to add to any incoming phone numbers that don't contain country codes.
  5. Enable the Enable standardization toggle and click Save.
  6. Click Save settings.

After enabling standardization settings, allow approximately five minutes for Segment to apply normalization to incoming data.

Disable standardization settings

Codestin Search App
(warning)

Segment cannot retroactively merge profiles with different phone number formats

If you disable standardization settings and have new identifiers come in with a different phone number format, Segment won't be able to merge those profiles together. When you request a Replay, Segment can merge profiles with different phone number formats as long as there are other matching identifiers.

  1. Navigate to Unify > Unify settings and select Standardize identifiers.
  2. On the Standardization settings page, from the list of normalized identifiers, select Phone and deselect the Enable standardization toggle.
  3. On the Disable standardization popup, click Confirm.
  4. Click Save settings.

Profile API lookups

Codestin Search App

Once you've enabled identifier normalization, when you make a GET call using the Profile API to retrieve a profile's traits, Segment normalizes phone identifiers upon lookup.

The normalization process

Codestin Search App

Segment designed the normalization process to handle different types of input variations, including incomplete or poorly formatted entries, and convert them to a single, standardized format: E.164Codestin Search App.

If your phone number is successfully normalized, Segment stores the phone number in the original format as a trait titled __original_phone. If Segment is unable to standardize your phone number, your phone number will be stored in its original format.


The API access tab is where you can find the space ID value of the Engage space and generate an access token to connect to the Profile API. Each Engage space created in your workspace will have its own unique space ID value.