Common questions
Fix the usual confusion around live events, localhost, test users, privacy, speed, and no-code tools.
Answers to the setup questions founders usually hit
My users are not appearing in the dashboard
The most common reason is that identify() is not being called after login, or it is called with an empty user object. Also make sure you are not on localhost.
The live event feed shows nothing
Check that the script tag is in the <head> section of the page that actually loads. In browser DevTools, look for a request to cdn.dropfix.in.
Can my test users pollute the data?
Yes. Add your own user IDs in Settings -> Health Scoring -> Never track these users so DropFix ignores your internal activity.
Will the script slow down my app?
No. The script loads with async, never blocks rendering, is under 5KB, and sends small background batches every 5 seconds.
Does DropFix see passwords or private messages?
No. DropFix captures button clicks, page views, and form submissions, but never reads field values. Password fields are explicitly skipped.
What if a user is on multiple devices?
As long as identify() uses the same user ID on both devices, activity is combined into one user profile.
Will marketing page clicks appear in analytics?
DropFix automatically excludes common marketing routes like /pricing, /about, /blog, /signup, and /login. Add custom public routes in Settings -> Health Scoring.
Can I use DropFix with Webflow, Bubble, or no-code tools?
Yes for the script tag. For identify(), your tool needs a way to run JavaScript after login. Email febin@dropfix.in if you need help.