Data Formatting and Validation

Whether interacting with Lexer’s APIs, or simply sending data via SFTP or CSV upload, ensuring your data is well-formatted and validated is a sure-fire way to optimize your CDXP experience.

Addresses

Address data can vary greatly depending on the regions your data represents. We have a very open definition of what valid address data looks like to ensure all valid addresses can be used.

However, good address data can have a significant impact on your team’s use of the CDXP, particularly if your use cases include location-based segmentation and insights. It’s recommended that you consider how easy to use your address data is. For example, are your states in a consistent format? I.e, VIC versus Victoria; NY versus New York.

Depending on the configuration of your CDXP unification policies, customers’ address data might be used to unify against 1st, 2nd, or 3rd-party data. In doing so, geocoding services may be used to prepare data for unification. You may want to consider validating your address data using one of the many geocoding services, such as OpenStreet Map, to minimize issues with your customer data.

Currency and financial data

Currency and financial data is accepted as decimals without symbol suffixes or prefixes, i.e. “12.99”, “-100.00”.

Where a currency can be provided, it should be in an ISO-4217 format, i.e. “AUD” or “USD”. The case of the code does not matter.

For information on our currency conversion capabilities for multi-currency data, please contact us.

Dates

All dates and timestamps are ISO-8601 date strings.

It’s recommended that you provide the timestamp portion of the string. If not provided, a UTC timezone will be presumed.

Email addresses and email hashing

Email addresses are commonly used for unification and activation throughout your CDXP and integrated platforms. While the Lexer CDXP has a loose definition of an email, we recommend checking your email addresses against this regex:

[.code](^[a-zA-Z0-9_.+-]+@[a-zA-Z0-9-]+\.[a-zA-Z0-9-.]+$)[.code]

To ensure the highest matching success, we lowercase all email data, and may reject malformed email addresses.

*Note that downstream platforms such as ESPs and Social Ad Networks can have strict policies on what is considered a valid email. This might cause profiles that don’t match their own policies to be rejected.

Hashing

We hash email data internally, as many activation platforms only accept hashed email data.

If you choose to provide hashed (SHA-256) email data, you should:

  • Remove leading/trailing whitespaces.
  • Convert the text to lowercase.

Genders

We accept any string value as a representation of genders. This format can allow you to use any genders, the key is to keep the format consistent. 

It’s worth considering that consistent gender data can have a significant impact on your team’s use of the CDXP. For example, you may want to clean your data to ensure genders are in a consistent format, i.e. “Female” versus “F”. 

Phone numbers

Phone numbers are commonly used for unification and activation throughout the CDXP and integrated platforms.

You should convert each phone number to E164 format. This format represents a phone number as a number up to fifteen digits, starting with a + sign (e.g. +12125650000, +442070313000).

*Note: Downstream platforms such as SMS platforms and Social Ad Networks can have strict policies on what is considered a valid number. If their required format is not used, they may reject profiles.

Multi-lingual text data

The Lexer platform supports multi-byte data in a UTF-8 format. You will not need to convert or translate data formatted as such, but note that the Lexer platform does not do any language conversion. Data will be presented in the language and format provided.

