OneSignal for Streaming Services

Why Lifecycle Messaging Matters More in Streaming Than Almost Any Other Subscription Business

Streaming platforms face a specific retention problem: subscribers churn silently. No angry email, no cancellation survey response, no call to customer support. They just stop watching, let the billing date pass, and leave. By the time you see the churn in your numbers, the window to intervene closed weeks ago.

OneSignal gives you the infrastructure to act earlier — before disengagement becomes cancellation. But the platform is only as useful as the strategy behind it. This guide covers exactly how streaming teams should configure OneSignal to reduce passive churn, re-engage dormant subscribers, and build the kind of behavioral segmentation that actually moves retention metrics.

---

Setting Up OneSignal for a Streaming Platform

Data Architecture First

Before you send a single notification, connect your data correctly. OneSignal's value in streaming comes from behavioral triggers, not broadcast campaigns. That means your event data needs to flow in cleanly.

Connect OneSignal to your data warehouse or CDP using the Data Tags system. At minimum, you need these attributes on every subscriber profile:

• `last_watched_date` — timestamp of the most recent viewing session
• `content_genre_preference` — top 1-3 genres by watch time
• `subscription_tier` — free, standard, or premium
• `billing_renewal_date` — the next charge date
• `titles_completed` — count of series or films finished
• `days_since_signup` — calculated from account creation

These tags power every segment and automation you'll build. Without them, you're sending generic push notifications. With them, you're responding to behavior.

SDK Configuration

Implement the OneSignal SDK on all platforms your subscribers use — iOS, Android, and web. For streaming specifically, push permission opt-in rates vary significantly by surface. Web browser notifications convert at roughly 5-10%, while mobile app opt-ins can reach 50-70% with a well-timed in-app prompt.

Trigger your permission request after a subscriber completes their first full episode, not at account creation. That single timing change typically lifts opt-in rates by 15-25% because the user has already experienced value.

---

Key Events to Track

These are the events that matter specifically for streaming retention. Set these up as Custom Events in OneSignal and pipe them in from your analytics layer.

• `content_played` — any start event, with content ID, genre, and series name as properties
• `content_completed` — full watch (>85% of runtime)
• `series_finished` — subscriber completed the final available episode of a series
• `search_no_results` — subscriber searched for content you don't carry
• `payment_failed` — billing event that precedes involuntary churn
• `account_paused` — subscriber self-initiated a pause
• `plan_downgraded` — moved from premium to standard or standard to free

The `series_finished` event is one of the highest-leverage triggers in streaming. A subscriber who just finished a series has no obvious next destination. If you don't recommend something within 24-48 hours, you lose momentum. Competitors gain it.

---

Segments to Build

Engagement-Based Segments

Segment your subscriber base by recency and frequency, not just subscription status. Build these as dynamic segments in OneSignal that update automatically as tag values change:

• Active — watched in the last 7 days
• Cooling — last watch 8-21 days ago
• At-Risk — last watch 22-45 days ago
• Dormant — last watch 46+ days ago, still subscribed

Your messaging strategy should differ materially across these four groups. Sending a "What to watch next" recommendation to a Dormant subscriber is less effective than sending a re-engagement message that acknowledges the gap.

Content Affinity Segments

Build segments around `content_genre_preference` to personalize new release notifications. A subscriber who watches 80% crime drama should never receive a push notification about a new romantic comedy debut unless there's a specific crossover reason.

Billing Risk Segments

Create a segment for subscribers whose `billing_renewal_date` is within 7 days AND who fall into the At-Risk or Dormant categories. This is your pre-churn window — the best time to push a piece of content that might remind them why they subscribed.

---

Automations to Build

The Engagement Loop (Active Subscribers)

Set up a weekly personalized recommendation using a Journey in OneSignal. Trigger it every Sunday evening — historically the highest streaming start time across most platforms. Pull in the subscriber's top genre tag and populate the message dynamically.

Example message structure: "Three new [genre] titles added this week — [Title 1] is getting the most attention right now."

The Series Completion Sequence

When `series_finished` fires, trigger a two-step sequence:

1. Within 2 hours: Send a "You finished [series name]" message with one high-confidence recommendation based on genre and viewing history
2. 72 hours later (if no new watch session): Send a second recommendation framed around the same tone or theme as the completed series

This sequence alone can reduce post-series churn by measurable percentages because it closes the "what now" gap immediately.

The Re-Engagement Campaign

For Dormant subscribers, run a 3-message sequence spaced 5 days apart:

1. Message 1: Highlight the single most-watched title in their preferred genre this month — social proof framing
2. Message 2: Surface something specific they started but didn't finish (use `content_played` without a corresponding `content_completed`)
3. Message 3: If still no session, and renewal is approaching, include a pause or plan downgrade option — giving them control often retains them longer than a hard promotional push

Payment Recovery

When `payment_failed` fires, send an immediate push notification directing the subscriber to update their billing. Follow up at 24 hours and 72 hours if unresolved. Involuntary churn from payment failures accounts for 20-40% of total churn for many subscription businesses — this automation pays for itself quickly.

---

Industry-Specific Challenges with OneSignal

Content catalog size creates notification fatigue. Streaming platforms with large catalogs often over-notify because there's always something new to promote. Set a frequency cap of no more than 3-4 push notifications per week for active subscribers. Dormant subscribers should receive even fewer — 1-2 attempts per week maximum.

Cross-device attribution is messy. A subscriber might watch on their TV app but receive notifications on mobile. Their `last_watched_date` may update correctly, but notification opens will come from a different device. Use OneSignal's External User ID to tie all a subscriber's devices to one profile. Without this, your segmentation will show false dormancy for subscribers who are actually active on other devices.

Free tier subscribers require different messaging. If your platform has a free or ad-supported tier, do not send the same content recommendation messages to free users as you do to paying subscribers. Free users are conversion targets first. Build a separate automation focused on surfacing premium-only content as a conversion prompt, triggered after a free user completes 3 or more pieces of content.

---

Frequently Asked Questions

How many push notifications should a streaming service send per week?

For active subscribers, 3-4 per week is a reasonable ceiling. Beyond that, opt-out rates increase meaningfully. For at-risk and dormant subscribers, reduce to 1-2 per week and focus exclusively on high-relevance content. Volume without relevance accelerates disengagement.

Can OneSignal handle personalization at scale for a large content catalog?

Yes, but it requires clean tag data. OneSignal itself does not make content recommendations — your recommendation engine or data layer supplies the content ID and title, and OneSignal delivers the message. Build the personalization logic in your warehouse or CDP, pass the output as tags to OneSignal, and use those tags in message templates with dynamic substitution.

What is the most important segment to build first?

Start with the pre-churn billing risk segment — subscribers who are 22+ days inactive with a renewal date within 7 days. This group has the highest near-term churn probability and the most concrete intervention window. Even a modest 10% recovery rate on this segment has direct revenue impact.

How should streaming platforms handle subscribers who opt out of push notifications?

Opt-out is not loss of reach — it is redirection. Subscribers who decline push should automatically be enrolled in email sequences using whatever email platform you operate. OneSignal integrates with most major ESPs. Build a parallel email journey that mirrors your push logic so no segment of your subscriber base falls into a communication void.