The audit your Amplitude setup actually deserves.
Most teams inherit Amplitude setups that look fine on the surface but quietly break the data they depend on. We run 90+ checks against your configuration, surface what's broken, and give you the specific fix for each one.
Built by Adasight, who do this audit manually for clients every week.
Or scan a URL right now — no signup, ~10 seconds. Covers install quality; the full audit needs API credentials.
Configuration metadata only
We read your event taxonomy, settings, and feature config — never your user events, never PII. Your API credentials are used for the audit and discarded.
Adasight runs this manually
Every check we automate is one we already do for paying clients. The rules come from real engagements, not a generic best-practices document.
Why this matters, every time
Each finding includes the reasoning, the consequence, and the specific fix — code snippet where applicable. Less consulting deck, more teach-and-fix.
Sample of 24 live checks. 90+ shipping.
Every rule below runs against your Amplitude project's configuration metadata — no user data ever leaves your workspace. Importance flag tells you which findings to act on first.
Coming in Sprint 2: Session Replay · Guides & Surveys · Web Experimentation · Governance.
What we publish.
What makes a good Amplitude tracking plan
Most tracking plans are documents. The good ones are operating models that hold up after the analyst who wrote them leaves.
Five Amplitude misconfigurations that quietly kill data quality
The defaults look fine. The data isn't. The five most common misconfigurations Adasight finds on every audit, and how to fix them.
Session Replay masking — the privacy guide nobody wrote
Default masking covers form inputs. It does not cover account balances, internal IDs, or PII rendered in plain text. Here's what to actually configure.
Find what's wrong with your Amplitude.
Beta access opens in waves. Add yourself to the list — we'll send the link when we're ready for you.