OneSignal Reviews & Product Details

What I like best about OneSignal is how many tools it gives me to engage users and grow my business in one place. I can easily send push notifications, create automated journeys, and send emails based on user behavior.

It makes it much easier to build consistent communication with my users, improve engagement, and automate important parts of the customer journey without having to manage several different platforms. Review collected by and hosted on G2.com.

I found it too difficult to add users to an audience... too many clicks to get it done. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

First off, the segmentation logic can get clunky once you start stacking multiple customer behaviors together. We sell a wide range of apparel, and I often want to build nuanced groups — like shoppers who purchased linen items in the last six months, opted into SMS, and haven’t checked out our new linen restock alert. Simple single-rule segments work great, but layering multiple filters gets confusing fast. I ran into this issue during our summer linen restock. I tried to exclude anyone who already grabbed the new drop so we wouldn’t spam recent buyers. The rule builder kept returning wonky results, and I ended up sending a push notification to a small group of customers who’d already purchased. That was an easy misstep to avoid if the filtering UI was clearer, and it made me double-check every segment three times after that.

Reporting is another area that feels pretty surface-level for an apparel e-commerce brand. I need to tie notification performance all the way back to actual sales: which push or SMS campaigns drove add-to-cart events, how many converted, and what average order value those customers hit. OneSignal shows opens, clicks and sends, but it doesn’t make it easy to map those metrics against our store’s revenue data natively. I have to export campaign CSV reports and manually match them up with our shop analytics after every launch. That manual cross-referencing eats up time I’d rather spend prepping for our next collection drop or cleaning up inventory spreadsheets.

I’ve also noticed limitations around SMS compliance workflows, which matters a lot for a fashion brand running regular promotional texts. We have to stay careful with opt-out tracking and disclosure language. OneSignal handles the basic STOP replies fine, but it lacks built-in tools to audit our SMS list health at a glance. I can’t quickly pull a report showing how many contacts haven’t engaged with our texts over the last 90 days, so I have to run separate exports to prune inactive subscribers. If I let stale numbers sit in the list, we risk hurting our deliverability and running afoul of messaging rules. It’s doable, but it adds another manual task to my plate. Review collected by and hosted on G2.com.

What I like best about OneSignal is how it lets me set up segmented push and SMS alerts for our B2B electronics buyers, and I can tag each client with their part number interests, allocated order status and preferred alert types all in one dashboard. Before we started using it, I was manually sending stock updates and lead time changes through separate emails and group texts, and I learned the hard way with our supplier Pacific Component Supply. They notified us that a batch of wireless controller chips would be delayed six weeks, and I only put that delay note in our shared spreadsheet. I was sending out a mass stock alert and forgot to exclude the buyers who had pre-ordered that exact chip. One of our biggest retail clients got the “in stock” notification, committed to a downstream sale, and then we had to call them to break the bad news. That cost us a small reorder and a lot of trust. After that mess, I knew I needed a tool that can filter audiences automatically before any alert goes out.

I really rely on the custom tags and journey automation features. I can tag every buyer by their SKU interests, pricing tier, and whether they only want critical delay alerts, not routine stock updates. When we get supply updates from vendors like Pacific Component Supply, I just update the tag on the affected product, and OneSignal keeps that segment separated. I also love the A/B testing and delivery scheduling; I can send alerts at times that work for our west coast and east coast buyers separately, instead of blasting everyone at once. A couple months ago, a buyer told us they didn’t want to get pings for anything except shipment release notices for their bulk HDMI cable order. I set their tag and built a simple journey rule, so they only get triggered alerts when their goods are ready. That would’ve been impossible to manage reliably when I was doing everything manually.

CSV bulk uploads also save me hours every time we onboard new reseller clients. I import their account details, tag their preferred product lines, and they are ready to receive relevant alerts right away. Every sent notification, click and reply stays attached to their subscriber profile. If our sales rep is out visiting clients and I have to cover their accounts, I can quickly pull up their alert history and see what messages they’ve received, no long phone calls to chase context. We’re just a small wholesale electronics shop, we don’t have a dedicated dev team to build custom notification tools. OneSignal is straightforward enough for me to manage without constant engineering support. It’s not perfect, I still double-check every segment before sending urgent supply alerts, but it stops those careless mix-ups where the wrong client gets the wrong update. It keeps our communications with resellers precise and helps us avoid the costly missteps we ran into before. Review collected by and hosted on G2.com.

