SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Resolving "Identifier Standardization: Invalid Input" Errors in Identity Resolution

Issue

When using Segment Unify, users may encounter the error message "Identifier standardization: Invalid input." in the Profile Insights section. This occurs when incoming phone number do not match the set normalization conditions or cases where values do not contain numeric digits or are formatted as text, causing events to be dropped and not assigned to user profiles.

 

Product

Segment 

 

Environment

Segment Console

 

Cause

This error is triggered when the phone identifier in the incoming payload does not match the expected numeric format. Common causes include sending phone numbers as text or leaving the field undefined.

 

Resolution

  • Ensure all incoming phone number values contain numeric digits and follow a standard phone number format (such as E.164) as defined in the normalization settings.
  • If a phone number is not available or is incorrectly defined, remove the field from the payload before sending the event.
  • After correcting the data at the source, re-run any relevant data models or processes to ingest the corrected events.

 

Additional Information 

Consistent identifier formatting is required for successful profile resolution and event assignment in Segment Unify. Review your data sources and mappings to ensure compliance with identifier normalization requirements.

Have more questions? Submit a request
Powered by Zendesk