Retry and dunning experimentation best practices
How to design statistically sound experiments when comparing retry and dunning configurations in Recurly Recover.
Why experimentation matters
Because recovery is a yes-or-no outcome for each invoice, the number of recoveries in a variant behaves like a coin flip repeated many times — some invoices recover and some won't, and the overall rate will naturally shift a bit even when nothing about the underlying performance has changed. Good experiment design accounts for that natural variability, so you can trust that a difference you observe reflects a real difference in performance rather than chance.
Key considerations
Assign invoices to variants randomly. Grouping by customer segment, card type, or invoice size instead can make your results reflect those differences rather than the configuration you're testing.
Configure experiments by randomly assigning invoices to different dunning campaigns, then compare variant performance on the Dunning Comparison Dashboard.
Only analyze invoices that have completed their full dunning cycle — open invoices haven't yet succeeded or failed, and including them will distort your results.
Significance depends on your baseline recovery rate, the size of the change's impact, and how many invoices are in each variant.
We recognize this volume isn't always achievable, especially for smaller merchants. Even without statistical significance, experimentation still provides a useful directional signal, and we encourage merchants to experiment regardless of scale.
Updated 1 day ago