Segmented Broadcasts in IZI: Sending Notifications to the Right Group
यह कंटेंट अभी तक आपकी भाषा में उपलब्ध नहीं है।
Segmented Broadcasts in IZI
Section titled “Segmented Broadcasts in IZI”A segmented broadcast in IZI is a notification that only a needed portion of the database receives — not every client. Implemented through automation rules: a group condition filters recipients, the “Send notification” action delivers the message. Works through the IZI mobile app — no SMS or external mailing services.
Segmentation Logic in IZI
Section titled “Segmentation Logic in IZI”In IZI, segmentation = client groups. A client belongs to one or more groups. A group can be a rank (Bronze/Silver/Gold), a behavioral segment (VIP, Newcomers, Students), or a temporary tag (promotion participants, dormant clients).
An automation rule filters by group through a condition:
- “Client group = VIP” → notification to VIP clients only
- “Client group = Gold” → only Gold-rank clients
- “Client group ≠ Blacklist” → everyone except blocked clients
Multiple conditions are combined via AND or OR, enabling complex combinations.
Step 1 — Define the Segment
Section titled “Step 1 — Define the Segment”Before creating the rule, decide who you’re sending to and why.
Typical segments for broadcasts:
| Segment | Group in IZI | Typical Scenario |
|---|---|---|
| High-value clients | Gold / VIP | Exclusive access, personal offers |
| Regulars without decline | Silver | Motivation to grow to Gold |
| Newcomers (under 30 days) | Newcomers | Engagement, program explanation |
| Students | Students | Weekday promotions |
| Promotion participants | Temporary group | Reminder of promotion terms |
If the needed segment doesn’t exist as a group yet — first create the group and populate it with clients (manually or via automation). How groups work → Client Base in IZI.
Step 2 — Estimate the Audience
Section titled “Step 2 — Estimate the Audience”There is no direct “audience preview” before launch — but reach can be estimated manually.
Navigate: Clients → filter by the target group → see the count in the list header. This is the maximum reach. Actual reach will be lower — some clients don’t have the IZI app or have notifications disabled.
Guideline for app-using client share: depends on the club, typically 30–60% of the active base. Higher if the mobile app is actively promoted.
Step 3 — Create a Segmented Broadcast Rule
Section titled “Step 3 — Create a Segmented Broadcast Rule”Navigate: Automation → Create Rule.
Example: Promotional Notification for VIP
Section titled “Example: Promotional Notification for VIP”Task: notify VIP clients of a special weekend offer.
| Element | Setting |
|---|---|
| Name | ”VIP weekend promotion — notification” |
| Trigger event | Session ended |
| Condition 1 | Client group = VIP |
| Action | Send notification |
| Title | ”VIP only: weekend bonus” |
| Message | ”This weekend — double bonus on top-up for you. Come in!” |
Example: Motivating Silver Clients Toward Gold
Section titled “Example: Motivating Silver Clients Toward Gold”Task: remind Silver-rank clients how many hours remain until Gold.
| Element | Setting |
|---|---|
| Name | ”Silver → progress toward Gold” |
| Trigger event | Session ended |
| Condition 1 | Client group = Silver |
| Condition 2 | Hours played ≥ 35 (i.e., <15 remaining until Gold) |
| Action | Send notification |
| Title | ”So close to Gold!” |
| Message | ”You’re almost at Gold rank. Keep visiting — you’re nearly there!” |
Example: Reminding Newcomers About the Program
Section titled “Example: Reminding Newcomers About the Program”Task: tell clients in their first month about the bonus system.
| Element | Setting |
|---|---|
| Name | ”Newcomers — about the bonus program” |
| Trigger event | Session ended |
| Condition 1 | Session count = 3 (third session) |
| Action | Send notification |
| Title | ”Know about bonuses?” |
| Message | ”Top up your balance — earn bonuses. The more you top up, the higher the percentage.” |
No group condition is used here — filtering by session count instead. This is also a form of segmentation: “clients on their third session.”
Step 4 — Launch the Campaign
Section titled “Step 4 — Launch the Campaign”After configuring the rule, enable the “Rule active” toggle and save.
For a temporary campaign:
- Enable the rule on the promotion start day
- Disable the rule when the campaign should end
- Don’t delete it — it’ll be useful next time
Step 5 — Measure Results
Section titled “Step 5 — Measure Results”Open the rule → History tab. You can see:
- How many times the rule executed in a period (entries with “Completed” status)
- For which clients
- When exactly
“Read/unread” statistics are not available in the current version. An indirect measure of campaign effectiveness: growth in top-ups or visits from the target segment during and after the campaign period.
Segmentation Without a Group: Filter by Metrics
Section titled “Segmentation Without a Group: Filter by Metrics”Sometimes the needed segment doesn’t exist as a ready group. Filtering directly through rule conditions is possible:
| I Want to Send To | Rule Condition |
|---|---|
| Clients with balance below 100 | Gaming balance < 100 |
| Those who played more than 20 hours | Hours played ≥ 20 |
| Those who spent above a certain amount | Amount spent ≥ N |
Combine conditions to match your scenario.
Managing Multiple Campaigns
Section titled “Managing Multiple Campaigns”With multiple active notification rules, a client may receive several messages per visit. Monitor overlaps:
- Open the automation list — see all active rules with a “Send notification” action
- For each client segment, estimate how many notifications they can receive per session
- If more than 1–2 — revisit conditions or frequency
More on spam prevention → Automation Best Practices.
Typical Mistakes
Section titled “Typical Mistakes”| Mistake | Consequence | Solution |
|---|---|---|
| No group condition | Notification goes to the entire database | Add “Client group = …” condition |
| Rule not disabled after promotion | Clients receive outdated offers | Disable temporary rules after campaign ends |
| Condition too broad | Notification fires too often | Add additional conditions to narrow the audience |
| No clients in the group | Zero reach | Check group population before launching |
See Also
Section titled “See Also”अक्सर पूछे जाने वाले सवाल
Can a notification be sent to only one segment, not the entire database?
Yes. In the automation rule, add condition 'Client group = target group.' Then the 'Send notification' action will only execute for clients in that group.
How do you send a notification to the entire database at once?
Create a rule without group conditions. The notification will reach all clients who experience the trigger event — for example, everyone who tops up their balance on a given day.
Can you see in advance how many clients will receive the notification?
There is no direct audience preview before launch. To estimate reach — go to the Clients section, filter by the target group and see the member count.
How do you measure campaign results?
Through the rule firing history — it shows how many times the rule executed in a period. Open/unread statistics are not available in the current CRM version.
Can a group be excluded from a broadcast?
Yes — add condition 'Client group ≠ excluded group' or 'Client group not in list.' Clients from the excluded group won't receive the notification.
Is a segmented broadcast by last visit date possible?
Via automation conditions, filtering by accumulated client data is possible. For scenarios like 'hasn't visited in N days,' triggered mechanics are more appropriate — see the triggered messages section.