Point a one-off send at the segment. Open + click numbers update live.
Target what they do. Not just what they are.
Stack conditions on any event, any property, any score. The segment updates the moment someone qualifies — or stops qualifying. One definition, used everywhere.
- ASAarav ShahVIP · ₹84K LTV · last opened 2h ago
- PKPriya KhannaSubscriber · ₹52K LTV · opened 4 of last 5
- RMRohan MehtaVIP · ₹71K LTV · cart abandoned today
- DADevika AnandSubscriber · ₹48K LTV · clicked pricing twice
- SKSneha KapurVIP · ₹95K LTV · last reply 3 days ago
Other tools give you yesterday’s list. We give you right now.
Build the condition once. The segment populates immediately, and updates the second any included contact stops matching — or any excluded one starts.
One definition. Four places it works.
Same segment in a campaign, a flow, a report, a branch. Edit it in one place and every usage updates. No three-tabs-of-the-same-audience.
Use as the entry condition. Contacts enter as they qualify, exit when they stop.
Compare two segments side by side — revenue, retention, AOV, deliverability.
Use as a flow branch condition. Same definition, used everywhere.
Things teams check first.
How fast does a segment refresh?
Live. As soon as an event fires for a contact, Bluey re-evaluates segment membership. Practically: under one second between event and segment-state change.
Can a contact be in more than one segment?
Yes. Segments are dynamic membership lists, not exclusive buckets. A contact is in every segment whose conditions they currently match.
What if I want a one-time static list?
Snapshot any segment to a static list with one click. Useful when you want to send to 'whoever qualifies at this moment' regardless of later changes.
Build the segment. Use it everywhere.
Drop conditions in. See contacts populate live. Point a campaign, a flow, a report at it.