KPI Tree

Metric Definition

Save and return behaviour

Bookmark usage rate = users who returned to a bookmark / users who created at least one bookmark
users who returnedDistinct users who opened a saved bookmark in the period
users who createdDistinct users who saved at least one bookmark in the period

Track from

Metric GlossaryOperations Metrics

Bookmark usage rate

Bookmark usage rate is the share of active users who save a bookmark and then return to use it within a defined period. It measures whether a save feature is genuinely helping people find their way back to content, or whether bookmarks are created and forgotten. It is a strong signal of perceived value, because people only save what they expect to need again.

6 min read

Generate AI summary

What is bookmark usage rate?

Bookmark usage rate is the share of users who save a bookmark and then return to use it within a defined period, expressed as a percentage. If 400 users saved a bookmark last month and 120 of them later opened one, the bookmark usage rate is 30 percent. The metric separates the act of saving from the act of returning, which is where the real value lives.

It matters because a save is a promise and a return is the payoff. A high creation count with a low return rate means people are saving things they never come back to, which usually points at a discovery problem: the saved items are hard to find again, or the bookmark list itself is hard to navigate. The metric tells you whether the feature closes the loop or just collects clutter.

Definition note

Measure return, not just creation. A rising number of bookmarks created looks like adoption but means nothing if nobody comes back. The honest signal is the share of savers who return and act on what they saved.

How to calculate bookmark usage rate

Count the distinct users who created at least one bookmark in the period. Then count how many of those same users later opened a bookmark. Divide the second number by the first and express it as a percentage. If 250 users saved bookmarks and 90 returned to open one, the bookmark usage rate is 36 percent.

Keep the cohort consistent. The denominator should be the people who saved within the window, and the numerator should be returns by those same people, so the rate reflects whether saving leads to using rather than mixing in unrelated traffic.

  1. 1

    Define the period

    Choose a window such as 30 days that gives users a realistic chance to return to a saved item.

  2. 2

    Count the savers

    Count distinct users who created at least one bookmark in the period. This is the denominator.

  3. 3

    Count the returners

    Count how many of those savers later opened a bookmark. This is the numerator.

  4. 4

    Divide and express as a percentage

    Divide returners by savers and multiply by 100 to get the usage rate.

Bookmark usage rate in a metric tree

A flat usage rate hides whether the problem is at the save step or the return step. A metric tree splits the rate into the journey: how easy it is to save, whether saved items are findable, and whether returning leads to a useful action. Each branch is a different fix, and the tree tells you which one to make.

KPI Tree models this decomposition and ties each branch to an owner through RACI, so a drop in the return rate reaches the product owner accountable for the bookmark experience rather than sitting in an analytics tool. A verified impact loop then checks whether a change to bookmark discovery actually lifted the return rate, closing the gap between shipping a fix and knowing it worked.

Metric tree insight

If saves are high but returns are low, the problem is almost always findability, not interest. People wanted the content enough to save it, then could not get back to it. Fix the path back before adding more reasons to save.

Bookmark usage rate benchmarks

Benchmarks vary widely by product type. A reference tool where users save documentation will see far higher return rates than a feed where bookmarks are a passing intention. Use these ranges as a directional guide and calibrate against your own healthy cohorts.

Usage rate bandShare of savers who returnWhat it signals
Strong40 percent or moreBookmarks are a core part of the workflow and easy to return to
Healthy25 to 40 percentThe feature is working, with room to improve findability
Weak10 to 25 percentPeople save but struggle to come back, usually a discovery gap
Poorunder 10 percentBookmarks are clutter, the return path is broken or hidden

How to improve bookmark usage rate

Lifting the usage rate is mostly about the return half of the loop. Making it trivial to find and reopen saved items beats adding new ways to save. Focus on visibility, organisation, and well-timed nudges back to what people set aside.

Make saved items findable

Put the bookmark list one tap from the main view and add search within it. Saved items that are hard to find are never used.

Nudge people back

A gentle reminder about saved items they have not opened brings the return rate up without forcing more saves.

Let people organise

Folders, tags, or simple grouping turn a long undifferentiated list into something people trust enough to return to.

Keep saved content fresh

Surface when a saved item has been updated. A bookmark that shows new value is far more likely to be reopened.

Common mistakes when tracking bookmark usage rate

  1. 1

    Celebrating saves alone

    A rising count of bookmarks created is not adoption. Without returns it is just a growing pile of forgotten items.

  2. 2

    Mismatched cohorts

    Counting returns from people who saved in a different period inflates the rate. Keep the savers and returners the same cohort.

  3. 3

    Ignoring the relevance decay

    Saved content goes stale. A low return rate can mean the saved items expired, not that the feature failed.

  4. 4

    No window for returning

    Measuring returns the same day a bookmark is created understates the rate. Give a realistic window before you judge it.

Related metrics

Feature adoption rate

Product Metrics
PostHog

Metric Definition

Feature Adoption Rate = (Users Who Used the Feature / Total Active Users) × 100

Feature adoption rate measures the percentage of users who use a specific feature within a given period. It tells product teams whether new features are resonating with users and which existing features are underutilised, guiding investment decisions and roadmap priorities.

View metric

Retention rate

Product Metrics

Metric Definition

Retention Rate = (Users Active at End of Period / Users Active at Start of Period) × 100

Retention rate measures the percentage of users or customers who continue to use your product over a given period. It is the most important growth metric because sustainable growth is impossible when users leave faster than they arrive.

View metric

Daily active users

DAU

Product Metrics
PostHogSlack

Metric Definition

DAU = Unique Users Who Performed a Qualifying Action in a Single Day

Daily active users measures the number of unique users who engage with your product on a given day. It is the primary engagement metric for consumer and SaaS products, indicating whether your product has become a daily habit for its users.

View metric

Net promoter score

NPS

Product Metrics

Metric Definition

NPS = % Promoters - % Detractors

Net Promoter Score measures customer loyalty by asking how likely a customer is to recommend your product or service. It is the most widely used customer experience metric, providing a single number that captures sentiment and predicts growth through word-of-mouth.

View metric

Input metrics vs output metrics

Metric Definition

Bookmark usage rate is an input metric that drives downstream retention, so understanding the difference helps you place it correctly in a metric tree.

View metric

Metric trees for product teams

Metric Definition

Save and return behaviour is a product engagement signal, and this guide shows how product teams structure metrics like it into a tree.

View metric

Build bookmark usage rate as a metric tree

Decompose your usage rate into save behaviour, findability, return triggers, and value on return, then put a named owner on every branch. When the return rate dips, KPI Tree pushes it to the accountable owner and verifies whether the fix actually lifted the number.

Experience That Matters

Built by a team that's been in your shoes

Our team brings deep experience from leading Data, Growth and People teams at some of the fastest growing scaleups in Europe through to IPO and beyond. We've faced the same challenges you're facing now.

Checkout.com
Planet
UK Government
Travelex
BT
Sainsbury's
Goldman Sachs
Dojo
Redpin
Farfetch
Just Eat for Business