Subscriber journey

A viewer sees a trailer on a phone, taps through to a web landing page, subscribes there, and signs in on a living-room TV two days later. That is one subscriber journey and three surfaces, and at most companies each surface was built by a different team on a different schedule. The journey runs from first impression through first payment and keeps running after it.

No single system holds the whole thing. The ad platform sees the click and stops there. The store reports a purchase with no idea what preceded it. Product analytics counts sessions but not the reason someone subscribed. The subscriber experiences one continuous thing while the teams responsible for it each watch a different slice, which is how a landing page comes to promise one price and a paywall three taps later shows another.

Treating it as a journey rather than a pile of screens is what makes it testable. A path can branch on what the subscriber already said, carry an answer from an onboarding question into the offer shown three steps later, and be measured end to end instead of screen by screen. That is the work of Flows, and it is where the experience layer stops being an idea and becomes something a team can ship. The web-to-app version of this path, where acquisition happens on the web and delivery happens in the app, carries its own set of problems; web2app funnels covers those.