Push at the right moment, not every moment.
Use real-time audiences to send one-time, recurring and triggered notifications to your mobile app and to the browser. Respect quiet hours and frequency limits while deep links take each customer to the next useful action.
Your cart is waiting
Complete your order while your items are still available.
One-time
Schedule a launch, service message or limited campaign for every reachable profile in one or more audiences.
Recurring
Run daily, weekly or monthly in the account's timezone while the audience is resolved again for each send.
Triggered
Respond to a customer state such as an abandoned cart after the configured delay and eligibility checks.
Cart recovery with customer context
A reminder is sent only after the shopper, cart and timing rules agree.
Qualification controls
- • Configurable delay after cart activity
- • Minimum cart value
- • Audience eligibility
- • Per-customer reminder frequency
- • Quiet hours in the account timezone
Useful message context
- • Item count, cart total and first item name
- • Images, sounds and app deep links
- • Custom data payloads
- • TTL and collapse-key controls
- • Android notification channel
Two transports, one module
Most of your audience will never install an app. Web push reaches them in the browser, and it is not a separate product with separate rules — the campaigns, the audiences, the delivery policy and the reports are the same ones.
Mobile push
- • Your own Firebase project, credentials encrypted at rest
- • iOS and Android, with an Android notification channel
- • App deep links, sounds and custom data payloads
- • Invalid tokens pruned automatically after a send
Web push
- • Your own VAPID key pair, generated in the panel or pasted in
- • Chrome, Edge, Firefox, Opera, Samsung Internet and Safari
- • A service worker snippet with your account details filled in
- • No app, no SDK and no store review
One person, one message. Frequency caps and quiet hours are counted per customer, so a phone and a browser share a single budget rather than doubling it. A campaign can name the platforms it was written for, and the filter is applied before the newest-device pick — so a browser-only campaign finds a person's newest browser instead of skipping them because their newest device is a phone.
Delivery controls that protect the experience
Frequency caps: limit non-triggered pushes per profile per day.
Fresh-device selection: choose a recently active device and deduplicate shared tokens.
Reliable batching: divide sends into provider-safe jobs, retry transient failures and remove invalid tokens.
Reporting: track targeted, sent, delivered, failed and invalid-token outcomes by campaign and day.
Campaign delivery
Illustrative interface values
Make push part of the customer journey.
Coordinate real-time audience data, respectful delivery controls and measurable outcomes in one platform.
Plan your first campaign