Identity
How users are identified, and whether anonymous activity merges into the right user when people log in.
How users are identified, and whether anonymous activity merges into the right user when people log in.
How much of your count is visitors who never log in, and whether you need to track all of them as users.
Test devices, staging builds and your own team, which land in your count unless you filter them out.
Bots and other traffic you can filter out before it reaches your reports.
Which events you use and which are noise.
Whether your analytics, engagement and attribution tools agree on who a user is.
What's in your count that shouldn't be, by how much where we can measure it, and what each fix changes.
Expected users and events for the year ahead, before and after the fixes.
What to change first, and what each change might cost you in data you can no longer see.
A call with whoever owns your analytics and whoever will make the changes.
Product analytics platforms such as Amplitude, plus the engagement and attribution tools that share their users. If you use something else, ask us.
Some fixes stop data at the source, and you can't get it back later. We agree every one of those with you before anything changes.
Conversion rates, retention charts and your plan all start from it. When the count is off, every number built on it is off too.
No. The check is about getting the count right on the platform you already have.

Tell us which platforms you use and roughly how your user numbers have moved. We'll tell you whether a check is worth it.