Honestly, OneSignal works great for our stock and shipment alerts for electronics resellers, but there are some frustrating limitations that have burned me before, and the trouble with Pacific Component Supply is still fresh in my mind. I was doing a bulk CSV update to adjust subscriber tags, marking all buyers waiting on those delayed wireless controller chips so they would be suppressed from in-stock alerts. I mapped all the columns correctly, uploaded the file, but OneSignal didn’t properly overwrite the old tags for that group. The alert still went out, and one of our retail resellers got the wrong stock notice again. I thought I had locked that segment down, and I ended up spending the whole afternoon calling customers to apologize and reset expectations. Now I only update small batches of subscribers at a time, and I manually spot check every single suppressed account, which eats up a ton of my week.

I also find the alert rule logic pretty rigid for our supply chain workflows. We often have partial shipments from our vendors. For example, when we received a partial delivery of USB power modules from Zenith Electronics Parts last month, I tried to set up a rule that only alerts buyers whose order quantity matched the newly received stock. OneSignal’s filtering can’t split a single SKU’s subscriber list by the quantity they ordered. I had to manually split the list into two separate CSV files, one for customers getting partial fulfillment and another for those still waiting. It took me hours, and I almost mixed up the two lists before I sent anything out. I wish there was a way to build more nuanced conditional triggers around order quantity and partial shipments.

The notification preview is another weak spot. I can see how the message looks on mobile, but there’s no quick way to test it against a specific subscriber tag. I once drafted a delay alert for buyers waiting on parts from Zenith Electronics Parts, and I accidentally left in a placeholder for the revised ship date. I didn’t catch it until a buyer replied confused, asking what the new timeline was. There’s no sandbox test group that inherits the exact same tag rules as our real customers, so testing feels risky. Review collected by and hosted on G2.com.

The overall reliablility 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. Review collected by and hosted on G2.com.

Exporting our user data in bulk can take a surprisingly long time to process. Review collected by and hosted on G2.com.

What I like most about OneSignal is how reliable and straightforward it is. The integration process is well documented, and once everything is set up, it works consistently without requiring much maintenance.

I also like that it provides a good set of features without making the platform feel overly complicated. For our use case, especially push notifications, it has been easy to manage and dependable. Review collected by and hosted on G2.com.

There isn't much I strongly dislike. The main downside is that some of the more advanced features can take a little time to understand, and the dashboard can feel a bit overwhelming at first because there are so many options.

That said, once you get familiar with the platform, it becomes much easier to use. Review collected by and hosted on G2.com.

The automated workflows ensure that no user is ever left unengaged for too long. It is super crucial to keep people well informed about all promotions, announcements or any other piece of information we have to share with them in the given time. Review collected by and hosted on G2.com.

Customer service relies a little bit too heavily on chat bots before you can reach a human. But once you get in touch with real human agents, it is quite very easy to explain what is the problem and to receive all necessary help to solve it. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

The in-app messaging feature feels slightly less polished than the push notification side. This might be a nice thing to consider upgrading. Review collected by and hosted on G2.com.

OneSignal is excellent at managing all aspects of our APNS and FCM communications. Having used it for over four years, we’ve never experienced an outage or fault. Setting up and managing the push notification system has always been effortless, and searching for messages, subscriptions, or user groups is straightforward. In-app messaging has been invaluable for both our day-to-day and emergency communications; we’ve come to rely on it so much that we’re currently expanding how we use it. The setup tools make creating dialogs so simple that anyone on our team can do it. Review collected by and hosted on G2.com.

Very little to dislike. Sometimes I need to set up a segment of 1 subscription to get a message to an individual which is a bit of a pain - it's not a problem though, this is about the worst thing I can think of Review collected by and hosted on G2.com.

The ability to include action buttons directly inside the push notifications makes OneSignal so effective and user-friendly. Review collected by and hosted on G2.com.

Adding custom sounds to notifications is difficult, much more than it needs to be. But it is really not a big deal, not some big thing or flaw to be seriously considered as a disadvantage. Review collected by and hosted on G2.com.

I really enjoy the seamless experience the OneSignal Platform provides. The recent time-scheduling upgrade has made it even more convenient to plan and manage notifications efficiently. I also appreciate how quickly notifications are delivered to users once they’re sent. Overall, it’s a reliable and easy-to-use platform that makes communication much smoother. Review collected by and hosted on G2.com.

One issue is the slow initial load time on mobile when opening the app. Might call it cold start. Don't know if I'm the only one experiencing that, but OneSignal is seamless on desktop/laptop compared to mobile app. Review collected by and hosted on G2.com.