# Create useful reasons to return

- **Canonical URL:** https://playbook.affpartners.io/en/practices/retention-content/index.html
- **Markdown version:** https://playbook.affpartners.io/en/practices/retention-content/index.md
- **Module:** Retention
- **Time:** 90 minutes for the first calendar

Content drives retention when it connects to a user's interest or action—not simply because more items are published. Decide who needs a reason to return and why before choosing the channel.

## Outcome

A one-week calendar of five return moments with audience, value, destination screen, frequency limit, and action metric.

## A reason is a useful change for a specific user

A new article is not, by itself, a reason to message everyone. A reason appears when the material matches a saved interest, helps continue a journey, or explains a real change. The user should understand the benefit before opening the message.

## What you will need

- **Interest signal:** A save, a subscription, a topic view, an unfinished lesson, or another confirmed sign of user interest.
- **Content owner:** An editor, communications specialist, or product manager who checks accuracy, freshness, and the destination screen.
- **Frequency rules:** A shared message limit and exclusions for recently active users or those who already got a similar reason.

## Terms in plain language

- **Retention — The share of users who return:** Definition: Shows how many people reopen the app after a set period from installation or registration. Example: If 18 of 100 new users return after seven days, D7 retention is 18%.
- **Segment — Users sharing a behavior or characteristic:** Definition: A segment groups people by platform, market, interest, or action so the team does not send the same message to everyone. Example: Android users who started but did not complete registration in the past 24 hours.
- **Analytics event — A record of a specific user action:** Definition: The app sends an event when a user opens a screen, taps a button, or completes an action. Example: registration_started and registration_completed reveal how many people abandon registration.
- **Deep link — A link to a specific app screen:** Definition: After a tap, the user lands in the promised journey rather than on the home screen. Example: A push about a saved lesson opens that lesson directly.
- **CTA — The main action offered to the user:** Definition: A CTA is a button or link with a clear next step and expected outcome. Example: “Continue registration” is clearer than “Next”.

## When to use it

The app sends generic reminders, content is planned separately from user behavior, and there are opens — but useful actions after them do not grow.

## Where to find useful reasons

Do not start from the holiday calendar. Look for the link between a real change, a user's interest, and an available action in the product.

- **Saves and views**
  - **Source:** See which topics, items, or lessons people save, reread, and finish.
  - **If access is unavailable:** Without events, use search queries, the most visited pages, and a manual list of common interests.
- **Support and search**
  - **Source:** Collect recurring questions and searches with no results — they show which explanation or material is missing.
  - **If access is unavailable:** Once a week, note the five most frequent support questions in a shared table.
- **Product changes**
  - **Source:** Add an updated status, new material, or a feature only if it is relevant to the chosen segment right now.
  - **If access is unavailable:** If personalization is not available, publish the reason in the right section instead of a mass notification.

## Build a calendar of useful return reasons

1. **Collect real changes.** Write down the statuses, new materials, updates, and unfinished actions that will actually be available next week.
   - **Where to do it:** In the first column of the calendar, with the relevance date.
   - **Example:** A new analysis appeared in a saved topic; a lesson got a follow-up; an application status changed.
2. **Tie the reason to an interest.** Name the confirmed action that puts a user in the audience. Do not stretch the “all users” segment.
   - **Where to do it:** In the message's audience condition.
   - **Example:** Saved the topic or read it twice in 30 days, but has not seen the new material yet.
3. **State one benefit.** Say what the user can learn, continue, compare, or check. The benefit must be clear before the open.
   - **Where to do it:** In the title and the first line of the message.
   - **Example:** “A new analysis appeared in your saved collection” instead of “Don't miss our updates.”
4. **Prepare an exact route.** After the tap, open the material, the saved step, or the right collection. The home screen destroys the context of the reason.
   - **Where to do it:** In the deep link and a test account.
   - **Example:** The message about the analysis opens that analysis inside the saved topic.
5. **Cap competing messages.** Set the frequency and priorities. One user should not get three messages from different teams in one evening.
   - **Where to do it:** In the communications system and the last column of the calendar.
   - **Example:** At most two useful messages a week; service statuses outrank content collections.

## Practical examples

- **A saved topic update:** The message goes only to those who read or saved the topic within 30 days. It names the new analysis and opens it inside the personal collection — once per event.
- **A weekly digest without overload:** The digest bundles changes only around the user's confirmed interests and skips those who already saw the materials. The shared cap is two useful messages a week.

## Finished artifact: A one-week calendar of return reasons

Each row answers five questions: who it is for, what changed, what the benefit is, where it leads, and how the frequency is capped.

| Reason and audience | Benefit | Destination | Limit |
| --- | --- | --- | --- |
| A saved topic updated | See the new analysis | Deep link to the collection | Once per event |
| Unfinished lesson | Continue from step 3 | Saved progress | After 48 hours |
| Answer to a frequent question | Understand the condition before acting | Help article | Interested users only |
| Weekly digest | Collect changes by interest | Personal feed | At most once a week |
| New feature | Solve a familiar task faster | Feature screen | Matching segment only |

Before publishing, delete a row if the team cannot name the personal benefit or open the promised screen. Five strong reasons beat twenty generic messages.

## Reason checklist

Remove a reason from the calendar if even one required item cannot be verified before the send.

- [ ] There is a confirmed interest or an unfinished user action.
- [ ] The benefit is clear before the open and actually available in the product.
- [ ] The deep link leads to the promised material or the saved step.
- [ ] Recently active users and those who already saw the content are excluded.
- [ ] A shared frequency cap and one main action metric are set.

## How to know the reason is useful

- **Reached the content:** Users opened exactly the promised material or the saved journey.
- **Completed a useful action:** The material was finished, an item saved, a lesson continued, or a status viewed.
- **Kept the trust:** Notification opt-outs, complaints, and ignored follow-up messages did not grow.

## Key rule

An event becomes a reason only when it is useful to a specific user and leads to a real action.

---

- [HTML version](https://playbook.affpartners.io/en/practices/retention-content/index.html)
- [All practices](https://playbook.affpartners.io/en/)