State of client reactivation.Evidence before headlines.
This edition publishes the protocol Retention IQ will use before releasing any cross-vertical benchmark. It contains no observed customer averages and makes no performance claim.
When a number can be called a benchmark.
Every gate below must pass. If one fails, the publication may show methodology or formula-driven scenarios only.
Analysis plan and reporting window frozen before results are calculated
At least five independent customer organizations in every published cohort
Sends, clicks, bookings, cancellations, no-shows, completions, and attribution reconcile
Consent and suppression controls active for every included production send
Contracts and privacy terms permit de-identified aggregate analysis
A reviewer independent of the analysis checks queries, exclusions, labels, and calculations
Clicks are not returns. Bookings are not completions.
The future report will preserve every stage and denominator. Cancellations and no-shows cannot be silently removed.
| Stage | Definition | Billable? |
|---|---|---|
| Eligible recipient | Passed consent, suppression, tenant, and channel-readiness checks | No |
| Delivered send | Provider accepted or delivered under the documented definition | No |
| Click | Valid tracked click after bot and duplicate handling | No |
| Booking | Appointment or job created and linked under the attribution policy | No |
| Cancellation / no-show | Booking did not become a completed service | No |
| Completed return | Source system verifies the attributed service occurred | Yes — $75 unless an order form controls |
Required metrics
- Eligible recipients, delivered sends, clicks, bookings, cancellations, no-shows, and completed returns
- Median send-to-booking and booking-to-completion time
- Recovered revenue with median and interquartile range, not only totals
- Fees, disputes, reversals, missing-data rate, and cohort size beside every table
Required claim labels
- Observed Retention IQ aggregate — every release gate passed
- Customer-specific result — permissioned and auditable
- Planning scenario — formula-driven, not an observed result
- Third-party benchmark — direct source, date, population, and methodology caveat
Want to test the protocol on your own data?
Start with sample data. If the workflow fits, we validate permissions, data quality, consent, attribution, and completion evidence before customer data moves.