Data provision & schemas

Data types, formats, and schemas required, to build unified and enriched customer profiles in the Lexer CDP. 

Types of Data

We require a variety of data types, from multiple sources, in both historic and ongoing formats:

Data

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

Types of Linkage

To construct a single customer view, we support a variety of linkage types, enabling us to match data across various sources. Each source needs to be connected via one of these identifiable methods:

Data

Linkage Type

Email Address

Primary

Hashed Email SHA256

Primary

Customer ID

Primary

Mobile or cell number

Primary

Street Address

Secondary

Product SKU or UPC

Secondary

Lexer Standard Retail Schema

Through our experience working with retail customers, we’ve developed a range of calculated attributes that allow you to quickly find valuable customer insight and action. The schemas below allow Lexer to turn your raw data into enriched retail attributes.

The latest standard retail schema can be downloaded here.

Required Field

Required Format

Example

customer_id

Text string

123454221

email_address

Text string

steve@gmail.com

mobile_number

Text string

949245555

first_name

Text string

Steve

last_name

Text string

Jones

gender

Text string

Male

year_of_birth

Integer

1984

address_1

Text string

227 George St

address_2

Text string

Apt 7

city

Text string

Los Angeles

state

Text string

California

zip_code

Text string

90210

country

Text string

USA

join_date

Date

06-21-2019

customer_type

Text string

Registered or Guest

customer_group

Text string

Direct or Wholesale or Business

loyalty_status

Text string

Gold or Silver

email_optin_status

Text string

Subscribed or Unsubscribed

mobile_optin_status

Text string

Subscribed or Unsubscribed

employee_flag

Text string

True or False

Order, Item, Return & Product Schema

Required Field

Required Format

Example

customer_id

Text string

123454221

email_address

Text string

steve@gmail.com

order_id

Text string

U12345

product_sku

Text string

KYT67532

channel

Text string

Ecommerce or Retail

store_name

Text string

Broadway

order_date_time

Date

06-21-2019

product_unit_price

Float

19.99

product_unit_discount

Float

2.00

product_quantity

Integer

1

total_item_price_before_discounts

Float

19.99

total_item_price_after_discounts

Float

17.99

promo_code

Text string

thankyou20

product_description_1

Text string

Large (size)

product_description_2

Text string

Blue (color)

product_description_3

Text string

Mens (department)

product_description_4

Text string

Jeans (category)

product_description_5

Text string

Summer19 (season)

product_description_6

Text string

Denim (material)

product_description_7

Text string

Levis (brand)

product_description_8

Text string

Slim (fit)

payment_type

Text string

AMEX or Afterpay

return_flag

Text string

True or False

return_date

Date

06-21-2019

Email schema (if not being provided by ESP integration) 

Required Field

Required Format

Example

email

Text string

sam@yahoo.com

first_name

Text string

Sam

last_name

Text string

Smith

signup_date

Date

06-21-2019

unsubscribe_date

Date

06-21-2019

list_names

Text string

Marketing or VIPs

email_optin_status

Text string

Subscribed or Unsubscribed

mobile_optin_status

Text string

Subscribed or Unsubscribed

Data Provision Methods

Lexer supports multiple data provision methods, from fully automated, to manual batch uploads. An integration or API is preferred, for a secure and automated solution - below are the most common methods:

Powered by HelpDocs (opens in a new tab)