Why us Easy integration
Developers
Talk to sales
Industries · Streaming

Keep subscribers through the gap between releases

A subscriber watches six episodes in a weekend, then nothing for eleven weeks. The release week looks after itself. We turn completed episodes, titles started and watchlist adds into missions that work in the quiet weeks, which is where the cancellation actually happens.

The shape of a streaming year

Subscribers binge for two weeks, then watch nothing for months

Release weeks produce most of your viewing and almost none of your risk. The gap weeks produce almost no viewing and all of your cancellations, so that is where the campaign has to work.

The release is the unit

Week is the honest recurrence here. A per-player reset gives somebody who joins on a Thursday a full seven days, not the four that were left.

Churn is decided in the gap

The peak produces most of your events and almost none of your risk. So the useful rules look back over a window, such as episodes_completed over 21 days.

one subscriber · one season and the gap after it
Sixteen weeks of one subscriber. Sixteen bars, one per week. A season lands and viewing peaks for two weeks, then declines across its run, then falls to nothing for six weeks, then returns sharply when the next season drops. A band over the six empty weeks marks the window a win-back mission runs in, which is where a cancellation actually happens. minutes watched that week the weeks a win-back mission runs wk 1 wk 8 wk 15 Cancellations happen in the quiet weeks, not at release.

Reading the chart: each bar is one week of viewing. A season lands, the first two weeks peak, viewing declines, then falls to nothing for six weeks before the next season. The release weeks carry the viewing and none of the risk. The band covers the empty weeks, where a subscriber decides to cancel.

The rule you would build

The win-back mission runs in the weeks between releases

You build this yourself in the dashboard. It targets the weeks when a subscriber has stopped watching but has not yet decided to cancel, which is the only window where anything you do still changes the outcome.

how this is set up
Match all of the 3 rules below
Count of episodes finished = 0 rolling 21 days
Sum of watchlist adds 1 all time
Attribute plan tier cancelled
Then: eligible for Finish what you started · two episodes from anything saved · award 600 points
KeyKindWhat it carries
episodes finished Metric · Number An episode or film watched past your completion threshold.
titles started Metric · Number A first play of something new. Your breadth signal.
watchlist adds Metric · Number Something saved for later. Still arrives during a gap.
genre Property · String The shelf. Turns a new commission into a mission today.
plan tier Attribute · String Read directly by eligibility rules.
What we will not reward

We reward what a subscriber finished, never hours left running

Paying points for hours watched is gamed in an afternoon by leaving a tablet playing to an empty room. Every objective here is either met or not met, so there is no meter anybody can run up.

  • No personal data. A record holds your own identifier, a time zone and timestamps. No name, no email, no payment method.
  • No database access. Events arrive over the API. We hold no catalogue and no viewing history.
  • One setup, then unlimited campaigns. Declare your keys once, then publish as many missions as you like.
  • You own the rules. Every threshold, filter and window is yours to edit.
  • Sandbox before Live. Rehearse the whole programme before a subscriber sees it.

Send us one finished-episode event

Send us the event your player sends when an episode finishes. We will build the win-back mission in a test account while you watch.