OneSignal Agency
BMO Media sets up and runs OneSignal push notifications for consumer apps and DTC brands: SDK or web push setup with your developers, two-step opt-in prompts, data tags, segments, Journeys and in-app messages, all capped against your email and SMS. The first step is an audit of your opt-in rate, reachable audience and block rate.
What we do
Why a OneSignal specialist, not a generalist
OneSignal is easy to install and easy to waste. Airship puts median push opt-in at 53.3% on Android and 48.85% on iOS, with retail apps on iOS falling as low as 18.1% (Airship Mobile App Push Notification Benchmarks for 2026, 2025 data). The gap between the median and the floor is not the platform. It is when the prompt fires, what the user was told before it, and whether the first notifications were worth allowing.
A generalist installs the SDK, fires the system prompt on first launch and broadcasts to everyone who allowed it. On iOS that spends the one system prompt you get: once a user taps Don't Allow, only a trip to Settings brings them back. A specialist shows a primer first, writes data tags from real behavior, builds segments on them, runs Journeys that exit the moment the customer buys on any channel, and treats opt-out and block rate as the health metric.
The method is the same on every platform we run: for Centr, a fitness app and membership brand on Braze, we aligned email, push and in-app messaging into one lifecycle, and rebuilt onboarding lifted trial-to-paid conversions by 20%.
What's included
What we do inside OneSignal
An implementation spec for your developers: the OneSignal SDK in your iOS, Android, React Native or Flutter build, or the web push service worker, with the external ID set at login so every channel resolves to one customer.
A two-step opt-in: an in-app primer shown after a moment of value, such as a first order, a saved item or a shipped order, with the system prompt only after a yes.
Data tags written from behavior (last category viewed, cart value, subscription status, order count), so every segment reflects what a customer did, not when they installed.
Journeys built in revenue order: cart and browse abandonment, back-in-stock, price drop, onboarding and win-back, each with an exit the moment the customer converts anywhere.
Frequency caps and quiet hours shared with email and SMS, so a shopper who got a cart email at 10:00 never gets a push about the same cart at 10:05.
Live Activities on iOS for order status, from confirmed to out for delivery, which puts the answer to 'where is my order' on the lock screen.
In-app messages for what push should not carry: subscription offers, review asks and feature tours, shown in session to people already in the app.
Opt-out and block rate tracked by message type, with any type that drives unsubscribes paused until it is rewritten or retargeted.
OneSignal features we lean on
Journeys: multi-step flows that branch on what the user did, with wait steps and exits, running push, in-app, email and SMS from one flow.
Segments and data tags: tags carry the behavior, segments read them, and suppression segments keep recent buyers out of recovery messages.
In-app messaging: the opt-in primer, onboarding steps and offers, triggered in session so they reach active users without spending a push.
Live Activities: order and delivery status on the iOS lock screen, updated as the order moves, the kind of push customers are glad they allowed.
Web push: the same segments and Journeys for your site, planned around iOS, which only delivers web push to sites installed to the home screen.
OneSignal AI: we treat its suggestions as test candidates and judge them against a control group, not as settings to accept.
Switch on data tags first: every segment, Journey and cap on this list depends on them.
When OneSignal is the right platform
OneSignal sends 1.3 trillion messages a year for 200,000 apps (OneSignal, October 2026), so scale is not the question; fit is.
Platform | Best fit | Where it falls short |
|---|---|---|
OneSignal | Apps and sites that want mobile push, web push and in-app messaging in one tool, with developers who can install an SDK | Most brands keep email in a dedicated ESP, so caps span two tools; revenue reporting depends on the purchase events you send in |
Braze | Mobile-first apps at scale that need real-time data and push, in-app, email, SMS and Content Cards on one platform | Heavier to implement and quote-only pricing; more platform than most push programs need |
Brevo PushOwl | Shopify stores that want web push with ready-made back-in-stock, price drop and cart triggers | Shopify only, and on 23 Oct 2026 its Shopify App Store listing read 'This app is not currently available on the Shopify App Store' |
Klaviyo push | Shopify brands with a native app whose email and SMS already run in Klaviyo | Mobile app push only in this comparison, so it needs a native app on Klaviyo's SDK; push is a supporting channel there |
Choose OneSignal when push and in-app are core channels and your developers can own the SDK.
Choose Braze when the app is the business and the data volume justifies a heavier build.
For a Shopify store with no app, start with our Shopify web push with PushOwl page.
Results
Results from our push and in-app programs
Both sets of figures below are published on the linked case studies. Centr runs on Braze and Spoonful of Comfort on Klaviyo.
Centr, on Braze: email, push and in-app messaging aligned across acquisition, free trial, paying and win-back segments; a 20% lift in trial-to-paid conversions from rebuilt onboarding; $1.9M+ in CRM-attributed revenue in the BFCM season alone; engagement 2.5x higher year over year in key sale periods.
Spoonful of Comfort, on Klaviyo, owned channels at peak with segments and caps holding: email and SMS attributed revenue up 196.9% year over year in BFCM 2025, 46.1% of BFCM revenue from owned channels, and 64.91% of Cyber Monday revenue from email and SMS.
Push joins that system as the fastest, cheapest layer, which is why caps come before campaigns.
Process
How we work in a OneSignal account
Audit, week one: with view access to your OneSignal dashboard, we read opt-in rate by platform and prompt, reachable audience against monthly active users, data tag and external ID coverage, what each Journey earns, and opt-out and block rate. We benchmark your opt-in against Shopping apps at 36% on Android and 33.2% on iOS (OneSignal Mobile App Benchmarks 2024). You keep the audit.
Scope with your developers: SDK updates, data tags, deep links and Live Activities go into one written spec, sized before work starts and tested on real devices, so engineering time is a known number rather than an open ticket.
Build in revenue order: the primer and prompt timing first, then cart and browse abandonment, back-in-stock and price drop, then onboarding and win-back, with caps and quiet hours set before the first campaign goes out.
Report monthly: opt-in rate, reachable audience, revenue per thousand reachable users, revenue by Journey, and opt-out and block rate, with lift measured against a holdout, the attribution window held constant, and what changes next month.
Who it's for
Who our OneSignal agency works best with
Consumer apps such as fitness, membership and subscription products, and DTC brands with an app or heavy mobile web traffic, already running OneSignal or choosing it. The best fit has developers who can ship SDK changes and nobody who owns push strategy, revenue or block rate. We are a poor fit for brands that want daily broadcasts to everyone, apps with no developer access at all, and stores with too little return traffic to build a push audience. For push as part of a wider lifecycle, see our push notification service. Want to know what your push audience could earn? Book a OneSignal audit.
Frequently asked questions