Validation Rules and Campaign Limits

This article covers all rules and limits that you can use in the validation rule builder in your promo campaigns. You will learn how to secure your campaigns from fraud, create specific buying circumstances that limit code usage, and define criteria for earning loyalty points.

  1. Glossary
  2. Rules and limits reference
  3. Context

This article is divided into three parts:

  1. The glossary explains Voucherify’s terminology and key definitions you need to know to create campaign validation rules easily. 
  2. Description of the rules and limits that you can add to various campaign types.
  3. Contexts for the validation rule builder.

This article serves as a reference for the Validation Rule Builder manual.

Glossary

This glossary explains Voucherify’s terminology and key definitions you need to know to create campaign validation rules easily.

Customer segment

Segments group customers based on standard attributes (email, postal code, and many more) and custom attributes added as metadata. You can also use custom events and system attributes to create segment criteria. Segments are used in validation rules and distributions to define the campaign/distribution audience. 

Custom event

Custom events are actions taken by the customers you track in your application or website and pass to Voucherify using the API.

Earning rules

An earning rule defines an action(s) that assigns a particular number of loyalty points to a customer's loyalty card. There is no limit on the number of earning rules in a single loyalty campaign.

Holder of the code

The customer is the holder of a unique code (e.g. (coupon, gift card, referral code, loyalty card)) once it was assigned to them. You can see all assigned codes in the customer profile in the Wallet tab.

Metadata

Also “Custom attributes”. Metadata allows you to add custom data in Voucherify. You can use metadata for building validation rules and reporting/tracking. Each metadata attribute is a key-value pair that carries custom information about Voucherify objects, such as redemption, customer, product, and many more.

Redeeming user

The user in validation rules and our pricing refers to your team members. Setting up the Redeeming user in validation rules enables you to limit the rights of your project members to invoke successful redemptions.

Redemption

A redemption is a single use of a promo code or an in-cart discount. In loyalty programs, a redemption is equal to exchanging loyalty points for a reward.

Rules Builder

The Rules Builder creates validation rules. The Rules Builder is built into the Campaign Manager, so you can create validation rules when creating a new campaign. You can also open the Builder in the Validation Rules section in the Voucherify dashboard. 

Validation rules

Validation rules are rules and limits created in the Rules Builder. They are applied to codes or loyalty earning rules in your campaigns. The validation rules applicable to codes and promotions are checked during the redemption.

Rules and limits reference

This section describes the rules and limits that can be found in the campaign manager and the validation rule builder.

Note that rules and limits depend on the context of the campaign that you create. Some of the rules and limits are not available in the specific configuration of a campaign.

Audience

These rules define the conditions customers must meet to receive an incentive.


Customer segment It defines targeting and/or excluding specific customer segments. You can limit redemptions to specific customer segments and/or exclude particular segments from the campaign.
Customer loyalty tier It defines targeting and/or excluding specific loyalty tiers. You can limit redemptions to specific loyalty tiers and/or exclude particular loyalty tiers from the campaign.
Customer metadata satisfy It creates a redemption limit based on Custom attributes (metadata) added previously to the Customers schema. The metadata enables you to extend customers' characteristics with new attributes and use them to build campaign limits.
Only for customers who are holders of the code It defines that a code can be redeemed only by the person it has been published to. 

Products

These rules define the validation that is dependent on the structure of the order placed by a customer.
Any order item It contains a filters editor (Find and apply filters) that defines the criteria that ANY item in the customer's cart needs to match (based on metadata and standard product attributes). In addition to the default filters, you can also define filters based on Product attributes or Custom attributes (metadata).
There are two conditions for the any order item rule:
  • is – the provided items or collections must be in the cart,
  • from – the items or collections provided in the "is" field must also meet the "from" condition.
For example, "is" a t-shirt collection, "from" a summer clothing collection.

    You can further define this rule with the Add subrule option for Order Structure or Order Volume:
  • Metadata of matched items – it defines limits using order items metadata that need to be met by at least one order line item.
  • Subtotal of matched items – it defines the total amount of all items that meet criteria set with product filters.
  • Quantity of matched items – it defines the total number of all items that meet criteria set with product filters across all order lines.
  • Unit price of the matching order line – it defines the price of at least one matching order line.
  • Item quantity in the matching order line – it defines the required quantity for at least one matching order line.
Every order item It contains a filters editor (Find and apply filters) that defines criteria that EVERY item in the customer's cart needs to match (based on metadata and standard product attributes). In addition to the default filters, you can also define filters based on Product attributes or Custom attributes (metadata).
There are two conditions for the any order item rule:
  • is – the provided items or collections must be in the cart,
  • from – the items or collections provided in the "is" field must also meet the "from" condition.
For example, "is" a t-shirt collection, "from" a summer clothing collection.

You can further define this rule with the Add subrule option for Order Structure or Order Volume:
  • Metadata of matched items – it defines limits using order items metadata that need to be met by every order line item.
  • Subtotal of matched items – it defines the total amount of all items that meet criteria set with product filters.
  • Quantity of matched items – it defines the total number of all items that meet criteria set with product filters across all order lines.
  • Unit price of the matching order line – it defines the required price of every order line.
  • Item quantity in the matching order line – it defines the required quantity in every order line.
