Whether you’re on a standard e-commerce platform or you have built your own solution, Custora enables you to tailor your marketing based on customer-level insights.
Find great customers. Keep them coming back.
Insights: First, you learn
Custora provides e-commerce companies with a suite of customer analytics and insights – from simple reports on revenue to advanced reports that detect high-value customers right when they make their first purchase.
- Customer lifetime value analysis – Custora lets you know the long-term, lifetime value of each customer you acquire. Better yet, Custora predicts the lifetime value of even brand new customers. This enables you to quickly measure the long-term profitability of every new acquisition channel.
- Cohort analysis – Custora lets you slice and dice historical information in any way you can imagine to get a sense for the health of your business. Compare how users who joined at different points in time vary in ordering behavior. Get a sense of how much revenue is driven from newer and older customers.
- Persona analysis – Custora runs advanced models to identify “types” of shoppers based on the collection of items they purchase over their lifetime. Learn your personas, then drill down to see where you acquire them, and more.
- Churn detection – Custora detects when specific shoppers are fading off their unique buying patterns, so you can reach out exactly when it matters.
Actions: Then, you earn
- Lifecycle marketing – Custora makes it simple for MySQL shops to tailor marketing for customers across all the customer lifecycle stages. Learn the perfect way to convert members into buyers, to encourage buyers to become loyal customers, and to save customers when they start to fade away.
- Customer acquisition – start optimizing your ad spend based on customer lifetime value instead of simply looking at the cost of acquisition. Double down on channels that attract loyal shoppers, and peel back on channels that attract one-time buyers.
Configuring Custora to pull data from MySQL is a straight-forward process that takes just minutes to set up. During the signup process, a wizard will walk your tech team through the following steps for integration:
Step 1: Access to the server
The first thing Custora needs is access to your server machine where MySQL is hosted. You have four options for how you’d like Custora to access your database server.
- Custora can access your server via SSH authentication (recommended)
- You can grant access to Custora’s IP address
Step 2: Access to the database
Once Custora can access your machine, the next step is to access your MySQL database itself. For this step, you’ll need to provide Custora with the following information:
- Database Host
- Database Port
- Database User
- Database Password
Step 3: Configure database queries
The final step is to indicate the queries Custora should run to pull down the necessary sales and customer data. You can configure up to three queries:
- A users query: this query pulls down information on all your customers. It can include user_id, email, signup_date, and any number of segmentation columns such as region, acquisition source, and more.
- An orders query: this is the main query for sales information. It includes user_id, date of purchase, revenue, cost (if possible), and any number of custom segmentation fields. These segmentation fields often include things such as a coupon code used on the order, the device type used to make the order, and more.
- An order items query: this information pulls down product-level information associated with sales data. It includes user_id, date of purchase, order_id, product category, brand, department, and more.
Data Feeds: details and examples
A visual representation of each data feed, along sample files, is included below. Hover over each data feed to see details:
A customer data file should include customer id, email address, sign up date, and custom fields like gender and age.
Our customers have found the most value including custom fields they can directly act on – for example, ads can be targetted by region, gender, and age, so these are great things to include if you have them readily available.
An order file includes a record with basic details for each order you have received. They often include customer ID, date of purchase, revenue, and cost, as well as custom fields such as device used to place the order.
An order items file includes the details of the items in each order (customer id, date of purchase, revenue, cost, and custom fields such as brand and category of the item purchased).
Unsure about exactly which fields to include in your query? Our team is happy to provide best practices knowledge and to help you fine tune your queries.