Updated:
September 19, 2022
Did this page help you?
Thank you! Your feedback has been received!
Oops! Something went wrong while submitting the form, for assistance please contact support@lexer.io
Welcome to Lexer!
Fundamentals
Getting started
Our glossary
Fundamentals
Getting started
Integrations
Fundamentals
Setup
My account
Fundamentals
Setup
Manage team
Fundamentals
Setup
Group permissions
Fundamentals
Setup
Classifications
Fundamentals
Setup
Out of the box segments
Fundamentals
Setup
Browser guide
Fundamentals
Security
Corporate networks
Fundamentals
Security
Emergency contact
Fundamentals
Security
Multi-factor authentication
Fundamentals
Security
Single sign-on
Fundamentals
Security
Trust and compliance
Fundamentals
Security
Lexer's Identity Resolution
Fundamentals
Identity Resolution
Troubleshooting tech issues
Fundamentals
Troubleshooting
Error code: 503 Service Unavailable
Fundamentals
Troubleshooting
Error code: 401 Unauthorized
Fundamentals
Troubleshooting
Error code: 403 Forbidden
Fundamentals
Troubleshooting
Troubleshooting Activate
Fundamentals
Troubleshooting
Troubleshooting Respond
Fundamentals
Troubleshooting
Help! My data is missing from the Hub
Fundamentals
Troubleshooting
Understanding APIs at Lexer
Data
Data Onboarding
Providing JSON data to Lexer
Data
Data Onboarding
Providing CSV data to Lexer
Data
Data Onboarding
Upload using SFTP
Data
Data Onboarding
Upload using S3
Data
Data Onboarding
Lexer data specification
Data
Lexer Data Specification
Customer data specification
Data
Lexer Data Specification
Commerce data specification
Data
Lexer Data Specification
Marketing data specification
Data
Lexer Data Specification
Compliance data specification
Data
Lexer Data Specification
Data Formatting and Validation
Data
Getting Started with APIs
Authentication and API token creation
Data
Getting Started with APIs
Rate Limits
Data
Getting Started with APIs
Response codes and common errors
Data
Getting Started with APIs
Product imagery
Data
Getting Started with APIs
Currency conversion
Data
Getting Started with APIs
Lexer’s APIs overview
Data
Lexer’s APIs
Dataset management in the Hub
Data
Dataset management
Chatbox user API
Data
Lexer’s APIs
Activity API
Data
Lexer’s APIs
Visualize API
Hidden from nav
Profile Read API
Data
Lexer’s APIs
Lexer Javascript Tag basics
Data
Lexer Javascript Tag
Lexer Javascript Tag technical guide
Data
Lexer Javascript Tag
Lexer Javascript Tag use cases
Data
Lexer Javascript Tag
dataLayer configuration: Shopify
Data
Lexer Javascript Tag
Customer segment CSV export
Data
Data off-boarding
Export to CSV
Data
Data off-boarding
Data in Lexer's CDXP
Understand
Customer Data
Lexer's attributes
Understand
Customer Data
Attribute value types
Understand
Customer Data
Data source - CRM
Understand
Customer Data
Data source - Transactions
Understand
Customer Data
Data source - Email
Understand
Customer Data
Partner data - Experian
Understand
Customer Data
Partner data - Mastercard
Understand
Customer Data
Partner data - Roy Morgan
Understand
Customer Data
GDPR and CCPA requests
Understand
Customer Data
Upload data files
Understand
Customer Data
File upload API
Understand
Customer Data
Data provision and schemas
Understand
Customer Data
Segment overview
Understand
Segment
Creating segments
Understand
Segment
Smart Search
Understand
Segment
Export attribute results
Understand
Segment
Contact a customer
Understand
Segment
Fixing a disabled segment
Understand
Segment
Profile tab
Understand
Segment
Compare segments
Understand
Compare
Compare attributes
Understand
Compare
Activate overview
Engage
Activate
Ongoing activations
Engage
Activate
Audience splits
Engage
Activate
A/B splits
Engage
Activate
Control group splits
Engage
Activate
Inbox filtering
Engage
Respond
Ignored Senders
Engage
Respond
Forms for service
Engage
Respond
Workflow states
Engage
Respond
Bulk changes
Engage
Respond
Scheduled replies
Engage
Respond
Message templates
Engage
Respond
Customer profiles
Engage
Respond
Grouped messages
Engage
Respond
Automation rules
Engage
Respond
Redact messages
Engage
Respond
Track overview
Measure
Track
Activity overview
Measure
Activity
Team report
Measure
Activity
Cases report
Measure
Activity
Listen overview
Measure
Listen
Searching in Listen
Measure
Listen
Tier filters
Measure
Listen
Boolean search
Measure
Listen
Saved dives
Measure
Listen
Email notifications
Measure
Listen
Twitter data
Measure
Listen
Facebook data
Measure
Listen
Instagram data
Measure
Listen
Visualize overview
Measure
Visualize
Curate feed
Measure
Visualize
Report overview
Measure
Report
// Rich text for code blocks and nested lists