Data provision and schemas

Enriching your customer profiles

To build unified and enriched customer profiles in the Lexer CDP, data types, formats, and schemas are required. In this article, we'll look at common subject matter, our different schemas, and provision methods.

Common subject matters

Lexer supports a wide range of subject matter and implementation styles. The below table outlines some common data areas and our supported connectors for these types of data.

Data area Connector Type Frequency
Customer Direct Integration or batch via API or SFTP. Historic and daily updates.
Ecommerce Transactions Direct Integration or batch via API or SFTP. Historic and daily updates.
Retail/POS Transactions Direct Integration or batch via API or SFTP. Historic and daily updates.
Returns Direct Integration or batch via API or SFTP. Historic and daily updates.
Email Engagement Direct Integration. Historic and daily updates.
Master Product fie Direct Integration or batch via API or SFTP. Historic and daily (including discontinued products).
Website Engagement Lexer Javascript Tag Integration. Real-time.
Other Subject to scoping. Subject to scoping.

Lexer Standard Retail Schema

Through our experience working with retail customers, we’ve developed a range of retail attributes to enable valuable customer insight and action.

These attributes are generally powered by supported integration data, but in some cases a solution might entail pushing data directly to Lexer (rather than via an integration).

Lexer generally supports these solutions provided this data is shared in the required format and structure.

Example Email Data Schema

Lexer offers in-platform integrations to easily connect with many popular Email Service Providers (ESPs). These integrations automatically gather data to drive related data points against your customer profiles.

In some cases (for example, with on-premise data) your solution might entail email service data directly to Lexer. In these instances Lexer will work with you to agree the requirements of an optimal data format.

The below table shows a rudimentary example structure for a "contacts" dataset, which would form one part of a broader ESP dataset.

Required Field Required Format Example
email Text string "sam@yahoo.com"
first_name Text string "Sam"
last_name Text string "Smith"
signup_date Date 2019-06-21
unsubscribe_date Date 2019-06-21
list_names Text string "Marketing", "VIPs"
email_optin_status Text string "subscribed" | "unsubscribed"
mobile_optin_status Text string "subscribed" | "unsubscribed"

Data Provision Methods

Lexer supports multiple data provision mechanisms. Below are the most common:

Customer profiles, enriched

That's how you can use our data provision and schemas to help unify and enrich you customer profiles in our CDP!

Updated:
September 23, 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