The live delivery stats let's you know and watch engagement happen in real-time. That is only one of the positive sides of using OneSignal.

The overall reliability of and breadth of SDKs available for different frameworks is really helpful. Besides that, free plan, we are currently using, is very generous, best offer out of all we have tested so far.

Look, the thing I value most about OneSignal is how it bridges our dev team and our marketing workflow without locking us into constant back-and-forth, which is huge for me as the E-Commerce & Operations Manager at Coastal Thread Apparel out of LA. Our brand is small, only 11–50 people, and we don’t have a big dedicated dev team on tap every single day. I juggle online store operations, new apparel drop launches, customer marketing campaigns, and regularly test out SaaS tools to see what fits our fashion brand’s needs. Before we started using OneSignal, getting any kind of personalized outreach out to our shoppers was a bottleneck. Our developer was swamped fixing inventory sync bugs, tweaking product page layouts, and prepping our site for seasonal drops. Every time I wanted to send segmented alerts for restocks, flash sales, or new tee launches, I had to put in a dev ticket and wait days to get it live. OneSignal changed that dynamic because the setup is straightforward for developers, but once it’s wired up, the marketer-facing dashboard is really approachable. Our dev knocked out the core web push, email and SMS connections in a single afternoon, and after that, I can build and schedule campaigns entirely on my own. I don’t need to pull them away from priority site work just to fire off a restock alert for our best-selling coastal hoodies. That independence makes such a difference around launch weeks, when timelines are tight and we need to move fast. I also love how many messaging channels live in one place. We use web push for site visitors who opted in, SMS for our loyal repeat customer group, and email for longer storytelling around limited runs and fabric updates. We even tested in-app messages for people browsing our mobile web store. Everything lives inside the same platform, with shared customer segments. Last month we dropped a new linen short collection. I built one segment for people who previously bought our linen pieces, another for followers who saved the launch announcement but hadn’t purchased yet, and a third group of subscribers who only shop our sale items. I sent a tailored push notification first to the linen repeat buyers with early access, then followed up with a softer SMS reminder to the second group an hour later. Being able to reuse those same segments across different channels keeps our messaging consistent and saves me from rebuilding lists in separate tools. The open API and webhook support is another big plus for our stack. We tie it to our online store so subscriber data stays aligned with purchase activity. When someone buys one of our pieces, our store feeds that event over, and OneSignal automatically adds them to a “recent buyer” segment for post-purchase nurture messages. We can trigger abandoned cart reminders automatically too, without messy custom code. It’s reliable enough that I don’t stress about messages failing to send mid-drop. And honestly, the personalization controls feel built for a small apparel brand. I can drop in dynamic tags for product names, size availability, and discount codes right inside messages. We ran a campaign last quarter alerting customers when their out-of-stock size restocked, and those notifications drove way more conversions than generic sale blasts. For a lean fashion team like ours, that’s the sweet spot. It’s powerful enough to handle multi-channel customer engagement and flexible through the API, but simple enough that I can own day-to-day campaign work without leaning on engineering for every small change. It keeps our customer communication agile around launches, restocks, and promotions, and takes a ton of pressure off our overstretched dev resource.