Integrations

Qonversion sends subscription events, including purchases, subscriptions after free trials, renewals, refunds, and others to the integrated partners. This allows you to power your marketing and attribution platforms, as well as product analytics and retention tools, with accurate in-app subscription data. Qonversion validates user receipts directly with app stores and tracks in-app revenue even if a user doesn’t open your app. This allows you to have accurate subscription data of each subscription plan with 100% accuracy. See the list of the events Qonversion tracks and sends to the integrated partners below.

​

Tracked Events

The following section describes each event type Qonversion tracks and sends to third-party services.

​

Switching between subscriptions

Qonversion sends a ‘Subscription Renewed’ event in case of an upgrade, downgrade, or cross-grade of a subscription when a subscriber switches from his other subscription. Qonversion sends a ‘Trial Converted’ event if a user switches subscription and enters paid period at the same time. Qonversion does not send downgrade event to integrations to avoid any possible data discrepancies. Both upgrade and downgrade events are shown in Qonversion in user’s timeline available from the Customers dashboard. You can check our detailed article on subscription service level and groups here.

​

Configure Integrations

Each integration has the following settings, that affect all events sent in this integration:


• Send revenue properties If you turn this toggle off, you will not receive any revenue values for this integration. We recommend to send values, so do not turn it off unless you don’t need Qonversion to send revenue values. You can enable or disable sending revenue for each event.
• Send sales as proceed Choose if you want to send revenue values net of App Stores commission (default) or gross (before deducting App Stores commission) by switching the “Send sales as proceed” toggle.
• Send sandbox events Turn on the “Send sandbox events” toggle if you want to receive sandbox events from Qonversion to this integration while testing it.

Fine-tune each event:

• Enable event Turn off sending the event if you don’t need it in this integration.
• Send Revenue Enable or disable sending revenue value for the event.

​

Storefront

For Apple purchases, a populated storefront value is the country or region of the App Store storefront for the purchase, represented by a three-letter ISO 3166-1 alpha-3 code, such as USA, GBR, or CHN. Configure an App Store Connect API Certificate for the Apple application so Qonversion can retrieve this data; a value may still be unavailable for an individual transaction. The field identifies the App Store storefront, rather than the customer’s physical location or the country field based on the user’s IP address. In webhooks, storefront is null when its value is unavailable and is omitted when the event has no associated transaction. For Stripe and Paddle purchases, storefront is always null.

​

Event time

Qonversion can set the exact time when an event occurs for most of the events. For example, when the App Store or Google play received a payment from a user. But some events do not have the exact time. The event time for such events is set equal to the time when Qonversion detected the event while checking a user receipt. Here is the list of such events:

• Trial Canceled
• Trial Billing Retry
• Subscription Canceled
• Subscription Billing Retry
• Trial Still Active

Events are sent to integrations if tracked no later than 5 days from the moment they appeared on App Store or Google Play. If Qonversion detects an event later than five days after it originally appeared in Apple or Google, such an event will not be sent into integrations. Trial Still Active events are created in Qonversion and sent in real-time. Subscription Refunded events are sent into integrations if tracked not later than 30 days compared to the date available in user receipt on Apple or Google.

​

Event state

Event lifecycle includes several states in Qonversion. The available event states are:

• New
• In progress
• Disabled
• Stale
• Tracked

The New state is assigned to an event when Qonversion initially detects it. An event can be in this state for a few seconds before Qonversion processes it further. When the system starts processing the event, the state changes to In progress. The event eventually is assigned one of the three final states after processing: Disabled, Staled, Tracked. The final state depends on the event’s actual time (when the event happened on the app stores) and period of relevance for events. Disabled state means that the time of relevance for this event has expired. For example, Qonversion detects trial_started event that happened a few months ago before releasing the application with Qonversion SDK. This event gets Disabled state and is not sent to your project’s active integrations.

---

​

Available Integrations