Lexer data specification
Lexer has designed a data structure to automatically enrich your customer and transaction data into highly valuable attributes and segments to help you drive immediate impact. A reflection of our data structure can be found in the following schemas, each with a specific focus and their own set of APIs:
Together, these create a highly structured representation of your customers, their transactions, and marketing history.
Custom data
Your Lexer CDXP is capable of supporting data that doesn’t naturally fit within these predefined specifications.
The most common path for custom data sources is usually directed towards:
- Custom data on customer records - such as loyalty information, outputs from data modeling, or other data that relates back to customer identifiers, for example, an email, customer id, or phone number. This is supported through the Customer Data Specification via APIs, JSON, and CSV imports.
- Custom data on product records - such as hierarchical product categories, bundling, sizing, and so on. This is supported through the Commerce Data Specification via APIs, JSON, and CSV imports.
- Custom event data - such as store visits, app usage, and so on.
Please speak with your Solution Architect to design an implementation specific to your use cases.
What’s next? Let’s take a look as some schemas
This page has outlined what data specifications we have available for your use and what to do if you need to support some custom data that doesn’t quite fit. The following pages will look at the currently available schemas and requirements for customer, commerce, marketing and compliance data.
