Free tool · runs in your browser · nothing uploaded
Lint your Amplitude event names in ten seconds
Paste event names, get every naming-convention violation, duplicate, PII risk, and piece of deadline debris - each finding tied to a named rule. The fastest possible smell test of a taxonomy's health.
Runs entirely in your browser - nothing is uploaded, stored, or sent anywhere. We practice what we implement.
Why do event names deserve a linter?
Because names are the one part of a taxonomy every human and every AI assistant reads, and the part that decays fastest: a deadline instruments signup_new_v2_final, a redesign strands Button Clicked, and someone puts an email address into a name where it replicates - unencrypted - into every connected tool. The linter catches the patterns we see most in audit engagements; the naming system it checks against is the same one in our free taxonomy starter and glossary.
Frequently asked questions
What does the taxonomy linter check?+
Seven transparent rules: PII/PHI terms inside event names (high severity - names are unencrypted metadata in every downstream tool), duplicate and near-duplicate names (including verb variants like click/clicked/tap), naming-convention drift against your set's dominant convention, deadline debris (v2, final, test, temp), UI-coupled names (button, icon), single-word names, and whitespace/length/charset hygiene. Every finding names its rule - no black box.
Is my event list uploaded anywhere?+
No. The linter runs entirely in your browser - there is no network request, no storage, and no analytics on your paste. Check the network tab if you'd like to verify; we're a privacy-first analytics agency and this is exactly the standard we implement for clients.
My taxonomy scored badly - now what?+
The score tells you drift exists; it can't tell you what's safe to fix, because names can't show triggers, duplicate fire paths, or identity behavior. That's what the free scored audit reads directly from your instance - ten dimensions with evidence, and a consolidation plan that keeps history queryable. Renaming events without a migration map makes things worse, not better.
Which naming convention does it recommend?+
Object-Action in Title Case ('Report Exported', 'Trial Started') - the convention our taxonomy starter documents and the one that stays guessable at 500 events. But the linter's convention check is relative: it detects YOUR set's dominant convention and flags deviations from it, because consistency beats any particular style.
Names are the smoke - the audit finds the fire
The free scored audit reads your actual instance: triggers, duplicate fire paths, identity merges, governance, warehouse agreement. Ten dimensions, evidence attached, 48-hour turnaround.
Request the free audit