None of the order items It defines criteria for the products that exclude the cart from successful validation. In addition to the default filters, you can also define filters based on Product attributes or Custom attributes (metadata).
Most expensive of the order items It defines the rules for the most expensive item in the cart or for the most expensive item in the cart that belongs to a specific product collection. The built-in collection All Products defines the limits for the most expensive item in the cart. There are two conditions for the most expensive items:
  • is – the provided items or collections must be the most expensive in the order
  • from – the items or collections provided in the "is" field must be the most expensive from the collection defined in the "from" field.

You can further define this rule with the Add subrule option for Order Structure or Order Volume:
  • Metadata of matched items – it defines limits using order items metadata that need to be met by each qualified most expensive item.
  • Subtotal of matched items – it defines the total amount of all the qualified most expensive items.
  • Quantity of matched items – it defines the total count of all the qualified most expensive items.
  • Items quantity in any matching order line – it defines the required quantity of each qualified most expensive item.
  • Unit price of any matching order line – it defines the required price of each qualified most expensive item.
Cheapest of the order items It defines the rules for the cheapest item in the cart or for the cheapest item in the cart that belongs to a specific product collection. The built-in collection All Products defines the limits for the cheapest item in the cart.There are two conditions for the cheapest items:
  • is – the provided items or collections must be the cheapest in the order
  • from – the items or collections provided in the "is" field must be the cheapest from the collection defined in the "from" field

You can further define this rule with the Add subrule option for Order Structure or Order Volume:
  • Metadata of matched items – it defines limits using order items metadata that need to be met by each qualified most expensive item.
  • Subtotal of matched items – it defines the total amount of all qualified cheapest items.
  • Quantity of matched items – it defines the total count of all qualified cheapest items.
  • Unit price of any matching order line – it defines the required price of each qualified cheapest item.
  • Items quantity in any matching order line – it defines the required quantity of each qualified cheapest item.

Prices & Quantities

These rules define the validation that is dependent on the volume of the order placed by a customer.
Total amount It defines a value of the cart that enables the customer to use the code.
Initial amount It defines an initial value of the cart that enables the customer to use the code.
Items quantity It defines the required quantity of the products that need to be in the cart.
Price of each item It defines a price for each product in the customer’s cart.
Price of any item It defines a price required for at least one product in the customer’s cart.

Metadata

These rules define the validation that is dependent on the metadata.
Customer metadata satisfy It creates a redemption limit based on Custom attributes (metadata) added previously to the Customers schema. The metadata enables you to extend customers' characteristics with new attributes and use them to build campaign limits.
Order metadata satisfy It defines what custom attributes (metadata) need to be assigned to the customer's order.
Custom event metadata satisfy It defines what custom attributes (metadata) need to be assigned to the custom event.
Redemption metadata satisfy It defines what custom attributes (metadata) need to be assigned to the redemption request.

Budget constraints

These rules define the validation that is dependent on your budget. They can also affect the number of redemptions done by customers.
Total orders value It defines the value of all orders made within the campaign. Once the limit is reached, customers cannot redeem more codes.
Total discounted amount It defines the overall value of the discount that the customers can get by redeeming codes from a particular campaign.
Total number of redemptions It defines the total number of redemptions allowed per entire campaign (the sum of all redemptions made with unique codes from the campaign). 
Total number of redemptions per day It defines the daily limit of redemptions allowed in the entire campaign for all customers (the sum of all redemptions made with unique codes from the campaign). 
Total number of redemptions per month It defines the monthly limit of redemptions allowed in the entire campaign for all customers (the sum of all redemptions made with unique codes from the campaign). 
Redemptions per incentive per day It defines the daily limit of redemptions for a given code.
Redemptions per incentive per month It defines the monthly limit of redemptions for a given code.
Redemptions per customer per incentive It defines the total number of redemptions that a particular customer can make using a given code.
Redemptions per customer per incentive per day It defines the daily limit of redemptions that a particular customer can make using a given code.
Redemptions per customer per incentive per month It defines the monthly (calendar month) limit of redemptions that a particular customer can make using a given code.
Redemptions per customer in a campaign It defines the total number of redemptions counted per customer per campaign.
Redemptions per customer in a campaign per day It defines the daily limit of redemptions that a particular customer can make using codes from a particular campaign.
Redemptions per customer in a campaign per month It defines the monthly (calendar month) limit of redemptions that a particular customer can make using codes from a particular campaign.
Total redeemed gift amount  It defines the total value of the redeemed balance in the whole  campaign.
Pay with points (points used) It defines the number of loyalty points to be used to pay for an order.

Redemptions

These rules define the redemption validation options.
Redemption metadata satisfy It defines what custom attributes (metadata) need to be assigned to the redemption request.
Redeeming user It defines which team members or affiliates can/cannot invoke a coupon redemption.
Redeeming API key It defines the access to invoking successful redemptions to particular API keys. 
Only for customers who are holders of the code It defines that a code can be redeemed only by the person it has been published to. 

Context

Context for validation rules is used in the Validation Rules section of the Voucherify dashboard. Context defines the purpose and usage of validation rules and their future application.

The General Usage context can be used for situations where you want to use the rules in more than one context or campaign type. Other contexts define a proper list of conditions that can be used to validate a specific resource. As a result, certain rules are not available in some contexts. For example, there are different limits for earning loyalty points and another set for code redemptions.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us

Related Articles