Special Occasion Scratch Card Promo

Engage contacts during seasonal campaigns with a gamified scratch card pop-up revealing a limited-time promo code.

Goals

Improve conversion and sales

Encourage repeat sales

Improve personalization and the customer experience

Industries

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Description

This use case introduces a gamified scratch card pop-up that activates during key seasonal events such as Black Friday, Christmas, or Easter. By surprising contacts with an interactive experience, brands can dramatically boost campaign engagement and increase conversions using a pre-generated universal discount code. The system ensures that each contact sees the scratch card only once, avoids over-promotion through capping, and tracks all interactions for performance insights. This festive, high-impact mechanic is ideal for driving short-term sales spikes while enhancing the customer experience.

Implementation Effort

Impact on a goal

Assets

No items found.

Outcome

Increased contact engagement during promotional events

Higher conversions from seasonal offers

Reduced friction through a universal, easy-to-redeem promo code

Detail user scenario

During the defined festive period, contacts visiting the website may see a scratch card pop-up designed to reveal a generic promotional code. The system first checks whether the contact has already revealed the code to prevent repeated exposure. If not, and if the contact is not capped, the pop-up is displayed. Viewing the pop-up triggers tracking events and adds the contact to a capping segment. When the contact scratches to reveal the code, another event logs the reveal. The code is pre-generated in the e-commerce system and valid only during the promotional period, ensuring controlled and appropriate usage.

Step-by-step

1
Seasonal visit and eligibility check: When a contact visits the website during the special occasion period, the system checks whether a Pop-up scratch card revealed event already exists for the defined scenario (e.g., Black Friday 2026). If it exists, the contact is excluded from the flow
2
Capping verification: If the contact has not previously revealed the code, the system checks whether they belong to the Capping pop-up segment. If not, they are eligible to see the scratch card
3
Scratch card display and interaction tracking: A global pop-up appears on all pages, inviting the contact to scratch and reveal a seasonal promotional code. When shown, the system creates a Pop-up scratch card view event and adds the contact to the Capping pop-up segment
4
Promo code reveal event: When the contact scratches the card and the code becomes visible, the system generates a Pop-up scratch card revealed event with the relevant scenario attribute
5
Controlled festive usage: Because the promotion is active only during a defined seasonal timeframe, teams must enable the automation exclusively during those dates to avoid misuse of the generic code

Detail user scenario

Step-by-step

1
Seasonal visit and eligibility check: When a contact visits the website during the special occasion period, the system checks whether a Pop-up scratch card revealed event already exists for the defined scenario (e.g., Black Friday 2026). If it exists, the contact is excluded from the flow
2
Capping verification: If the contact has not previously revealed the code, the system checks whether they belong to the Capping pop-up segment. If not, they are eligible to see the scratch card
3
Scratch card display and interaction tracking: A global pop-up appears on all pages, inviting the contact to scratch and reveal a seasonal promotional code. When shown, the system creates a Pop-up scratch card view event and adds the contact to the Capping pop-up segment
4
Promo code reveal event: When the contact scratches the card and the code becomes visible, the system generates a Pop-up scratch card revealed event with the relevant scenario attribute
5
Controlled festive usage: Because the promotion is active only during a defined seasonal timeframe, teams must enable the automation exclusively during those dates to avoid misuse of the generic code