1. Introduction.
With Cool Tabs' AI Ticket Validation feature, you can create campaigns where users upload a photo of their purchase receipt and the platform automatically analyzes if it meets the requirements of your promotion.
It also allows you to set up validation rules to identify key elements such as the store, date, amount, or purchased products, ensuring that only tickets that meet these conditions are considered valid.
This tool is ideal for raffles, cashback, or purchase-based promotions, enabling you to automate verification, reduce fraud, and speed up participation.
How AI ticket validation works:
Purchase: User purchases at a participating store.
Campaign access: Enters the promotion's landing page.
Form: Fills in their personal details.
Ticket upload: Attaches a photo of the purchase receipt.
Processing: The AI analyzes and detects store, date, amount, and/or products.
Validation: The AI compares the data with the campaign rules (amount, dates, store, products, etc.).
-
Result:
Valid: user participates automatically.
Invalid: errors are shown and the user can try to upload another ticket, according to the allowed number of attempts.
Manual review (optional): If attempts are exhausted or there are doubts, the ticket can be reviewed manually.
TRY THE AI TICKET VALIDATION DEMO
2. Examples and use cases.
A) Promotion among different stores within the same group or shopping center.
Allows several stores to join the same campaign, encouraging purchases within the shopping center and providing automatic control over which tickets are valid.
For example, a joint promotion by a shopping center during the summer period. Only tickets from stores belonging to the XYZ shopping center are valid.
How it works:
Participants shop at any store in the XYZ shopping center.
They upload a photo of the ticket to the campaign.
The AI identifies the name of the establishment on the ticket and compares it with the list of authorized stores. Other validation conditions can be included, such as a minimum amount or a specific purchase period.
Valid tickets participate in a raffle.
B) Purchase within a specified period.
Ensures that only purchases made during the promotion period are valid and prevents old tickets. For example, a brand is organizing a promotion for customers who buy during Christmas.
How it works:
The participant buys brand products between December 1 and 24.
Uploads a photo of the ticket to the campaign.
The AI extracts the ticket date and compares it with the configured range.
If the date falls within the period, the ticket is validated, and the user enters the raffle.
C) Purchases of a new product for a certain amount.
Encourages the purchase of a new product, for example, a coffee, and automates validation more quickly.
How it works:
The customer buys the brand's new XXX coffee
Uploads the ticket to the campaign.
The AI validates that the XXX coffee was purchased and that the total product amount is ≥ €10.
If the ticket is valid, the user accesses the specific promotion. For example, a partial refund or cashback that the user can use on their next purchase.
3. Step-by-step setup.
3.1. Create the campaign.
The first step is to create your campaign and set up the basic aspects. This includes defining the name, start and end date, and general settings to ensure proper operation.
If this is your first campaign in Cool Tabs, we recommend following our step-by-step tutorial, where we explain how to set up the main sections and other recommended settings to maximize your promotion's results.
Tutorial: How to start creating a campaign. Basic settings.
If you have any questions while creating your campaign, write to us at help@cool-tabs.com and our team will help you quickly.
3.2. Activate validation.
Go to Entries > Restrictions > Purchase receipt validation with AI
Activate the AI Ticket Validation option
Click the Edit validation conditions button
3.3. Set up validation rules.
Define the validation rules that will indicate when a ticket is considered valid. These rules allow the artificial intelligence to automatically analyze the ticket's information and check that it meets the promotion's requirements, such as the purchase period, minimum amount, store, or presence of specific products.
- Click Add Rule.
Select the type of rule to create. You can choose from: amount, store name, store address, date, and product name. Add as many as you need.
3.3.1. Ticket amount.
Allows you to check that the total ticket amount falls within a specified range. This is especially useful for promotions that require a minimum spend, a maximum limit, or both.
When creating a new validation rule of type Ticket amount, you can set the following fields:
Error message for the user: This is the text that will be shown to the participant if their ticket does not meet the required amount. Example: The ticket must be more than €20.
Amount validation: Define the amount range that will be considered valid:
Minimum amount: the ticket must have a total equal to or greater than this value.
Maximum amount: the ticket cannot exceed this amount.
You can set only the minimum, only the maximum, or both, according to the promotion's conditions.
3.3.2. Store name.
Allows you to check that the ticket belongs to one or more authorized stores. This validation is especially useful in campaigns where only purchases made at certain stores, chains, or stores associated with a joint promotion are accepted.
When creating a new validation rule of type Store name, you can set the following fields:
Error message for the user. This is the text that will be shown to the participant if the ticket does not correspond to a valid store. Example: The ticket must be from LIDL or Mercadona.
List of valid stores. Enter the names of the stores that will be accepted in the promotion.
Example: LIDL, Mercadona, Carrefour.Regular expression for store name (optional). Advanced option that allows you to define a regular expression to recognize different variants of a store name as it may appear printed on the ticket.
3.3.3. Store address.
Allows you to check that a ticket comes from stores located in specific cities, areas, or addresses. This rule is useful when you want to limit the promotion to certain locations or regions.
When creating a new validation rule of type Store address, you can set the following fields:
Error message for the user. This is the text that will be shown to the participant if their ticket does not comply with the allowed address. Example: The ticket must be from a store in Barcelona, Madrid, or Valencia.
List of valid addresses. Enter the allowed cities, areas, or addresses.
Example: Barcelona, Madrid, Valencia.Regular expression for address (optional). Advanced option that allows you to use regular expressions to recognize variants or abbreviations of city or area names that may appear on tickets.
3.3.4. Ticket date.
Allows you to check that a ticket was issued within a specific date range. This is useful for campaigns that want to accept only recent tickets or from a specific promotional period.
When creating a new validation rule of type Date, you can set the following fields:
Error message for the user. This is the text that will be shown to the participant if their ticket does not comply with the date range.
-
Date validation. Allows you to define the date range that will be considered valid.
Minimum date: the ticket cannot be earlier than this date.
-
Maximum date: the ticket cannot be later than this date.
3.3.5. Line items.
Requires that the ticket include at least one of the products specified in the campaign list. This is useful for promotions focused on specific products, launches, or brand packs.
When creating a new validation rule of type Products, you can set the following fields:
Error message for the user. This is the text that will be shown if the ticket does not contain any of the required products.
List of valid products. Enter the names of the products you want to validate. The rule is met if any purchased product is on the list. For now, it is not possible to require that all products on the list are on the ticket.
Regular expression for products (optional). Allows you to define patterns to detect different variants of product names as they may appear on the ticket, offering greater flexibility in validation.
3.4. General settings.
In this section, you can define the maximum number of opportunities to upload a valid ticket that meets the campaign rules.
If a user uploads a ticket that does not meet the rules (for example, insufficient amount, date out of range, invalid store), a message explaining the reason will be shown.
After receiving this message, the user can submit another ticket to validate their participation.
The number you set here determines how many attempts they have to correct an invalid ticket.
Important: This number is independent of the number of entries allowed in the promotion.
3.5. Custom messages.
The next step is to customize the messages users will see during the ticket validation process. If you leave a message blank, a default system message will be displayed.
Types of messages you can customize
Screen to upload the ticket. This is the screen the user sees when attaching their ticket. Example: “UPLOAD YOUR TICKET. Make sure the store name, date, and amount are clearly visible.”
Message while the ticket is being processed. Message displayed while the AI analyzes the ticket. Example: “VERIFYING THE TICKET. We are checking that the ticket you uploaded meets the requirements. This process may take a few minutes.”
Invalid ticket due to system errors. Displayed when the AI cannot locate key elements such as store, date, or amount. Additionally, the unmet rules will be shown below. Example: "We could not validate your ticket. Please make sure to upload a ticket where the store name, purchase date, and total amount are clearly visible.”
Invalid ticket due to configured rules. Displayed when the ticket does not meet the rules you set (minimum amount, store, date, products…). Example: "It seems your ticket does not meet the requirements. Please review the promotion terms and make sure the minimum amount, purchase date, and store meet the indicated conditions.”
Maximum number of attempts reached. Displayed when the user can no longer upload tickets because they have used up their validation opportunities. You can use the variables
{{ email }}or{{ phone }}if requested by the user. Example: "You have reached the maximum number of attempts. Our team will review your ticket manually and contact you at the email {{email}} within the next few hours.”Error processing the ticket. Displayed when there is a technical problem (not related to the image), for example, a failure in the AI server. Example: “Oops… it seems something went wrong! We had a problem processing your ticket. Please try again in a few minutes.”
4. Other specifications.
AI ticket validation has an additional cost.
To let you try it out, your account includes 50 free credits, equivalent to 50 validations, included to test the feature with no obligation.
If you want to include it in your plan or have any questions, you can contact us at help@cool-tabs.com.
5. Related content.
How to create a campaign to validate promotional codes.
Comments
0 comments
Please sign in to leave a comment.