🎯 Discount Manager: Creating Variants and Rules
Overview
Variants control:
-
who sees the offer
-
what they see
-
whether they receive a push notification
Basic settings
Variant Name
Internal label
Status
Active / Inactive
Priority
Higher priority = evaluated first
Default Variant
Fallback if no rules match
Rules (the most important part)
Rules define who qualifies.
Each rule includes:
-
field (e.g. days since first seen)
-
operator (e.g. greater than)
-
value(s)
Common rule examples
New users (first 7 days)
-
Days since first seen → Between → 0 and 7
Push-enabled users
-
OS status → Equals → 1
Specific customer
-
First party ID → Equals → customer ID
Variant content
Define what the user sees:
-
title & subtitle
-
badge (e.g. “App Exclusive”)
-
discount label
-
discount code
-
button text & action
-
images & styling
Button actions
-
Reveal code
-
Copy code
-
Open URL
Push notifications
You can trigger a push when a user matches:
Key settings
-
Send Mode → when to queue
-
Max pushes → limit per user
-
Delay → send later
-
Cooldown → prevent repeats
What is “Cooldown Days”?
Cooldown prevents repeated pushes too quickly.
Example:
-
Cooldown = 7
→ user cannot receive another push for this variant for 7 days
Recommended setup
-
2–3 targeted variants
-
1 default fallback
-
clear priority order
Common mistakes
-
no default variant
-
incorrect operator
-
overlapping rules
-
push enabled without valid user (no OneSignal ID)