OneSignal

Name: OneSignal
Brand: OneSignal

The leading customer engagement platform, helping 1 in 4 app publishers send 1.3T messages a year.

Est 2011|Valuation $266M|Raised $84.3M|25 Ref Customers

LinkedIn 12K|Web traffic 1.0M|FTEs 173|HQ San Mateo, California, US

MarketsMobile App Engagement Customer Engagement Platforms (CEP)

Published Nov 8, 2026

01Common complaints

- Support is mission-critical but available budgets or contract commitments do not include higher-tier support: public complaint data suggests support responsiveness is tier-dependent. - The organization is highly sensitive to billing or cancellation risk: multiple public complaints allege billing after cancellation and sudden cost increases; procurement should validate billing mechanics and contract terms during a pilot. - The organization requires strong, publicly available enterprise security controls without gating documentation behind Enterprise contracts: SOC 2 and ISO certifications are documented, but detailed evidence is often provided only upon request. - The organization requires advanced email marketing and deliverability consulting out of the box: e-commerce-focused platforms (e.g., Klaviyo) often provide deeper email/SMS marketing ecosystems. - The organization requires a full enterprise engagement suite with deep experimentation and orchestration: enterprise vendors such as Braze or Airship may better match those needs despite higher cost and complexity.

Deal disqualifiers (poor fit)

Requirement for guaranteed, high-touch support while remaining on a low-cost tier
Strict compliance or data residency needs that cannot be met with the vendor’s publicly documented offerings
Requirement for an integrated enterprise-grade CDP with advanced experimentation and personalization (scenarios where Braze, Iterable, or an enterprise CDP may be more suitable)

Reliability / downtime incidents

The vendor public status page documents incidents affecting dashboard and API availability, including full and partial outages in 2025. These incidents are consistent with typical SaaS operational risks and should be evaluated relative to required SLAs.

SDK / integration issues (examples)

Public issue trackers contain bug reports and community questions related to SDKs (for example, framework-specific notification handling). These reports suggest that testing across targeted client platforms is required to identify edge cases before production rollout.

Plan limitations

Free plan limitations include constraints on web push sends and in-app concurrency; Growth introduces per-unit charges that can increase costs with scale.

Security disclosure limitations

SOC 2 and ISO certifications are documented, but detailed reports and certificates are often shared on request and may be gated to Enterprise discussions. This can lengthen security review cycles.

02Why they buy

Note: this section has been rephrased to present differentiators in neutral terms.

Differentiators supported by evidence

- Low initial barrier to adoption: a free plan and public reviews frequently reference straightforward setup and quick onboarding for common use cases. - Push-first heritage with omnichannel expansion: OneSignal is widely used for push notifications and has expanded to include email, SMS, in-app messaging, and workflow automation. - Workflow automation available at lower tiers: OneSignal’s Journeys functionality is available across tiers according to vendor documentation; exact feature access should be validated in product or contract.

Areas where competitors may have an advantage

Enterprise-grade capabilities and high-touch support tend to be stronger with vendors such as Airship or Braze.
Email and SMS marketing depth for e-commerce use cases is often more developed in providers such as Klaviyo.
Advanced event-driven lifecycle messaging and engineering-focused data models are strengths for platforms such as Customer.io.

03Field reports

This section includes content from curated B2B review platforms (which tend to be more positive) and open-web complaints (which tend to be more negative). The populations on these platforms can differ materially.

Review-platform sentiment (generally positive on product review sites)

G2: - Positive themes include perceived ease of use/setup, notification features, and integration simplicity. - Example positive quote (G2): - "The setup is straightforward… and the dashboard is clean and intuitive. Sending push notifications is quick, reliable…" - Example mixed/critical quote (G2): - "It requires a learning curve…" (indicates onboarding complexity for some users). Capterra: - Example feedback: some users note the convenience of having push notifications, emails, and SMS managed together. - Common negatives include limitations on the free tier, API issues, and complications with subscriber acquisition pop-up configuration. TrustRadius: - Pros mentioned by reviewers include fast operation and relative ease of setup and broad platform support. - Cons include pricing concerns and privacy cautions; some reviewers describe platform-level privacy trade-offs for SaaS.

