Who counts as active
Choose the people a new feature is for, so an adoption check counts the right crowd.
An adoption check asks one question: of the people this feature is for, how many used it? Who counts as active decides the answer as much as the usage does.
In an adoption check, active people are the people a new feature is for. Needlr counts how many of them used it. You decide who they are.
Think of a climbing wall
A school builds a climbing wall in the gym. Does anyone use it? If you count everyone who walks into the school, parents and visitors too, the wall looks unpopular.
Count only the students who came to gym class, and you get the honest answer. Those students are the active people.
When to change it
- The feature is only for some people: signed-in users, paying customers, people who reached a certain page.
- Your site has many visitors who could never use the feature, like blog readers.
- The feature is for everyone who visits. Keep everyone who visits the site.
- A KPI from Google Analytics. GA4 only gives daily totals, not people, so it can't be a condition.
- A KPI that has stopped firing. It isn't offered until it fires again (more).
How to set it
- 1On your project page, press + New impact check and pick Adoption in step 1.
- 2Next to Active people, press Change.
- 3Open Choose what they did… and pick a KPI you already have. Or pick Something new: build it on my site, and build it like a new KPI: a click, a page or a form (how).
- 4Need more? Press + Add a condition (up to 3). Remove one with ✕.
- 5With two or three conditions, choose the options below.
- 6Press Done. The line now says who counts, in words. For example: people who reached /app and clicked “New project”, in the same visit.
Changed your mind? Use everyone who visits the site goes back to counting everyone.
The options
- All or Any: people did every condition, or at least one. Any matches more people. All asks a sharper question.
- When (with All): Any time during the check, or All in the same visit. A visit is one person on one day, by the UTC clock.
- Order (with All): Any order, or In this order (each one after the previous one).
- With Any, the When and Order options don't apply, so they're hidden.
Between the conditions, the editor writes and, or or then, so the list reads like a sentence.
The weekly estimate
When every condition is a KPI you already have, the editor says Matches about so many people a week (last 7 days). It counts people the same way the check will.
Fewer than 30 a week is very few, and the verdict won't be reliable. Fewer conditions, or Any, match more people.
A new condition has no history yet, so there's no estimate. Needlr starts counting it when the check starts.
How Needlr counts them
- A person counts as active from the first day (UTC) they matched. Uses of the feature before that day don't count.
- A person is a browser, or a signed-in user when your site tells Needlr who is signed in.
- With no conditions, everyone who visits is active.
- On the check page, Active people shows how many there are, and who counts, in words.
Common mistakes
- Too many conditions. Each one shrinks the group. Three conditions, in the same visit and in order, can leave almost nobody.
- A condition that is the feature itself. If being active means using the feature, every active person used it, and the share looks perfect.
- The wrong order. In this order means each step after the one before. If people often do them the other way round, they don't count.
Words to know
- Active people
- The people a feature is for: everyone who visits, or people who did certain things.
- Condition
- One thing a person did, counted by a KPI.
- Visit
- One person on one day (UTC).
What the video says
An adoption check asks one question: of the people this feature is for, how many used it? Who counts as active decides the answer as much as the usage does.
By default, active means everyone who visits. Press Change to narrow it: add up to three conditions, each a KPI you have, or something new you pick on your site.
Then decide how they combine. All means people did every one. Any means at least one. All is stricter and more precise, but it matches fewer people.
With All, go further: all in the same visit, meaning one person on one day, and in this order, each step after the previous one. Now it's a real funnel.
When every condition is a KPI you already have, Needlr estimates how many people match each week. Under 30 a week, the verdict won't be reliable. Loosen it.
A person counts as active from the day they first match, and only their uses from then on count. Define the crowd first, and the adoption rate becomes a decision.