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 all of them in Amplitude.
Test devices, staging builds and your own team, all of which Amplitude counts.
Bots and other traffic you can stop at the door with Amplitude's block filters, so it never counts.
Which events earn their keep and which are noise. Events over your allowance can be added to your count as extra MTUs, one for every 1,000 events.
Whether your plan and pricing model still match how you use Amplitude.
What's inflating your count, by how much where we can measure it, and what each fix is worth.
Your expected users and events for the year ahead, before and after the fixes, to take into your next renewal.
What to change first, and what each change might cost you in data you can no longer see.
A call with whoever owns Amplitude and whoever will make the changes.
Amplitude defines a monthly tracked user as a unique user who triggers at least one event in a calendar month. Anonymous users are counted by device ID and known users by user ID, and since February 2024 a user is counted once across your whole organisation.
Blocked data is never collected and can't be recovered, so we agree every block with you first. Dropping data only hides it in charts and doesn't reduce your volume, which is why the difference matters.
On paid plans Amplitude may charge overage fees, and admins get alerts as usage approaches and passes the limit. On the free plan, going over for three months gets the account blocked.
Amplitude is a partner of ours. Paying for users who aren’t there doesn’t help anyone, though. A clean count also makes your data more trustworthy, which is the point of having Amplitude in the first place.

Tell us your plan and roughly how your count has moved. We'll tell you whether a check is worth it.