Push should feel like product, not a megaphone (Klaviyo, ex-Strava playbook)
A credited summary of Klaviyo’s practical push-notification playbook from a former Strava martech lead. The core idea: push works when it is tied to user moments, deep links, and a conservative frequency ramp, not when it copies email calendars.
Original article (source): Klaviyo - “Push Notification Marketing: Confessions of a Strava Alum” (Aug 7, 2026)
Summary
This is not an “App Store” post, but it is a useful reminder for growth teams: push wins when it behaves like a product surface, not like another blast channel.
The author’s Strava example is the right mental model. Notifications were part of the core loop (finish a run, get a notification; get kudos, get a notification). In a lot of retail/B2C apps, push is treated as an afterthought or a copy-paste of the email calendar, which trains users to mute you.
1) Why push is worth the effort (if you do it properly)
Klaviyo’s argument is mostly channel mechanics:
- users who opt into push have already raised their hand
- it lands on lock screen (high salience)
- incremental send cost is near-zero vs SMS/WhatsApp
Even if you disagree with the “free” framing (there is still opportunity cost and trust cost), the constraint is real: you only get a small amount of text, so every message needs a job.
2) Audience growth is its own system
They emphasise that “push strategy” starts upstream.
Practical acquisition levers they call out:
- make app download part of welcome/onboarding sequences
- give users a reason (exclusive drops, app-only discounts, early access)
- promote app install on-site and on social
3) Tactics that map cleanly to app growth
The six message types they list are familiar, but the implementation detail that matters is deep linking.
- time-sensitive alerts (flash sales, back-in-stock, price drops)
- behavior nudges (viewed, cart, wishlist, search intent)
- welcome messages
- loyalty and birthday updates
- location-based messages (where relevant)
- win-backs (low-risk reactivation test)
The growth lesson: if the tap lands users on a generic home screen, you burn your best moment. Deep link to the exact item, cart, or state.
4) Frequency: ramp slowly or you churn opt-ins
Their guidance is conservative: start new subscribers at ~1 to 2 pushes per week and then segment by engagement.
That aligns with what most teams learn the hard way: early spam is how you kill push as a channel for months.
What to do next (tiny wins)
- Write a “push promise”: one sentence that defines what your notifications are for (and what they are not). Make every message pass that test.
- Fix deep links first: pick your three highest-intent pushes (cart abandon, back-in-stock, delivery updates) and make the landing state perfect.
- Add an opt-out early warning: track opt-out rate per campaign. If it spikes, treat it as a UX regression, not just “creative fatigue”.
Read the source: https://www.klaviyo.com/blog/push-notification-marketing-strategy
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.