GoldenGecko
PlaybooksGuidesFeaturesPricing
  1. Playbooks
  2. /Retention
  3. /Drip-announce features users haven't tried
Common retention pattern

Users don't know about features you shipped months ago

Drip-announce features users haven't tried

Instead of one big announcement, drip-feed feature announcements to individual users based on what they haven't used yet.

RetentionIntermediate
1-2 weeks to build the system, ongoing to add new features

When to use

You have shipped features that users aren't discovering. You can track feature usage per user.

Hypothesis template

If we send targeted in-app messages about [unused features] to users who haven't tried them, feature adoption will increase by [target]% and churn will decrease.

Method

The problem: You ship features every week but most users never discover them. Your changelog goes unread.

What works: Track which features each user has and hasn't used. When they log in, show a subtle notification about one feature they're missing — not a popup, just a gentle nudge.

The result: Targeted feature announcements get 5-10x higher engagement than broadcast announcements because they're relevant to each user.

How to do it:

  1. List all features and track which ones each user has used
  2. For each feature, write a one-sentence benefit: "Did you know? You can X to save Y time"
  3. Show one announcement per session, max — never stack them
  4. Only announce features relevant to the user's use case
  5. Include a one-click way to try it (deep link, not "learn more")
  6. Stop showing after they've tried it or dismissed it 3 times

Key insight: "New feature!" announcements fail because they're broadcast. "You haven't tried X yet, and it could help with Y" works because it's personal.

Success metrics

  • •Feature adoption rate after announcement
  • •Announcement click-through rate
  • •Dismiss rate
  • •Churn rate of users who adopt announced features

Prerequisites

  • Feature usage tracking per user
  • In-app notification system
  • Feature-level analytics

Common pitfalls

  • •Announcing too many features at once
  • •Showing popups instead of subtle nudges
  • •Announcing features irrelevant to the user
  • •Not tracking whether the announcement actually drove adoption

Source: Common retention pattern. Targeted feature announcements outperform broadcast changelogs.

Suggested ICE scores

7Impact
7Confidence
5Ease
retentionfeature-adoptionannouncementsengagement

Ready to run this experiment?

Sign up free to use this playbook with step-by-step guidance and track your results.

More retention playbooks

Users sign up and never come back

Send a 7-day onboarding email sequence

RetentionBeginner

Users try once and never come back

Add a streak counter

RetentionIntermediate

Users have no accountability to keep using

Add friend challenges

RetentionIntermediate

Explore other categories

Acquisition

Get more visitors and sign-ups

Activation

Turn sign-ups into active users

Monetization

Increase revenue per user

Referral

Turn users into advocates

Run experiments like a pro

Get experiment suggestions, track results, and learn what works.

GoldenGecko

Always know what to test next. Proven playbooks, matched to your goals.

Product

  • Features
  • Pricing
  • Playbooks

Resources

  • Guides
  • Common Problems
  • Glossary
  • Comparisons
  • Documentation

Geckoverse

  • Silver Gecko - SEO
  • Local Gecko - local SEO

Company

  • About
  • Privacy
  • Terms

© 2026 GoldenGecko. All rights reserved.

[email protected]