Track State / Track Action not firing on Purchase Confirmation when app is suspended — expected Adobe behavior?

Hi everyone, I’m running into an issue with Adobe Analytics on our mobile app and hoping someone can clarify whether this is expected behavior or a configuration gap.

We’ve noticed that on certain flows, when a user completes a purchase and lands on the Purchase Confirmation page, if they suspend the app immediately (background the app, switch apps, lock the device, etc.), our Track State and Track Action calls for the confirmation step do not fire.

This is causing a measurable drop in attribution — we’re missing at least ~20 confirmed customers per day because the confirmation events never reach Adobe.

Expected behavior

Track State / Track Action should fire as soon as the user lands on the confirmation page, even if the app is suspended right afterward.

Actual behavior

Events only fire if the user stays active on the confirmation page long enough for the hit to dispatch. If the app is suspended immediately, the confirmation events are dropped.

Questions for the community

• Is this expected behavior with Adobe’s mobile SDK lifecycle handling?

• Does Adobe drop hits if the app is backgrounded before dispatch completes?

• Are there recommended configurations or patterns to ensure critical events (like purchase confirmation) fire reliably even during rapid app suspension?

• Should we move the confirmation event to a more synchronous trigger or queue it before the app enters background?

Any guidance or best practices would be greatly appreciated. We want to ensure our purchase tracking is accurate and not losing conversions due to lifecycle timing.

Thanks in advance!