There isn’t a way to “flush” or force the ID merge to propagate faster than the documented delay.
For both Original and Simplified ID Merge, Mixpanel updates the single-user Activity Feed in near real time (under a minute), but it can take up to 24 hours for the merged identity to be reflected consistently across all reports, including Funnels.[Simplified FAQ][Original FAQ] This is exactly why you’re seeing users appear as dropped off in onboarding funnels that span anonymous → logged‑in behavior shortly after they convert.[Funnels FAQ]
Given the docs, there’s no supported mechanism to:
trigger an immediate global recomputation of merges, or
bypass the 24‑hour propagation window for funnel calculations.
Workarounds mentioned in the docs are more about implementation hygiene than true real‑time funnel accuracy:
Make sure you call .identify() at registration/login and when reopening in a logged‑in state, and .reset() on logout, so that merges are correct and complete.[Simplified best practices]
Track your own stable user ID as an event and profile property to help debug and verify that the right events belong to the same person, even if the funnel hasn’t fully “caught up” yet.[Simplified best practices]
But the knowledge sources do not describe any official pattern that makes a cross‑anon→auth onboarding funnel fully reliable in real time; you may need to:
accept that those funnels are accurate only after the merge window (e.g. look at “yesterday and earlier”), or
temporarily analyze pre‑login and post‑login steps in separate funnels/Insights reports for real‑time monitoring, then rely on the full cross‑journey funnel for back‑looking analysis once merges have propagated.
If you’d like, describe your exact onboarding flow (events and where identify/reset are called), and I can help you sanity‑check that implementation against the documented best practices.
