In-app messages
Not every nudge belongs in an inbox. Show a banner, modal, slideout, or tooltip right where a customer is working: targeted to a segment, scoped to the pages that matter, and capped by frequency so it never nags. In-app messages share Banchurn's audience model and merge tags with email, so one lifecycle state can greet a power-user on-screen and win back an at-risk account by inbox.
Email is the only channel, so half your customers never hear you
The customer who stopped logging in won't open your email either. The moment that actually matters (when they're in the product, one step from the feature that would save them) is exactly when an email can't reach them, and most tools have no way to say anything there.
The flow, end to end
Compose
Pick a type (banner, modal, slideout, tooltip) and write the content, with merge tags for personalization.
Target
Choose the segment and the page rules that decide who sees it, and where.
Cap
Set frequency and an impression cap so it shows exactly as often as it should.
Activate
Turn it on; the SDK matches and renders it in-product, and every impression is tracked.
What's in the box
Four message types
Banner, modal, slideout, and tooltip: pick the format that fits the moment, from a quiet nudge to a full announcement.
Segment-targeted
Show a message only to members of a segment (at-risk, trial-ending, power-user) or to everyone.
Page & URL rules
Scope a message to the exact pages it belongs on with exact, contains, or regex URL rules.
Frequency caps
Show once or on a cadence, with an impression cap per customer so nothing ever nags.
Merge tags
Personalize with the same subscription and trait variables your emails use: name, plan, feature, renewal.
Scheduling & priority
Window a message with start and end dates; priority decides which one wins when several match.
The same audience, reached wherever they are
In-app messages read the same segments, traits, and merge tags as your email, so a single lifecycle state can drive a banner on-screen and an email in the inbox, without maintaining the customer logic twice. Email carries the reach; in-app catches the moment.
- ✓One audience model shared with email and automations
- ✓The same merge tags: subscription and any trait
- ✓Banner, modal, slideout, or tooltip per moment
The right message, on the right page, never nagging
Page rules put a message only where it belongs, frequency and per-customer impression caps keep it from repeating, and priority resolves which message wins when several match, so in-app stays helpful, not noisy. An automation can fire one the moment a customer enters a state.
- ✓Exact / contains / regex page targeting
- ✓Frequency and impression caps per customer
- ✓Fired on lifecycle entry straight from an automation
Campaigns
Batch or triggered, to a segment or a list: one campaign model covers every send you need.
Learn moreAutomations
A visual journey builder: trigger on any event or when a customer enters or leaves a lifecycle state, then send email or in-app, wait, branch, and act.
Learn moreSegments & lists
Dynamic, rule-based segments that keep themselves up to date, plus static lists you control by hand.
Learn moreStop losing customers you could have kept
Book a walkthrough and see churn prediction, account signals, segments, campaigns, destinations, and Autopilot working together, on one platform.