Duplicate deliveries for a small percentage of iOS transaction events

data repair is complete end-to-end

We are continuing to monitor for any further issues.

Duplicated records have been removed — dashboards and exports now show corrected figures, and per-user payment summaries have been recalculated.

Removal of duplicated records from dashboards and exports is in progress. If your project ingests Qonversion webhooks or integration events and you store them raw, duplicated events can be identified by the same App Store transaction ID appearing under different Qonversion user IDs; deduplicating on (store transaction ID, event type) is safe.

Between August 17 and August 20, 11:10 UTC, a defect caused some iOS subscription transactions to be duplicated under more than one user profile. Affected projects may see inflated revenue and subscription-event counts in dashboards and exports, and some duplicate events were delivered to connected integrations and webhook endpoints. No payments or end-user purchases were affected — this is limited to analytics data. The defect is disabled and no new duplicates are being created. We are removing the duplicated data and will contact affected accounts directly with details.

Approximately 5% of all events sent to
third-party integrations during this window were duplicates, and up to
approximately 8% for customer webhooks