Qonversion validates user receipts with app stores and sends subscription events to your HTTP endpoints. Keep in mind events delivery time when using webhooks to manage subscriber statuses on your back-end. Webhook delivery is asynchronous and typically completes within tens of seconds, but the exact latency depends on store-side notification timing, your server’s response time, and any retries. For real-time subscription status on the client-side, use the checkEntitlements method of the Qonversion SDK.Documentation Index
Fetch the complete documentation index at: https://documentation.qonversion.io/llms.txt
Use this file to discover all available pages before exploring further.
1. Set up the webhook URL
- Navigate to the Integrations section in your Qonversion account and select Webhooks.
- Register your URL and Qonversion will send a request
- Press the “Add new integration” or “Save” button. If the endpoint server returns a 200 response code, the integration is activated.

Sandbox webhook URL
The Webhooks integration form also exposes a separate Sandbox Webhook URL field. Production-environment events are delivered to the main URL; sandbox-environment events (environment: "sandbox") are delivered to the Sandbox URL when it is set. If you receive sandbox events but leave the Sandbox URL empty, Qonversion will fail to deliver them and they will be retried until the per-event tracking window expires.
2. Request format
Qonversion sends POST request to webhook URL every time an event occurs. The request includes anAuthorization header of the form Basic <token>, where <token> is the Header Authorization-Token Value you configured in the Webhooks integration settings - it is sent as-is, not base64-encoded as in standard HTTP Basic auth. Use it to protect your server from unwanted requests.
SSL certificate
Remember, maintaining secure connections is essential for the integrity and reliability of your application’s communication.Ensure the SSL certificate used is not expired and your server’s CA bundle is up-to-date to recognize the latest root CAs.| Column | Required | Description |
|---|---|---|
| event_name | yes | Event name provided in the integration config. See the details on the events trackedhere |
| user_id | yes | Unique user identifier assigned by Qonversion |
| custom_user_id | yes | Unique user identifier that you can set with Qonversion SDK methods:User Identifiers |
| identity_id | yes | Unique user ID for the authenticated users that you can set using identify method of the Qonversion SDK |
| advertiser_id | yes | IDFA or AAID |
| time | yes | The time an app store changed a subscription status or a time Qonversion detected the change in the UNIX epoch time format in seconds. Read more about events timehere |
| created_at | yes | The time Qonversion generated the event |
| product_id | yes | App Store or Google Play Store product identifier |
| revenue | yes | Dictionary with transaction revenue details. Only events with value filled |
| price | yes | Dictionary containing the price details of the product |
| transaction | yes | Dictionary with store transaction IDs and expiration timestamp |
| properties | yes | User properties provided by SDK as a JSON object (always present; sent as {} when the user has no properties). Read more about user properties here. |
| device_id | yes | identifierForVendor or Settings Secure Android ID. |
| app_version | no | Application version. |
| sdk_version | no | Qonversion SDK version. |
| environment | yes | ”production” or “sandbox”. |
| platform | yes | ”iOS”, “Android”, or “Stripe”. |
| ip | yes | Application device IP address. |
| country | yes | A two-letter code representing a country, defined by theISO 3166-1 alpha-2standard, is determined on the Cloud provider’s side based on the IP address of the incoming request. |
| storefront | no | Apple App Store country code (ISO 3166-1 alpha-3, e.g. “CHN”, “USA”, “GBR”). Represents the storefront from which the transaction originated. Not the user’s geographic location. Only available for iOS transactions when an App Store Connect API Certificate is configured. |
| old_product_id | no | Previous product (for product change events). |
| new_product_id | no | New product (for product change events). |
| locale | yes | A two-letter code representing a device language based on the device locale. |
| subscription_group | yes | subscription_group_identifier for iOS or Google base_plan_id for Android. Empty string for Stripe events. |
| user_install_date | yes | Timestamp when the user last installed the application. |
| project_name | yes | The project name of your app from the Qonversion dashboard. |
| app_id | yes | Store App Id. App Store ID for iOS or Android Package Name for Android. |
| quantity | no | Number of consumable in-app purchases. For non-consumable items or subscriptions, it will always return 1. Only present when the event has an associated transaction. |
| subscription_renew_count | no | Total number of times a user’s subscription has been renewed. Only present for events that carry a renewal counter (e.g. subscription renewals). |
| entitlements | yes | Granted user entitlements. Always present, delivered as a JSON object keyed by zero-based index ({"0": {...}, "1": {...}}); sent as {} when the user has no active entitlements. Entity fields are synchronised with our public API. |
| asa_attribution | no | Dictionary with Apple Search Ads attribution details. Only for events for users who were attributed with the ad. |
Revenue and price fields
There are 3 fields that contain transaction details:- The
revenuefield contains a dictionary with details depending on your integration setting Send sales as proceed. - The
pricefield always contains a gross price that is charged to a user. - The
transactionfield contains params of the transaction related to the event.
Revenue
| Column | Required | Description |
|---|---|---|
| value | yes | Value in user’s currency |
| value_usd | yes | Value in USD |
| currency | yes | Three-letter ISO currency code |
| is_proceed | yes | 1 – if value and value_usd are net excluding app stores’ commission; 0 - if values are before deducting app stores commission; |
| proceeds_rate | yes | 70 or 85; Proceeds rate that developer receives after deducting app stores commission. |
Price
| Column | Required | Description |
|---|---|---|
| value | yes | Value in user’s currency |
| value_usd | yes | Value in USD |
| currency | yes | Three-letter ISO currency code |
Transaction
| Column | Required | Description |
|---|---|---|
| transaction_id | yes | Transaction_id from App Store (e.g. 521456677817903) or Play Store (e.g. GPA.4563-9870-7648-87395) |
| original_transaction_id | yes | Transaction_id from App Store (e.g. 521456677817903) or Play Store (e.g. GPA.4563-9870-7648-87395) |
| expires | yes | Expire timestamp for purchase, prolong or product change events, event timestamp for refund or upgrade events. |
| grace_period_expires | yes | Grace period expiration timestamp. This field returns the timestamp for the grace period expiration. |
| transaction_date | yes | Timestamp when the transaction was made. |
Apple Search Ads attribution fields
You need to set up Apple Search Ads integration first, then we will send ASA attribution with all new events for only attributed users. The data in the table below can be found in theasa_attribution field.
| Column | Required | Description |
|---|---|---|
| org_id | yes | The identifier of the Organization or Campaign group Id that owns the campaign. |
| campaign_id | yes | The unique identifier for the campaign. |
| adgroup_id | yes | The identifier for the ad group. |
| keyword_id | no | The identifier for the keyword. |
| ad_id | yes | The identifier representing the assignment relationship between an ad object and an ad group. |
| country_or_region | yes | The country or region for the campaign. |
| conversion_type | yes | The type of conversion is either Download or Redownload. |
| click_date | no | The date and time when the user clicks an ad in a corresponding campaign. Available only if a user accepts App Tracking Transparency (ATT). |
| impression_date | no | The date and time when an ad view occurs in a corresponding Apple Search Ads campaign. Available only if a user accepts App Tracking Transparency (ATT). |
| claim_type | no | The type of claim is either Impression or Click. |
Retries between Qonversion and Destination Server
Qonversion increases the delivery rate to your server with retries. Retries happen automatically if your server is not responding (returns a non-2xx status, times out, or is unreachable). This substantially improves the data delivery rate. After the initial attempt fails, Qonversion schedules up to five retries spread over roughly 24 hours, then abandons the per-event delivery job. The tracking record itself is retained for 7 days. Retries have the following schedule (delay measured from the previous attempt):| Attempt | Delay since previous | Approx. time since first attempt |
|---|---|---|
| 1 | Immediate | 0 |
| 2 | 1 minute | ~1 minute |
| 3 | 5 minutes | ~6 minutes |
| 4 | ~3 hours 55 minutes | ~4 hours |
| 5 | 4 hours | ~8 hours |
| 6 | 16 hours | ~24 hours |
Tenjin Refund Keeper