OneSignal

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

To put it plainly, OneSignal clears up a major bottleneck we were hitting with customer outreach at Coastal Thread Apparel, where I work as E-Commerce & Operations Manager based out of LA. Our team is small, only 11–50 people, and we don’t have a dedicated marketing engineer on staff full time. Before we adopted OneSignal, coordinating timely customer alerts across different channels was messy and slow. Our developer was always swamped with store fixes, inventory sync issues, and prepping our site for new apparel drops. Any time I wanted to send push, SMS, or in-app alerts for restocks, limited-edition launches, or abandoned cart reminders, I had to submit a dev request and wait days to get it live. That lag killed a lot of momentum around time-sensitive promotions, and we were forced to rely mostly on email, which just doesn’t grab shoppers the same way an immediate notification does.

That’s the core problem OneSignal solves. Its setup is developer-friendly to implement, but once it’s connected, the marketing dashboard is intuitive enough that I can build, segment, schedule, and launch campaigns without pulling our dev away from critical site work. The multi-channel support is huge for our apparel brand because we speak to different customer groups in different ways. Web push works great for people browsing our site, SMS resonates best with our most loyal repeat shoppers, and email lets us share longer brand stories and fabric details. All of these channels live under one roof, and we can reuse the same customer segments across every message type.

I saw this pay off really clearly during our linen collection restock a couple months back. A bunch of our customers had signed up to get notified when their sold-out sizes came back. In the old setup, I would’ve had to maintain separate lists for push subscribers and SMS subscribers, coordinate separate tools, and bug our dev to trigger each alert. With OneSignal, I built one core segment of customers waiting on linen restocks, then sent out tiered notifications: early access push alerts first for our top repeat buyers, then an SMS reminder an hour later for everyone else on the waitlist. The whole campaign was built and scheduled by me, no dev support needed, and the notifications drove a solid spike in sales within the first few hours of the restock going live.

The webhook and open API functionality solves another pain point for us: automating event-based messages. We hook it up to our store so key shopper actions feed straight into OneSignal. That lets us run automated abandoned cart nudges and post-purchase nurture messages without building a bunch of custom scripts from scratch. When someone leaves a linen tee sitting in their cart, the system triggers a gentle reminder. When a customer completes an order, they get a follow-up message with care instructions for their garment. These automated touches keep our audience engaged without me manually firing off messages every single day.

Now, it’s not perfect. I already mentioned the clunky advanced segmentation, limited revenue-focused reporting, and extra work needed to maintain SMS compliance. But those downsides don’t overshadow the main benefit. OneSignal lets our lean fashion team move fast around drops and restocks. It removes the engineering bottleneck from our customer engagement workflow, unifies our messaging channels, and makes personalized, timely alerts accessible to someone like me who’s already juggling store operations, launch planning, and SaaS tool testing. At the end of the day, that means we can capture more sales from excited shoppers and build better habits with our audience, without stretching our tiny team too thin.

What do you like best about the product?

The send of notifications, when a new article is published

What do you dislike about the product?

Geolocation restrictions, I want word will

What problems is the product solving and how is that benefiting you?

Interaction send notification

What do you like best about the product?

I use OneSignal for app notifications, and it engages my users and helps with live updates. I like the easy-to-use API integration and push notifications. The initial setup was very easy, and I’m impressed with the way it works.

What do you dislike about the product?

None

What problems is the product solving and how is that benefiting you?

I use OneSignal notifications in my app to engage my users and provide live updates.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

OneSignal keeps our platform top-of-mind for our audience without requiring daily manual input from our staff. That simply saves our time, and time is the most valuable to all of us, no doubt.

What do you like best about the product?

The push notifications and the other features.

What do you dislike about the product?

Nothing! It is absolutely great to use!!

What problems is the product solving and how is that benefiting you?

The push notifications. They are really good.