Notifications can manufacture sessions the user never initiated

What it is

A notification does more than deliver information: it manufactures sessions that would not otherwise occur — a single push rewrites "the user decides when to use this" into "the product decides when the user appears." Such externally triggered sessions are what growth teams call re-engagement, and what an attention ledger records as new debits.

Why it happens

Self-initiated use starts from internal states — need, intent, an established rhythm. A notification inserts an external trigger: cue appears, opening follows. After repeated pairing the cue–open link automates, and internal states resembling the cue (boredom, a sound, the unlock gesture itself) begin evoking opens on their own — the external trigger has been internalized as a checking habit, and checking now feeds itself even when notifications are silent. Session-initiation rights transfer accordingly: timing, frequency, and content are all set by product strategy, while the user only ever makes the local choice "respond or not," never the global one "do I want to be initiated at all" — the interface offers no place to answer that question.

Studying it

Notification research combines logs with experience sampling: time-series analysis of notification events against session initiations (how many sessions are directly triggered, how many fall in a delayed window), and compensatory spontaneous use among users who turned notifications off. Independent variables include category, arrival timing, and content specificity. Methodological cautions: the attribution window for a "notification-driven session" drives the number — one minute versus five minutes of latency yields incomparable figures; opt-out experiments carry selection bias, since users who disable notifications were already low-dependence, so effect estimates need correction.

Where it stops holding

Legitimate uses are real: messages from people, safety alerts, and calendar reminders answer the recipient's goals. The claim here is the mechanism — notifications can manufacture sessions and shift initiation to the sender — not a normative verdict; whether a category should exist depends on whether it answers the recipient's goals. The transfer is also a matter of degree: in high-frequency products notifications contribute marginally, while in low-frequency tools a single notification can define nearly every session.

Applying it

Measure the product's session-initiation structure: the directly triggered share, the fully spontaneous share, and residual checking behavior among notification-off users. Before adding a category, answer "would the user come on their own without this notification?" — if yes, the notification is surplus manufacture; if no, then weigh whether its information justifies an interruption. Verification: run a disable experiment on one category and observe how much total use is compensated by spontaneous use — the fuller the compensation, the closer the category is to a pure session manufacturer.

Related

• Same group: P3.06.2 Recall unrelated to user goals is attention taking · P3.06.3 Frequency judged by user value, not retention · P3.06.4 The cost of interruption lands on task resumption · P3.06.5 Badges are content-free recall signals · P3.06.6 Permission granularity determines whether users can refuse in part · P3.06.7 Timing more than frequency decides whether notifications read as harassment
• Adjacent: P3.01 Variable reward · P3.12 Adolescents and attention protection
• Search terms: externally triggered session · push notification · checking habit · re-engagement