Purchase Frequency criterion

This article will show you how to use this Segment criterion.

The Purchase Frequency criterion is a segmentation criterion that enables defining a segment.

To learn how to create a segment, please refer to this article.

📖 Definition

The Purchase frequency targeting criterion enables you to create a segment of visitors based on the frequency of the purchases they made within a defined period of time. The Purchase frequency criterion is based on the transaction tag, which enables you to collect specific information on the buying patterns of users.

⚙️ Configuration

To configure the Purchase frequency criterion, apply the following steps:

1. Select the type of interval from the first drop-down list: more than (strictly higher) or less than (strictly lower).

2. In the Time(s) field, manually enter the number of desired purchases.

3. Select the type of interval from the first drop-down list: within, beyond or between.

4. In the Day(s) field, manually enter the value(s) depending on the chosen interval.

For data confidentiality reasons, you cannot target visitors who made their last purchase over a year (365 days) ago. Keep in mind that this duration is depending on your browser settings and policy.

You can also refine targeting by adding advanced conditions, thus defining the last purchase based on:

• payment method;

• delivery method;

• SKU code of the product;

• product category;

• transaction amount;

• coupon used.

💡 Use case

Example: a segment with people that have made more than 5 purchases within the last 30 days using an American Express card. All the values that need to be filled in are your websites’ variables. You have to enter the exact string: “Paypal”, “clickandcollect” etc. and match the spaces and special characters. However, you don’t need to match lowercase and uppercase letters. For example, “Paypal” and “paypal” will both work. You don’t need to specify the currency, just enter the amount in your website’s currency.

🔎 How Does It Work?

Within the tag, we created an object called ABTastyData that contains information about your visitors’ journey. Inside this object, we store transactional data in locations called transaction and items.

This is performed when you integrate the transaction tag on your website. With that integration, the generic tag receives hits from the transactional tag when your visitor validates a transaction.

Need additional information?

Submit your request at [email protected]

Always happy to help!

ALY-PROF.png