Segment-Based Audiences for Experiences
On-site and in-app nudges can now target any existing FirstHive segment, so the audience matches the one you use on every other channel.
The problem
When building an Experience (an on-site or in-app nudge), you could only target All Customers, or try to rebuild an audience by hand with Where and When conditions. You couldn’t point a nudge at a segment that already existed in FirstHive.
That meant:
- Rebuilding targeting logic that already existed for email, SMS and other channels
- Slower launches for every nudge
- On-site audiences that quietly drifted away from the official segment definition, making reporting inconsistent
How it solves the problem
In the Audience Selection step of the Experience Builder, you can now choose an existing segment under Select Audience.
- Any segment works: both static (list-based) and dynamic (rule-based) segments.
- See before you publish: the segment’s member count and last-refreshed time appear right in the builder.
- Always current: when a dynamic segment’s rules or members change, the nudge follows automatically. No need to reopen or resave the Experience.
- Fast for visitors: segment membership is prepared in advance, so the check happens in milliseconds and never slows the page or app.
- Nothing else changes: All Customers and your When, Where and Content settings work exactly as before.
Use cases
| Who | Use case |
|---|---|
| Lifecycle marketer | Show a reminder banner only to the “Cart abandoners, last 7 days” segment already used in email |
| CRM analyst | Report on a nudge using the same audience definition as other channels |
| Growth team | Offer an app-only discount to a high-value segment without rebuilding the rules |
Good to know: one segment per Experience in this release. Combining segments and Exclusions are planned for later.