Fixing Mixpanel Funnel Step Sequencing with Delayed Singular Server-to-Server Event in React Native App

Our React Native app initializes Mixpanel early to grab the distinct_id, passes it to the Singular SDK config as a global property, and immediately fires client-side product events (like App Launch and Login Completed) on mount without blocking the component lifecycle. On the Mixpanel UI, we are setting up a strict sequential funnel where Step 1 is the Singular S2S __START__ event (filtered by tracker_campaign_id), Step 2 is Login Completed, Step 3 is Playback Started, and Step 4 is Subscription Purchased. Meanwhile, Singular's server-to-server __START__ event carries all our marketing campaign data but arrives significantly later due to standard network latency and iOS ATT prompt delays. Because Mixpanel evaluates linear funnel steps in strict chronological order based on timestamps, placing this late-arriving __START__ event as Step 1 breaks our sequence completely, dropping users from the funnel and yielding an overall 0% conversion rate. We cannot block or pause the app's components to wait for the marketing data without ruining the user experience or losing events, so we need to know the official architectural blueprint to fix this sequencing problem inside Mixpanel without changing our app lifecycle or faking timestamps.