Push Notifications in IZI: Setting Up Campaigns via Automation
Push Notifications in IZI: Setting Up Campaigns
Section titled “Push Notifications in IZI: Setting Up Campaigns”Notifications in IZI work through the IZI mobile app — no SMS, no third-party mailing service. Set up once through an automation rule: event fires → client receives the message instantly. Below — how this is assembled technically and how to build campaigns that work rather than annoy.
How the Delivery Channel Works
Section titled “How the Delivery Channel Works”A notification in IZI is one of the actions in an automation rule. There is no standalone “send a message” without an event — only through a rule.
Notification path:
- Client event (top-up, session end, rank reached)
- Automation rule checks conditions
- If met — IZI queues the notification
- IZI app on the client’s phone receives the notification via the device push service (APNs for iOS, FCM for Android)
- Client sees the notification
Three conditions for delivery:
- Client has the IZI mobile app installed
- Client is logged into the app
- Notifications from the app are enabled on the device
If any one condition is not met — the notification is not delivered. In the rule history, the status will be “Completed” — IZI sent it from its side; non-delivery happened at the client’s device level.
Parameters of the “Send Notification” Action
Section titled “Parameters of the “Send Notification” Action”| Field | Limit | Recommendation |
|---|---|---|
| Title | Up to 40 characters | Specific and value-driven: “Bonus awarded,” “New rank!,” “Bar order cashback” |
| Message | Up to 120 characters | One concrete action: what happened + what the client can do |
Variables in notification text: The same variables as in action formulas work in the text. The full list depends on the rule’s trigger event.
| Variable | Event | Contains |
|---|---|---|
{{topup_amount}} | Balance top-up | Top-up amount |
{{order_total}} | Order payment | Order amount |
{{session_duration}} | Session ended | Duration in seconds |
{{total_hours}} | Any | Client’s total hours |
Typical Campaigns and Templates
Section titled “Typical Campaigns and Templates”Campaign 1 — Top-Up Bonus
Section titled “Campaign 1 — Top-Up Bonus”The most important scenario. Client topped up — received a notification that the bonus was credited.
Setup:
- Event: Balance top-up
- Conditions: amount threshold if a bonus ladder is in use
- Action 1: Award bonuses — ladder formula
- Action 2: Send notification
| Field | Text |
|---|---|
| Title | ”Bonus awarded!” |
| Message | ”Thank you for topping up. Bonuses are in your account — use them on your next session.” |
Place the notification after the bonus award in the action order. That way, when the client opens the app, the bonus is already in their account.
Campaign 2 — New Rank Achieved
Section titled “Campaign 2 — New Rank Achieved”Fires when a client is moved to a rank group. Rank-related notifications are the most motivating.
Setup:
- Event: Group assigned
- Condition: Group = target rank
- Action: Send notification
| Rank | Title | Message |
|---|---|---|
| Bronze | ”Welcome to the program!" | "Bronze rank — you’re already part of the club. Play more, climb higher.” |
| Silver | ”You’ve reached Silver!" | "Silver unlocked. Gold is just a bit further — keep it up!” |
| Gold | ”Gold rank!" | "Congratulations! You’re among the best clients. Special perks are now active.” |
Campaign 3 — Bar Order Cashback
Section titled “Campaign 3 — Bar Order Cashback”Reinforces the habit of ordering through the app.
Setup:
- Event: Order payment
- Condition: optionally — order amount ≥ threshold, to avoid notifying on every coffee
- Action 1: Award bonuses —
{{order_total}} * 0.05 - Action 2: Send notification
| Field | Text |
|---|---|
| Title | ”Cashback for your order” |
| Message | ”Your order earned cashback. Bonuses in your account — spend them on gaming time.” |
Campaign 4 — Welcome on First Session
Section titled “Campaign 4 — Welcome on First Session”Locks in the first visit. Full guide → Creating Your First Rule.
| Field | Text |
|---|---|
| Title | ”Welcome!” |
| Message | ”Great to have you! Welcome bonuses are in your account — use them on your next visit.” |
Campaign 5 — Dormant Client Reactivation
Section titled “Campaign 5 — Dormant Client Reactivation”Client hasn’t visited in 14+ days → notification with an offer. Full mechanics → Anti-Churn Automation.
| Field | Text |
|---|---|
| Title | ”We miss you!” |
| Message | ”It’s been a while. Bonuses waiting — come play.” |
Managing Campaigns
Section titled “Managing Campaigns”Creating a campaign: Each campaign = one or more automation rules. Navigate: Automation → Create Rule → configure event, conditions, “Send notification” action.
Enabling/disabling: “Rule active” toggle on the rule card. A disabled rule is not deleted — it’s saved with all settings.
Temporary campaign (promotion): For a time-limited promotion — enable the rule for the promotion period, disable after. Or add a date condition to the rule if that’s supported.
Checking delivery: Open the rule → History tab → find the client entry. Status “Completed” means IZI sent the notification. “Read/unread” statistics are not available in the current CRM version.
Message Template Principles
Section titled “Message Template Principles”A good notification = value + action, in 120 characters.
Structure:
- What happened (bonus awarded, rank reached, cashback)
- What it means for the client (how much, what to spend it on)
- Call to action (if needed)
Examples:
| Bad | Good |
|---|---|
| ”Notification from the club" | "Bonus awarded!" |
| "You have been credited with a reward for using the service" | "+50 bonuses for top-up. Bonuses in your account — spend on sessions." |
| "New status in the loyalty program" | "You’ve reached Silver! Gold is just a bit further.” |
Write like a person, not a corporate auto-reply. The 120-character limit is your ally, not your enemy: it forces you to be specific.
Diagnostics
Section titled “Diagnostics”Client not receiving notifications:
- Confirm the client has the IZI mobile app
- In the rule history, find the entry for this client — status should be “Completed”
- Ask the client to check device settings: iOS — Settings → IZI → Notifications; Android — Settings → Apps → IZI → Notifications
Rule fires but notification doesn’t send: Open the history entry with details. Check that the “Send notification” action is not placed after an action that errored — if a preceding action fails, subsequent ones don’t execute.
What Cannot Be Done via Notifications
Section titled “What Cannot Be Done via Notifications”- Notification about upcoming bonus expiry — the “Bonuses expiring soon” event is not in the current trigger catalog
- Mass manual broadcast to the entire database — notifications only go through event-based rules, not a “send to all” button
- Custom channels (SMS, email, Telegram) — delivery channel is only through the IZI app
More on best practices and anti-spam approach → Automation Best Practices.
See Also
Section titled “See Also”Frequently asked questions
Through which channel do notifications reach clients?
Only through the IZI mobile app. No separate mailing service is needed — notifications are delivered directly through the app instantly when a rule fires.
How many characters in the title and body of a notification?
Title — up to 40 characters. Message body — up to 120 characters. Brevity is required: a mobile screen shows the first 2–3 lines; the rest is cut off.
Will a notification reach a client without the mobile app?
No. Notifications only reach those who have the IZI app installed and notifications enabled. Clients without the app or without active authorization won't receive the notification — this is not a system error.
Can the amount of the awarded bonus be inserted into the notification?
Yes. Event variables work in notification text — the same ones as in award formulas. For example, {{topup_amount}} substitutes the top-up amount.
Can a notification be sent manually to a specific client?
In the current version, manual notification sending without an automation rule is not available. All notifications go through rules.
Can a schedule be set — sending notifications only at certain times of day?
A direct send schedule isn't configurable — the notification goes out at the moment the event fires. To restrict by time — add a schedule condition to the rule; then events at the 'wrong' time simply won't trigger a firing.
How many notifications does a client receive per day?
As many as the number of rules that fired that day. There's no automatic limit — frequency is controlled by the owner through rule design. Recommendation: maximum 1–2 meaningful notifications per day.