How recovery works
Start events, finish events, timing, and why Snagr never nags someone who already paid.
Every recovery in Snagr follows the same pattern.
- Someone starts. A checkout opens, an account is created, a trial begins. This is the start event.
- Snagr waits. Nothing happens until the delay you set has passed.
- Snagr checks. If the person has already finished (paid, completed setup, upgraded), nothing is sent.
- Snagr follows up. Otherwise it runs the next step: an email, an on-site banner, a flag, or a webhook.
- They finish, Snagr stops. The finish event cancels every step still waiting.
Where events come from
| Setup | Start event | Finish event |
|---|---|---|
| Polar | Snagr sees the open checkout, failed renewal or cancellation in your store | Snagr sees the paid order |
| SDK | Your site calls snagr.track("checkout_started") | Your server sends purchase_completed |
With the SDK you can use any event names you like, such as signed_up and onboarding_completed.
Who gets emailed
Snagr only emails people whose address is verified: a Polar customer, or an email your server confirmed. It also skips anyone who unsubscribed, bounced or marked a message as spam, and checks again before every step.
Timing
Each step has its own delay, from a few minutes up to 90 days after the previous step. A typical checkout flow sends one email after 30 minutes, another after a day, and a last one after three days.