free · no signup
Mixpanel installation checker
Check if Mixpanel is installed on your site, flag duplicate or render-blocking loads, then confirm events arrive in your Mixpanel project.
Scans the page's HTML in seconds. It also reports every other tracking script it finds.
about Mixpanel
Why it breaks quietly.
Mixpanel's browser SDK calls mixpanel.init with your project token. It sends page views and custom events, and links them to users through identify.
Mixpanel installs tend to break at the identity and config layer. Events go to the US servers for an EU project, every user gets merged into one profile, or page views were never turned on, and the reports look plausible but wrong.
what the free scan checks
Whether Mixpanel is in the page
The scan fetches the page's HTML and matches the vendor's script URL and install snippet.
Whether it blocks rendering
A script tag without async or defer delays the page from painting. Marketing scripts never need to.
Whether it's installed more than once
Duplicate installs usually send every event twice and inflate conversions.
How exposed the page is to blockers
A server-side readiness grade: whether tags load from domains blocklists target, and whether conversions have a server-side path.
It reads the HTML, so tags injected later (inside GTM, for example) don't show up, and it can't see events fire. That's what verification is for.
common failures
How Mixpanel goes dark.
EU projects without the EU api_host
Projects with EU data residency need the SDK's api_host set to Mixpanel's EU endpoint. Without it, events do not reach the project.
identify called with the same ID for everyone
Calling identify with a placeholder like undefined or a shared account ID merges many people into one user profile.
reset never called on logout
On shared devices, the next person to log in inherits the previous user's identity unless the app calls mixpanel.reset() on logout.
Page views are not tracked
Automatic page view tracking is an init option. If it is off and nothing calls track for page views, you only see custom events.
by hand
Check it yourself, step by step.
- 1
Open the Events view in Mixpanel and watch for your events as you click through the site.
- 2
Initialize with debug: true, or call mixpanel.set_config({ debug: true }), and watch the browser console log each event.
- 3
In Chrome DevTools, filter the Network tab for mixpanel and confirm requests go to the right regional host and succeed.
- 4
Log in and out with two test accounts and check that each shows up as a separate user profile.
questions
Asked and answered.
Can this check tell me if Mixpanel events are firing?+
No. The scan reads served HTML and can see whether Mixpanel's script or init call is present, duplicated or render-blocking. It cannot see Mixpanel bundled into your app at runtime or confirm events arrive. TracerKit's Verification tier watches real fires and alerts when a tag goes silent.
Why are my Mixpanel users merged together?+
Usually identify is being called with the same value for different people. Check what ID your app passes and that it is unique per user.
Will ad blockers block Mixpanel?+
Often, yes. Mixpanel documents proxying requests through your own domain.
check other tags
Know Mixpanel is firing, every hour of every day.
Verification watches each tag on real traffic and emails you the moment one goes silent. 14-day trial, no card.