Open-web complaints (notably focused on billing/support themes)

Trustpilot and similar sites show a mix of long-term satisfactory experiences on the free plan and more negative reports focused on billing and support.

Interpretation: consumer-facing complaint sites can skew toward particularly negative experiences; nonetheless, repeated billing and support complaints on public forums are risk indicators that merit validation during procurement.

Reasons cited by customers for adopting OneSignal (from reviews)

Rapid implementation and developer-oriented setup referenced by reviewers
Reliable push notification delivery and cross-platform support
Unified dashboard for multiple channels (push/email/SMS/in-app)
Automation and workflow features (Journeys) used for lifecycle messaging

Reasons cited for leaving or churn indicators (from complaints)

Support gaps, particularly for smaller or non-enterprise customers
Billing disputes and frustration with cancellation or unexpected charges
Pricing model changes that led to cost increases
SDK or API reliability issues in some technology stacks

Vendor-published outcomes (useful but not independently validated)

Vendor materials highlight large-scale usage and reliability claims. These vendor-published outcomes are not independently verified within the sources reviewed; procurement teams should request references and measurement methodologies for claims that will influence decisions.

Operational reliability evidence (incident transparency)

OneSignal maintains a public status page with incident writeups, which is a transparency signal for operational issues. Examples documented in vendor status history include dashboard outages and partial API impacts. Critical view: The incident history demonstrates that outages have occurred, including incidents that were related to dependencies. Buyers with mission-critical notification requirements should validate SLA terms, failure modes, and escalation procedures with the vendor.

Missing: independent, quantified customer case studies

In the sources reviewed for this report, detailed third-party case studies with independently audited ROI or impact metrics were not identified. Buyers should request customer references in relevant industries and ask for measurable outcomes (CTR uplift, retention impact, opt-in growth) with clear measurement methodologies.

04Best fit

Company size

Based on price structure and review patterns:

Most suitable: startups through mid-market (small to mid-sized organizations) operating apps or sites where push or lifecycle messaging is important.
Larger organizations can be suitable if they acquire Professional or Enterprise plans to obtain required support, legal, and SLA terms.

Industries / verticals

Typical fits include mobile applications (consumer apps, marketplaces, on-demand services), media and publishing (frequent updates), and some e-commerce use cases where push complements email/SMS. Dedicated e-commerce ESPs may still be preferable for advanced email marketing use cases.

Roles and personas

Decision makers: Head of Growth, VP Product, Head of Marketing Operations, Engineering Lead
Primary users: lifecycle marketers, CRM managers, mobile developers

Qualification criteria (suitable fit)

Organizations seeking push notifications combined with basic-to-advanced automation without a large enterprise rollout
Need for multi-channel messaging (push/email/SMS/in-app) delivered from one tool with APIs
Acceptance of consumption-based pricing (MAU/subscriber billing) and capacity to model expected costs

05The pitch

What the product does (objective value proposition)

OneSignal is a SaaS customer engagement and messaging platform that enables organizations to send and orchestrate messages across mobile push, web push, in-app messaging, email, SMS/RCS, and (for iOS) Live Activities from a unified dashboard and APIs. The product is positioned as an omnichannel customer engagement platform with workflow automation (Journeys), segmentation, personalization, and analytics. OneSignal’s historical strength and core adoption driver remains push notifications (mobile and web), with broader cross-channel capabilities added over time.

Target market and market positioning

- Primary buyers/users: product teams, growth/marketing teams, and developers who need push and lifecycle messaging without building a full messaging stack. - Positioning: oriented toward developer-friendly implementation and relatively rapid deployment, competing in a range that includes low-cost push providers and enterprise customer engagement suites. - Observed typical customer segment (from reviews): small-to-mid businesses and application teams seeking reliable push capabilities and basic-to-moderate orchestration without enterprise-level complexity.

Get a comprehensive analysis of OneSignal including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →