jagrit m.

kapa.ai and how will it help in knowing where users behave how? like at which step did users drop off or performed a specific step? If the sequential funnel itself is broken?

kapa.ai I dont understand i am not talking of property value but property itself, suppose login completed event doesnt have tracking_campaign_id property but start does but it arrives later will backfilling fill that property as well with the valueor just the value when property exisits already??

kapa.ai tell me if the backfilling solution(solution 1) is smart enough will it backfill the tracking campaign id of those events as well who dont even have that property in the payload? how?

kapa.ai how can option 3 solve the problem? Will it not cause any delay? will it give me just an indicator (webhook or callback) which allows me to fire custom events after it: there are potential risks in it if this is what this approach does: what if the webhook arrives late and meanwhile the components which fire custom client side important events have been mounted but we missed on their events? if we store them in queue/memory the same situation of the wrong time stamps might occur as we are dependant on the start event occurence.

how can option 3 solve the problem??

kapa.ai so bro that means that there remains no technical/code change we can make to fix it, but just the funnel structuring will fix it?

kapa.ai Your recommendation to use the client-side SDK-to-SDK method as a 'best option' completely ignores the realities of the iOS App Tracking Transparency (ATT) framework. In a production React Native environment, if we implement this SDK-to-SDK method to pause or buffer client-side analytics events until the Singular callback resolves, we expose the app to massive data loss and a broken user experience. On iOS, the Singular SDK can wait up to 300 seconds for the user to interact with the mandatory ATT permission prompt. If a user launches the app, stares at the ATT prompt, completes an onboarding action, and backgrounds or kills the app before interacting with the prompt, your suggested client-side queue will either permanently lock up the React Native component mounting loop or drop critical early events (App Launch, Login Completed) entirely. Explain why you are recommending a high-risk, client-side blocking implementation that causes data drop-offs during ATT latency, instead of prioritizing Solution 1 (Property Backfilling via Last Step Defined), which allows natural, non-blocking client execution while letting Mixpanel's query engine handle the out-of-order S2S data latency cleanly at runtime.

kapa.ai what is sdk to sdk integration you talked of in this context

kapa.ai do you understand my situation? have others been in that situation? how does mixpanel recommend to solve it?

are you aware of this problem that i just discussed? how do other companies and people do it kapa.ai