Find heavy buyers with declining purchase activity
There are many criteria by which you can create a variety of customer segmentations. The measures you choose will largely depend on the business goal you want to achieve. One of the possible goals may be to keep heavy buyers engaged. Heavy buyers are those customers who do an above-average amount of shopping. Heavy customers typically make up less than one-third of consumers of goods or services but account for more than two-thirds of sales revenue. That is why companies try to take special care of this group of customers.
This use case describes the process of identifying heavy buyers whose buying activity has declined in the current period and reactivating them with communications containing personalized offers that will prompt them to make a purchase.
Prerequisites
Implement transaction events.
Process
- Create a segmentation of heavy buyers
- Create a segmentation of heavy buyers whose buying behavior has changed over the past year
Create a segmentation of heavy buyers
In this part of the process, you will create a segmentation of heavy buyers based on the number of transactions generated by these customers in the previous period. Before you proceed to creating the segmentation, you will create an aggregate and metric which you will use in the conditions of the segmentation.
Create an aggregate
Create an aggregate that sums up the number of transactions in the previous period.
- Go to Analytics > Aggregates > Create aggregate.
- As the aggregate type, select Profile.
- Enter the name of the aggregate.
- Click Analyze profiles by and select Count (then the aggregate result shows the total number of transactions in the time range selected in the analysis).
- From the Choose event dropdown list, select the transaction.charge event.
- Change the date range, by clicking the calendar icon. Create the following custom date range
last 365 days before 365 days
. - Confirm the changes with the Apply button.
- Save the aggregate by clicking Save.
Create a metric
Create a metric that sets a cutoff value for the customer segment with the highest number of transactions.
-
Go to Analytics > Metrics > New metric.
-
Enter the name of the metric.
-
As a metric kind, select Simple metric.
-
As a metric type, select Profile.
-
As the aggregator, set Quantile.
Note: Quantile is used to divide a sample of data into equal-sized subgroups -
In the input field which appears next to the aggregator, type
0.7
(to create a cutoff that defines the highest number of values). -
Click Choose event.
-
From the dropdown list, select the aggregate you created before.
-
Define the same time range as in the aggregate you use in the metric.
-
Click Save.
Create a segmentation
In this part of the process, you will create a segmentation of customers with the highest scoring (30% of customers who made the highest number of transactions).
- Go to Analytics > Segmentation > New Segmentation.
- Enter the name of segmentation.
- On the canvas, click Add condition.
- From the dropdown list, select the aggregate you created before.
- From the Choose operator dropdown list, select More than.
- In the text field, enter the value returned from the metric you created in the previous step.
- Click Save.
Create a segmentation of heavy buyers whose buying behavior has changed over the past year
In this part of the process, you will create a segmentation that groups together all heavy buyers whose buying behavior has declined. Before you proceed to creating the segmentation, create an aggregate and metric which you will use in the segmentation.
Create an aggregate
Create an aggregate that sums up the number of transactions from the current period.
- Go to Analytics > Aggregates > New aggregate.
- Enter the name of the aggregate.
- By clicking the button, set Count as the type of the aggregate result (then the aggregate result shows the total number of transactions in the time range selected in the analysis).
- From the Choose event dropdown list, select the transaction.charge event.
- Change the date range, by clicking the calendar icon. Create the following custom date range
last 365 days before 0
. - Confirm the changes with the Apply button.
- Save the aggregate by clicking Save.
Create a metric
Create a metric that sets a cutoff value for the customer segment with the lowest number of transactions.
- Go to Analytics > Metrics > New metric.
- Enter the name of the metric.
- As a metric kind, select Simple metric.
- As a metric type, select Profile.
- As the aggregator, set Quantile.
- In the input field which appears next to the aggregator, type
0.3
(to create a cutoff that defines the lowest number of values). - Click Choose event.
- From the dropdown list, select the aggregate you created before.
- Define the same time range as in the aggregate you use in the metric.
- Click Save.
Create segmentation
Create a segmentation of customers who have the lowest number of transactions from the current period and also belong to the segmentation of heavy buyers.
- Go to Analytics > Segmentation > New Segmentation.
- Enter the name of segmentation.
- On the canvas, click Add condition.
- From the dropdown list, select the aggregate you created before.
- From the Choose operator dropdown list, select Less than.
- In the text field, enter the value returned from the metric that sets a cutoff value for the customer segmentation with the lowest number of transactions.
- From the Add condition dropdown list, select a segmentation of heavy buyers.
- From the Choose operator dropdown list, select Boolean Is true.
- Click Save.
What’s next
Send an email with personalized offers to the segmentation you have created with heavy buyers who should be reactivated.
Check the use case set up on the Synerise demo workspace
You can check the segmentation configuration directly in Synerise demo workspace:
- Segment of heavy buyers
- Segment of heavy buyers whose buying behavior has changed over the past year
If you don’t have access to the Synerise Demo workspace, please leave your contact details in this form, and our representative will contact you shortly.