Data source - Transactions
Learn how we process your transaction data
Lexer’s Customer Data Platform ingests data from a variety of sources, and one of the most common is transaction data, from both ecommerce and in-store. Sending Lexer this data allows you to understand your customers’ behavior towards your brand in terms of spend and frequency, to better market to the right crowd, at the right time. In this article, we'll walk you through how to integrate your account and which transaction attributes are available.
Integrate your account
First we need to connect your account, which will give us permission to retrieve transactions and customer profiles from your ecommerce platform.
- Connect your BigCommerce account
- Connect your Commercetools account
- Connect your Magento account
- Connect your Shopify account
What we do with the data
Once you’ve connected your account, Lexer is then able to retrieve your customer and product information to create a set of attributes, that you can later query and compare in Lexer.
This is what we do with your data to achieve this:
- Auto-validation: We check the format of the file, and the records in the file, to make sure they can be imported.
- Validation: We look at the data to make sure it’s what we expect it to be.
- Enrichment: We transform the data to turn it from what it is into a set of value-add attributes.
- Unification: We unify your transaction data to other data you have provided, as well as third-party data sets.
- Import: We take the validated, enriched, and unified data and import it into the Lexer product.
What we build
Once we’ve retrieved your data, we will build a set of attributes you can query in Lexer. We either import it without transformation, or we change it so you can get more value from it. Here is a list of the attributes we can build with this data.
Lexer cleans and transforms your data into straightforward representations of the raw data, making it easy for your team to search, analyze, and activate.
Lexer takes all the data you have provided and enriches it, often combining multiple data points to make them more useful than they are on their own.
How we unify
The data we receive can be matched to first, second, and third party sources. This could be your own data, partner data, or public data sources. To match the data, we need certain fields to do certain jobs.
This field is typically used to match to your other data sources, such as CRM and Email Engagement platforms. If this ID is used across your business, it will be the field that links across all systems.
This field is used to unify your data to Twitter, enable activation on various sales channels, and can be used to unify your data to certain second and third party sources. If this field is only available in your CRM system, then the Customer ID in your Transaction file should match the IDs in the CRM file.
This field is used to unify on other data sets, such as Experian. Lexer transforms your mobile numbers to make sure they’re in a consistent format, ensuring the highest possible unification rates.
This field is matched to product files, capturing richer descriptions of categories and products your customers purchase.
This field is used ot capture information about an order from a variety of sources. Order IDs are a great way to match all data about a purchase a customer has made.
This field is typically attached to a specific sales channel. Orders with store information can be unified to data about stores to understand channel behaviors.
The volume of data being sent from each platform’s respective API will affect the time it takes to extract it. If we're trying to extract a large amount of data, it’s worth noting this could take a while, and has the potential to fail. This is based on each platform’s ability to send across the data Lexer is asking for, within a reasonable time, and without becoming overwhelmed.
And that's it! Now that you know how we process your transaction data and which attributes we can build with it.