Fundamentals
Getting started
Setup
Integrations
Strategies
Lexi
Security
Identity resolution
Troubleshooting
Data
Onboarding
Data specification
Formatting
APIs
Datasets
Logs
Forms
Javascript Tag
Customer data
Partner data
Compliance
Offboarding
Understand
Segment
Attributes
Compare
Engage
Activate
Respond
Contact
Schedule
Serve
Measure
Track
Activity
Listen
Visualize
Report
Customer data specification
The heart of any CDXP is customer data… it’s two of the four letters in the acronym after all!
The Lexer Customer Data specification provides a standard format for your customer records to be onboarded with ease into the CDXP. The process captures common CRM style fields, as well as customer identifiers, for unification and activation. When data is provided using this API, this data will enrich your customers’ profiles with additional attributes.
More detail about the attributes that can be created from this API are in the links below:
For more information about these attributes you can find our full attribute list here.
Customer records
Here is a sample of a customer record:
| // Profile API: Customer Write | |
| { | |
| "records": [ | |
| { | |
| "link": { | |
| "email": "jane@fake.com" | |
| }, | |
| "email": "jane@fake.com", | |
| "email_sha256": "8b1885...", | |
| "mobile": "61400000000", | |
| "first_name": "Jane", | |
| "last_name": "Doe", | |
| "gender": "Female", | |
| "customer_id": "b6ef3b...", | |
| "date_of_birth": "2023-09-20", | |
| "country": "Australia", | |
| "state": "Victoria", | |
| "city": "St Kilda", | |
| "postcode": "3182", | |
| "zip": "90291", | |
| "employee_flag": false, | |
| "customer_type": "VIP", | |
| "address_1": "Inkerman St", | |
| "address_2": "string", | |
| "custom_fields": { | |
| "churn_risk": 0.291, | |
| "loyalty_status": "platinum" | |
| } | |
| } | |
| ] | |
| } |
Required Fields
- link: Where a customer record is defined by a single identifying link (email, email_sha256, email_md5, mobile, customer_id or external_id). To add more links for unification purposes, you will need to provide Unification data.
That’s a wrap on Customer data specifications
This page covered some samples of the customer data schema itself, and the requirements of the schema. If you have any questions, please reach out to your Success Manager.
