A rule identifies Loyalty members based on criteria you specify. Use rules to create groups that you can use for targeted recognitions or communications.
To build a rule:
- In Loyalty Admin, go to Campaigns > Rules.
- Click Add New Standard Rule or Add New At Purchase Rule.
Note: The system evaluates Standard rules either throughout the day or overnight. Contact your Vista representative if you’re not sure when this scheduled task occurs. The system evaluates At Purchase rules whenever it processes a transaction.
- In the Name field, enter a name for your rule.
- Define the criteria of the rule by completing the fields in any of the available sections.
Important: A member must meet all of the criteria you specify to satisfy the rule. If a member doesn’t meet one or more criterion, the rule won’t add that member to a group.
Note: Keep your rules simple to make them easy to use and maintain. To analyse multiple criteria while keeping your rule build simple, consider using multiple rules together in a model.
Some of the campaign rule criteria are:
Criterion | Description |
Points Balance |
More than a certain quantity of a specified balance type. This can be used to identify customers with more than a particular points balance, more than a specified number of total visits or visits this year, or total value spent at the cinema. Example: Has more than 10 points of balance type Visits. This means that once the member has accumulated 10 visits then this rule will be triggered. |
Quantity Sold |
Members that have purchased a particular quantity (or more) of tickets or items. This can be narrowed further to particular films. This can also be further refined to only search on recent sales, in the preceding number of days as specified by the user. Example: Purchased more than 4 standard tickets to King Kong in the last 30 days. |
Total Spend |
Members that have spent a particular value (or more) at the cinema. This can be narrowed further to particular films. This can also be further refined to only search on recent sales, in the preceding number of days as specified by the user. Example: Has spent more than $30 on popcorn in the last 60 days. This means that once the member spends more that $30 total on popcorn in the last 60 days, then this rule will be triggered. |
Session Attended |
Members that have attended a session that fits the selected session range, type and location. Session time range, month range, last x days, genre of movie and transaction cinema location can be selected to create a statement that can be used individually or in conjunction with other statements. Example: The session range is in the Weekdays time range and the member has attended a session between January and February and in the last 20 days, the genre of the movie is Action and the transaction occurred at the Queen Street Cinema. This means that if the member had attended a session for an action movie at Queen Street in the last 20 days between January and February, then this rule will be triggered. |
Recognition |
Members that have had some change in status with respect to a recognition. Recognitions can include messages, requests, special offers, “one-off” free or discounted products awarded to a member when they previously met particular criteria. This field allows you to identify members who have:
It is also possible to specify a particular recognition that this event has occurred for (or generic, to capture all recognitions). Example: Free Preview Invite has changed status to Redeemed in the last 60 days. This means that if the Free Preview Invite recognition for a member has changed status to Redeemed in the last 60 days, then this rule will be triggered. |
Transaction Value | Members who have completed transactions above a certain value, visited a certain Cinema/Cinema Type, or attended a session between a date range. |
Initial Transaction | Member's first transaction is between a specific date range. |
Member's Birthday |
Member’s whose birthday falls on a particular day. Options are:
Example: Members birthday is in Date Range between 01 January and 15 February. This means that if a members birthday occurs between 1st January and 15th February, then this rule will be triggered. |
Member Sign up | Members who signed up at a certain location, during a certain date range, and/or expire within a specific date range. |
Demographic Matches |
A number of demographics are available:
Example: The following demographics apply: Lowest Age 16, Highest Age 30, Gender Male, Preferred Genre Action. This means that when the member demographics match all those listed, then the rule is invoked. |
Communication |
Members who have a particular setup for their communications. Example: Members who have an incorrect email or postal address. To create a rule for members with bad emailing address you select 'Bad Email' and select 'Email' as the Method. To use 'Bad Mailing Address' select 'Mail' as the method. |
Custom SQL Query | This is an advanced option that allows users with a technical knowledge of the system and database to write customised rule parameters that returns a list of Membership IDs. |
See also:
Comments
0 comments
Please sign in to leave a comment.