if a user landing on a page is what is used to listen and fire an event to Mixpanel for instances where a user has adblocker turned on, since it is not a page load event but it still relies on the user landing on a specific page to trigger that response, could this be the reason for the discrepancy in Mixpanel event sent?
Hi event, Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
Yes, this could be a reason for discrepancies in Mixpanel event counts. When using client-side tracking (such as firing an event when a user lands on a page), ad blockers and browser privacy settings like Do Not Track (DNT) can prevent Mixpanel’s JavaScript SDK from loading or sending events. This means that even though a user lands on a page, the event may not be sent or received by Mixpanel if an ad blocker is active or DNT is enabled. As a result, you may see fewer events in Mixpanel compared to what you expect based on actual user activity.
Mixpanel specifically notes that client-side tracking can be unreliable, with the potential to lose events for 30-50% of users due to ad blockers and privacy settings. They recommend server-side tracking for more reliable data collection, as server-side events are not affected by client-side blockers or browser settings. If you must use client-side tracking, setting up a proxy server can help reduce event loss due to ad blockers, but it still may not be as reliable as server-side tracking Choosing the Right Method, Data Discrepancies, Track Events FAQ.
In summary, if your event relies on a user landing on a page and is tracked client-side, ad blockers and privacy settings can definitely cause discrepancies in the events sent to Mixpanel. Server-side tracking is recommended to avoid this issue.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Let me check the knowledge base for you again. One moment! 📚
If your Mixpanel event is triggered by a user landing on a specific page (regardless of whether it’s a traditional page load or a client-side route change), but the event is still sent from the client-side (e.g., via the JavaScript SDK), then ad blockers and privacy settings can still prevent the event from being sent to Mixpanel. The key issue is not whether the event is a "page load" event, but whether the Mixpanel SDK is able to execute and send data from the client’s browser.
If an ad blocker is active, it may block the Mixpanel SDK or requests to Mixpanel’s API endpoints, regardless of what triggers the event (page load, route change, or any other client-side action). This means that even if your logic is based on listening for a user landing on a specific page and then firing an event after an API response, the event may still not reach Mixpanel if the SDK or network request is blocked. This is a well-documented cause of discrepancies in event counts between Mixpanel and other systems, especially with client-side tracking. Mixpanel recommends server-side tracking or using a proxy to mitigate this issue, but even with a proxy, some blockers may still interfere if not configured correctly Choosing the Right Method, Data Discrepancies, Track Events FAQ.
In summary: Even if your event is not a traditional page load event, but is still triggered client-side when a user lands on a specific page, ad blockers and privacy settings can still prevent the event from being sent to Mixpanel, leading to discrepancies. The underlying issue is the client-side nature of the tracking, not the specific trigger.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
