Recovery dashboard and abandonment capture

Recovery tracks checkout sessions that can be brought back through email, SMS, or provider-driven follow-up. It is store-scoped, so the selected store controls the queue, settings, templates, provider callbacks, and recovered revenue.

What counts as recoverable

A checkout becomes recoverable when RocketCheckout can identify enough session and contact context to follow up. That may include checkout activity, cart or order context, email, phone, consent state, and provider configuration.

Capturing contact details

When a shopper enters an email or phone during checkout, the SDK or connector should capture it as soon as the field value is usable, not only after a completed purchase. This helps recovery work when the shopper closes the browser, abandons the tab, or leaves before payment.

What happens if the browser closes

If the contact detail and checkout/session context were already captured and sent, RocketCheckout can mark the checkout as recoverable. If the endpoint is temporarily unavailable, platform plugins should queue eligible events locally and retry when the service is back.

Recovered revenue

Recovered revenue should represent users who came back and actually purchased after recovery influence. Dashboard recovered revenue and Recovery page revenue should agree for the same store and time range. If they do not, check whether one page is using a different range, attribution source, or selected store.

Issues panel

Recovery issues should only appear when something is blocked, failing, or waiting on infrastructure. When provider settings are healthy and no issues remain, the issues panel should clear instead of staying on the page.