Commerce data specification
Commerce data is critical to providing actionable insights to your enriched customer profiles.
The Lexer Commerce Data specification provides a standard format for your product entities, transactions, and returns to enrich your customer profiles into the CDXP. When data is provided using this API, this data will enrich your customer’s 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.
Product entities
A sample of a product entity record:
Required fields
- [.code]product_id:[.code] A product object requires a [.code]product_id[.code]. This should be unique and used in purchase, and return events.
Purchase
A sample of a transaction record:
Required fields
- [.code]link[.code]: Where a customer record is defined by a single identifying link ([.code]email, email_sha256, email_md5, mobile, customer_id or external_id[.code]). To add more links for unification purposes, you will need to provide Unification data.
- [.code]action_at:[.code] The purchase date and time.
- [.code]purchase_id:[.code] A product object requires a [.code]purchase_id[.code]. This should be unique and used in purchase, and return events.
- [.code]type:[.code] The type of process the customer went through to make a purchase. This usually differentiates between ecommerce and in-store purchases.
Returns
A sample of a returns record:
Required fields
- [.code]link:[.code] Where a customer record is defined by a single identifying link ([.code]email, email_sha256, email_md5, mobile, customer_id or external_id[.code]). To add more links for unification purposes, you will need to provide Unification data
- [.code]action_at:[.code] The return date and time.
- [.code]return_id:[.code] A product object that is being returned requires a unique [.code]return_id[.code].
That’s a wrap on Commerce data specifications
This page has covered some samples of the commerce data schema itself, and the requirements of the schema. If you have any questions, please reach out to your Success Manager.
