# Qonversion

## Docs

- [TASK JOURNAL](https://documentation.qonversion.io/TASK_JOURNAL.md)
- [Get active subscriptions chart data](https://documentation.qonversion.io/api-reference/analytics-charts/get-active-subscriptions-chart-data.md): Retrieve active subscriptions analytics. Product filters and segmentation. filter[user_id] and filter[device_id] are NOT applied.
- [Get paid subscriptions movement chart data](https://documentation.qonversion.io/api-reference/analytics-charts/get-paid-subscriptions-movement-chart-data.md): Retrieve paid subscriptions movement analytics. Common + product filters only. Segmentation, filter[user_id], and filter[device_id] are NOT applied.
- [Get proceeds chart data](https://documentation.qonversion.io/api-reference/analytics-charts/get-proceeds-chart-data.md): Retrieve proceeds analytics. All filters and segmentation supported.
- [Get users overview chart data](https://documentation.qonversion.io/api-reference/analytics-charts/get-users-overview-chart-data.md): Retrieve users overview analytics. User filters and segmentation, no product filters.
- [Get analytics card data](https://documentation.qonversion.io/api-reference/analytics/get-analytics-card-data.md): Returns the current value of a scalar dashboard card. Cards bundle several related metrics (e.g. `realtime` returns today's trials, subscriptions, in-app purchases and tracked revenue as a four-row table).
- [Get analytics chart data](https://documentation.qonversion.io/api-reference/analytics/get-analytics-chart-data.md): Returns time-series data for a chart. `chart_code` selects the metric; pass query parameters to constrain the time range and segmentation.
- [Get analytics chart metadata](https://documentation.qonversion.io/api-reference/analytics/get-analytics-chart-metadata.md): Returns the chart's display metadata: available filter attributes and their concrete values (pre-scoped to the project), available segmentation dimensions, supported time units, and chart types. Use this to build a UI / discover the `filter[<attribute>][]` and `segmentation` values for `GET /v4/anal…
- [Get analytics insights](https://documentation.qonversion.io/api-reference/analytics/get-analytics-insights.md): Returns AI-generated insights for the project over the last `period` days. Responses are cached on the upstream; pass `force=true` to regenerate. The `insights[]` array groups observations by type (`critical`, `positive`, `tip`, `info`) — each item has a short `title`, a longer `body`, and a suggest…
- [Get cohort analytics data](https://documentation.qonversion.io/api-reference/analytics/get-cohort-analytics-data.md): Returns cohort-over-time tables for the project. A cohort is a group of users sharing an acquisition event (see `cohort_definition`). Rows are cohorts, columns are time offsets (see `grouping`). Cells are the `metric` (revenue, subscriptions, payers, ARPU, ARPPU).
- [Get cohort analytics metadata](https://documentation.qonversion.io/api-reference/analytics/get-cohort-analytics-metadata.md): Returns the discrete value sets needed to build a cohort query: available `mode`s, `grouping`s, `metric`s, `cohort_definition`s, and filter attributes with their concrete values (pre-scoped to the project).
- [Get LTV analytics data](https://documentation.qonversion.io/api-reference/analytics/get-ltv-analytics-data.md): Returns lifetime-value curves for cohorts in the requested range. `series` is a list of time-indexed revenue (or ARPU / ARPPU) points; `segment` + `segments` let you split the curve by an attribute.
- [Get LTV analytics metadata](https://documentation.qonversion.io/api-reference/analytics/get-ltv-analytics-metadata.md): Returns available `mode`s, `segmentation` attributes, and project-scoped filter attribute values for the LTV endpoint.
- [Get LTV trial-conversion analytics data](https://documentation.qonversion.io/api-reference/analytics/get-ltv-trial-conversion-analytics-data.md): Returns the trial→paid conversion rate for the requested cohort range — number of trials started, number that converted, and the conversion rate as a decimal (0.0–1.0). Accepts the same filter and `mode`/`revenue_type` shape as the LTV chart endpoint.
- [Get supported analytics currencies](https://documentation.qonversion.io/api-reference/analytics/get-supported-analytics-currencies.md): Returns the list of three-letter ISO 4217 currency codes accepted by the `currency` query parameter across analytics endpoints. `USD` is always first and is the implicit default when `currency` is omitted.
- [Create an automation](https://documentation.qonversion.io/api-reference/automations/create-an-automation.md): Deprecated — the Automations product surface has been removed; this API remains available for existing integrations only. Creates a new automation for the authenticated project.
- [Delete an automation](https://documentation.qonversion.io/api-reference/automations/delete-an-automation.md): Deprecated — the Automations product surface has been removed; this API remains available for existing integrations only. Permanently deletes an automation by ID.
- [Get an automation](https://documentation.qonversion.io/api-reference/automations/get-an-automation.md): Deprecated — the Automations product surface has been removed; this API remains available for existing integrations only. Returns a single automation by ID.
- [List automations](https://documentation.qonversion.io/api-reference/automations/list-automations.md): Deprecated — the Automations product surface has been removed; this API remains available for existing integrations only. Returns a paginated list of automations for the authenticated project. Automations are ordered by ID (descending). Supports cursor-based pagination via `limit` and `starting_afte…
- [Update an automation](https://documentation.qonversion.io/api-reference/automations/update-an-automation.md): Deprecated — the Automations product surface has been removed; this API remains available for existing integrations only. Fully replaces an automation's mutable fields. All mutable fields must be provided.
- [Update automation status](https://documentation.qonversion.io/api-reference/automations/update-automation-status.md): Deprecated — the Automations product surface has been removed; this API remains available for existing integrations only. Toggles the status of an automation between `active` and `inactive`.
- [Delete a customer (GDPR)](https://documentation.qonversion.io/api-reference/customers/delete-a-customer-gdpr.md): Permanently deletes a customer and all associated personal data. This operation is irreversible and intended for GDPR right-to-erasure requests. Returns 204 on success.
- [Get a customer](https://documentation.qonversion.io/api-reference/customers/get-a-customer.md): Returns a single customer by ID.
- [Get aggregated customer metrics](https://documentation.qonversion.io/api-reference/customers/get-aggregated-customer-metrics.md): Returns aggregated metrics for customers of the authenticated project.
- [Get customer metrics (Analytics)](https://documentation.qonversion.io/api-reference/customers/get-customer-metrics-analytics.md): Retrieve aggregated customer metrics for a project. Accepts the same filters and `search` as the customers list (no `page`, `limit`, or sort).
- [Get customers list](https://documentation.qonversion.io/api-reference/customers/get-customers-list.md): Retrieve a paginated list of customers with optional filters and search.
- [Grant a permission to a customer](https://documentation.qonversion.io/api-reference/customers/grant-a-permission-to-a-customer.md): Grants a permission to the specified customer. Returns 201 with a Location header pointing to the new permission resource. If `expires_at` is provided it must be a valid RFC 3339 / ISO 8601 timestamp.
- [List customer permissions](https://documentation.qonversion.io/api-reference/customers/list-customer-permissions.md): Returns a list of all active permissions for the specified customer.
- [List customers](https://documentation.qonversion.io/api-reference/customers/list-customers.md): Returns a paginated list of customers for the authenticated project. Manifest-compliant: list envelope, ISO 8601 timestamps.
- [Revoke a customer permission](https://documentation.qonversion.io/api-reference/customers/revoke-a-customer-permission.md): Revokes a specific permission from a customer. Returns 204 on success. Returns 404 if the customer or permission does not exist.
- [Set customer properties](https://documentation.qonversion.io/api-reference/customers/set-customer-properties.md): Sets one or more custom properties on a customer. Accepts up to 100 key/value pairs per request. Keys must be 1–256 characters; values must be at most 1024 characters.
- [Create an entitlement definition](https://documentation.qonversion.io/api-reference/entitlements/create-an-entitlement-definition.md): Creates a new entitlement definition for the authenticated project.
- [Delete an entitlement definition](https://documentation.qonversion.io/api-reference/entitlements/delete-an-entitlement-definition.md): Deletes an entitlement definition by ID. Returns 204 on success. Returns 404 if not found.
- [Get an entitlement definition](https://documentation.qonversion.io/api-reference/entitlements/get-an-entitlement-definition.md): Returns a single entitlement definition by ID.
- [Grant an entitlement](https://documentation.qonversion.io/api-reference/entitlements/grant-an-entitlement.md): Manually grants an entitlement to a user. **Requires Secret Key authentication.**
- [Grant an entitlement to a user](https://documentation.qonversion.io/api-reference/entitlements/grant-an-entitlement-to-a-user.md): Grants an entitlement definition to a specific user, optionally with an expiry time. Attempting to extend or modify a user entitlement whose source is a paid purchase (store or Stripe) returns `422 paid_entitlement`.
- [List entitlement definitions](https://documentation.qonversion.io/api-reference/entitlements/list-entitlement-definitions.md): Returns a paginated list of entitlement definitions for the authenticated project. Entitlements are ordered by creation date (newest first).
- [List user entitlements](https://documentation.qonversion.io/api-reference/entitlements/list-user-entitlements.md): Returns all entitlements currently granted to the specified user. The response is wrapped in the standard list envelope, but pagination is not supported on this endpoint — `has_more` is always `false` and the full set is returned in a single call.
- [Retrieve entitlements](https://documentation.qonversion.io/api-reference/entitlements/retrieve-entitlements.md): Retrieves all entitlements for a user.
- [Revoke a user entitlement](https://documentation.qonversion.io/api-reference/entitlements/revoke-a-user-entitlement.md): Revokes a previously granted entitlement from a user. Only entitlements whose source is `manual` can be revoked. Returns 204 on success, 404 if the entitlement is not active for the user, and `422 paid_entitlement` when the entitlement came from a paid purchase (store or Stripe).
- [Revoke an entitlement](https://documentation.qonversion.io/api-reference/entitlements/revoke-an-entitlement.md): Revokes a manually granted entitlement from a user. **Requires Secret Key authentication.**
- [Update an entitlement definition (partial)](https://documentation.qonversion.io/api-reference/entitlements/update-an-entitlement-definition-partial.md)
- [List events](https://documentation.qonversion.io/api-reference/events/list-events.md): Returns a list of event definitions (track events) for the authenticated project. Events are emitted by the SDK and represent subscription lifecycle and user behavior.
- [Attach a user to an experiment group](https://documentation.qonversion.io/api-reference/experiments/attach-a-user-to-an-experiment-group.md): Manually assigns a user to a specific experiment group. The assignment persists; raising traffic later does not re-admit previously rejected users, and finishing the experiment releases all users. It also invalidates the SDK's in-memory config cache.
- [Change experiment status](https://documentation.qonversion.io/api-reference/experiments/change-experiment-status.md): Changes the status of an experiment (e.g. start, pause, finish).
- [Create an experiment](https://documentation.qonversion.io/api-reference/experiments/create-an-experiment.md): Creates a new experiment. Returns 201 with the created experiment and Location header.
- [Create an experiment group](https://documentation.qonversion.io/api-reference/experiments/create-an-experiment-group.md): Creates a new group for the specified experiment. Returns 201 with Location header.
- [Delete an experiment](https://documentation.qonversion.io/api-reference/experiments/delete-an-experiment.md): Deletes an experiment by ID. Returns 204 on success.
- [Delete an experiment group](https://documentation.qonversion.io/api-reference/experiments/delete-an-experiment-group.md): Deletes the specified experiment group. Returns 204 on success.
- [Detach a user from an experiment](https://documentation.qonversion.io/api-reference/experiments/detach-a-user-from-an-experiment.md): Removes a user's assignment from an experiment, invalidates the SDK's in-memory config cache, and makes the user eligible for automatic experiment assignment on subsequent requests.
- [Get an experiment](https://documentation.qonversion.io/api-reference/experiments/get-an-experiment.md): Returns a single experiment by ID.
- [Get experiments analytics summary](https://documentation.qonversion.io/api-reference/experiments/get-experiments-analytics-summary.md): Returns aggregated analytics summary for experiments.
- [List experiment groups](https://documentation.qonversion.io/api-reference/experiments/list-experiment-groups.md): Returns all groups for the specified experiment.
- [List experiments](https://documentation.qonversion.io/api-reference/experiments/list-experiments.md): Returns all experiments for the authenticated project.
- [Partially update an experiment](https://documentation.qonversion.io/api-reference/experiments/partially-update-an-experiment.md): Updates specified fields of an experiment. Only provided fields are updated.
- [Update an experiment group](https://documentation.qonversion.io/api-reference/experiments/update-an-experiment-group.md): Updates fields of the specified experiment group. All fields optional.
- [Create export (async)](https://documentation.qonversion.io/api-reference/exports/create-export-async.md): Creates a new data export task. Returns 202 Accepted with a Location header pointing to the status endpoint. Exports are project-scoped and require the RAW_DATA_ACCESS feature.
- [Get export status](https://documentation.qonversion.io/api-reference/exports/get-export-status.md): Check the status of an export or download the result.
- [List past exports](https://documentation.qonversion.io/api-reference/exports/list-past-exports.md): Returns a list of past exports for the authenticated project.
- [Create an identity link](https://documentation.qonversion.io/api-reference/identities/create-an-identity-link.md): Links a Qonversion anonymous user to an external identity ID. If `user_id` is null, a new user is created and linked. This is the mechanism for matching Qonversion anonymous users with your own user IDs.
- [Get an identity by external ID](https://documentation.qonversion.io/api-reference/identities/get-an-identity-by-external-id.md): Returns the identity linked to the specified external ID. An identity represents the association between a Qonversion anonymous user and an external user identifier from your system.
- [Create an identity](https://documentation.qonversion.io/api-reference/identity/create-an-identity.md): Creates an identity. If `user_id` is not provided, a new Qonversion user is created automatically.
- [Retrieve an identity](https://documentation.qonversion.io/api-reference/identity/retrieve-an-identity.md): Retrieves an identity by its ID.
- [Create integration](https://documentation.qonversion.io/api-reference/integrations/create-integration.md): Creates a new integration for the project.
- [Delete integration](https://documentation.qonversion.io/api-reference/integrations/delete-integration.md): Permanently deletes an integration.
- [Get integrations metadata](https://documentation.qonversion.io/api-reference/integrations/get-integrations-metadata.md): Returns the catalog of supported integration providers grouped by category. Each item exposes its `slug` (use as `integration` in `POST /v4/integrations`) and `allowedStores` (the subset of `target_platform` values the provider supports). Per-provider credential schemas are **not** returned — creden…
- [List integrations](https://documentation.qonversion.io/api-reference/integrations/list-integrations.md): Returns every integration configured for the project. There is no cursor or offset pagination: the full set is returned in a single call and `has_more` is always `false`.
- [Update integration status](https://documentation.qonversion.io/api-reference/integrations/update-integration-status.md): Enables or disables an integration.
- [Create an offering](https://documentation.qonversion.io/api-reference/offerings/create-an-offering.md): Legacy — Offerings are superseded by Remote Configs; create Remote Configs for new integrations instead. Creates a new offering for the authenticated project. If the project has no offerings yet, the new one is auto-promoted to main (`tag` will be `1` in the response even if it was omitted in the re…
- [Delete an offering](https://documentation.qonversion.io/api-reference/offerings/delete-an-offering.md): Legacy — Offerings are superseded by Remote Configs; use Remote Configs for new integrations. Removes the offering and its product attachments. Experiment-variant offerings (owned by the experiments service) cannot be deleted via this API and return `422`.
- [Get an offering](https://documentation.qonversion.io/api-reference/offerings/get-an-offering.md): Legacy — Offerings are superseded by Remote Configs; use Remote Configs for new integrations. Returns a single offering by ID.
- [List offerings](https://documentation.qonversion.io/api-reference/offerings/list-offerings.md): Legacy — Offerings are superseded by Remote Configs; use Remote Configs for new integrations. Returns regular offerings only. Experiment-variant offerings (owned by the experiments service) are excluded.
- [Set main offering](https://documentation.qonversion.io/api-reference/offerings/set-main-offering.md): Legacy — Offerings are superseded by Remote Configs; use Remote Configs for new integrations.
- [Update an offering](https://documentation.qonversion.io/api-reference/offerings/update-an-offering.md): Legacy — Offerings are superseded by Remote Configs; use Remote Configs for new integrations. Partial update. Only supplied fields are changed. `product_ids` replaces the full list in the given order — pass `[]` to detach all products, omit the field to leave the list unchanged.
- [Create a product](https://documentation.qonversion.io/api-reference/products/create-a-product.md): Creates a new product for the authenticated project.
- [Delete a product](https://documentation.qonversion.io/api-reference/products/delete-a-product.md): Deletes a product by ID. Returns 204 on success. Returns 404 if the product does not exist.
- [Get a product](https://documentation.qonversion.io/api-reference/products/get-a-product.md): Returns a single product by ID.
- [Get products](https://documentation.qonversion.io/api-reference/products/get-products.md): Retrieve a single product by ID, or omit the ID to get all dashboard products.
- [List products](https://documentation.qonversion.io/api-reference/products/list-products.md): Returns a paginated list of products for the authenticated project. Products are ordered by creation date (newest first). Manifest-compliant: list envelope, string enums, ISO 8601 timestamps.
- [Patch a product](https://documentation.qonversion.io/api-reference/products/patch-a-product.md): Partially updates a product. Only the submitted fields are updated — omitted fields remain unchanged.
- [Update a product](https://documentation.qonversion.io/api-reference/products/update-a-product.md): Replaces all product fields. Unlike PATCH, all fields must be provided — omitted fields are reset to defaults.
- [Update a product (partial)](https://documentation.qonversion.io/api-reference/products/update-a-product-partial.md)
- [Get project settings](https://documentation.qonversion.io/api-reference/project-settings/get-project-settings.md): Returns the settings for the authenticated project, including API keys, proxy URLs, and project name.
- [Get store configuration](https://documentation.qonversion.io/api-reference/project-settings/get-store-configuration.md): Returns the store configuration for the specified platform. Sensitive fields (private keys, service account credentials) are masked with boolean flags (has_connect_private_key, has_service_account_key, etc.).
- [Regenerate project secret key](https://documentation.qonversion.io/api-reference/project-settings/regenerate-project-secret-key.md): Regenerates the project's secret key. The old key is revoked; clients may see a short grace period (seconds) while internal caches expire. This is a destructive operation.
- [Update project settings](https://documentation.qonversion.io/api-reference/project-settings/update-project-settings.md): Partially updates the project settings. Only provided fields are changed.
- [Update store configuration](https://documentation.qonversion.io/api-reference/project-settings/update-store-configuration.md): Updates the store configuration for the specified platform. For Apple: if private keys are not provided, existing values are preserved. For Google: if service account key is not provided, existing value is preserved.
- [Create a purchase](https://documentation.qonversion.io/api-reference/purchases/create-a-purchase.md): Records a purchase for a user. Stripe and Paddle are the recommended paths when calling this API directly; App Store and Play Store purchases normally flow through the Qonversion SDK and rarely need to be POSTed manually.
- [List purchases for a user](https://documentation.qonversion.io/api-reference/purchases/list-purchases-for-a-user.md): Returns a paginated list of purchases for the specified user. Purchases are ordered by purchase date (newest first). Supports cursor-based pagination and optional platform filtering.
- [Attach a user to a remote configuration](https://documentation.qonversion.io/api-reference/remote-configurations/attach-a-user-to-a-remote-configuration.md): Pins a specific user to this configuration, overriding segment and percentage targeting rules. The pin is never re-evaluated and survives config edits until removed; it also invalidates the SDK's in-memory config cache.
- [Change remote configuration status](https://documentation.qonversion.io/api-reference/remote-configurations/change-remote-configuration-status.md): Changes the status of a remote configuration. Allowed transitions: `draft` → `active`, `draft` → `archived`, `active` → `archived`. Archiving is terminal — an archived configuration can only be deleted. Only `active` configurations are served to the SDK.
- [Create a remote configuration](https://documentation.qonversion.io/api-reference/remote-configurations/create-a-remote-configuration.md): Creates a new remote configuration. New configurations start in `draft` status. Returns 201 with the created configuration and a Location header.
- [Delete a remote configuration](https://documentation.qonversion.io/api-reference/remote-configurations/delete-a-remote-configuration.md): Deletes a remote configuration by ID. Returns 204 on success.
- [Detach a user from a remote configuration](https://documentation.qonversion.io/api-reference/remote-configurations/detach-a-user-from-a-remote-configuration.md): Removes a user's manual pin to this configuration, invalidates the SDK's in-memory config cache, and makes the user eligible for automatic targeting evaluation on the next request.
- [Get a remote configuration](https://documentation.qonversion.io/api-reference/remote-configurations/get-a-remote-configuration.md): Returns a single remote configuration by ID, including its read-only inline `payload` values (`{}` when unset).
- [Get the payload mapping](https://documentation.qonversion.io/api-reference/remote-configurations/get-the-payload-mapping.md): Returns the payload **mapping** — the key → type schema that tells the SDK how to interpret each payload key. This is the schema, not the values: see the payload endpoint for the JSON values delivered to the SDK.
- [Get the payload values](https://documentation.qonversion.io/api-reference/remote-configurations/get-the-payload-values.md): Returns the payload **values** — the actual JSON object delivered to the SDK for this configuration (`{}` when unset). This is distinct from the payload mapping, which describes the key → type schema.
- [List remote configurations](https://documentation.qonversion.io/api-reference/remote-configurations/list-remote-configurations.md): Returns a paginated list of remote configurations for the authenticated project. Configurations are ordered by creation date (newest first). List items do not include the inline `payload` values — read a single configuration or the payload endpoint to fetch them.
- [Replace the payload values](https://documentation.qonversion.io/api-reference/remote-configurations/replace-the-payload-values.md): Replaces the payload **values** delivered to the SDK. Full replace: the supplied `data` object entirely overwrites the stored payload — to change one key, read the current payload, modify it, and send the whole object back. An empty object `{}` clears the payload. Requests are limited to 64 KiB.
- [Set the payload mapping](https://documentation.qonversion.io/api-reference/remote-configurations/set-the-payload-mapping.md): Replaces the payload **mapping** (key → type schema). Full replace: the supplied `data` object becomes the complete mapping. Allowed types: `String`, `Number`, `Bool`, `Json`, `Color`, `Products`, `Screens`.
- [Update a remote configuration (full replace)](https://documentation.qonversion.io/api-reference/remote-configurations/update-a-remote-configuration-full-replace.md): Replaces the configuration's editable fields. `name` is required; omitted optional fields are reset. Use the status and payload endpoints to change status or payload values.
- [Create scheduled report](https://documentation.qonversion.io/api-reference/scheduled-reports/create-scheduled-report.md): Creates a new scheduled report.
- [Delete scheduled report](https://documentation.qonversion.io/api-reference/scheduled-reports/delete-scheduled-report.md): Deletes a scheduled report.
- [Get scheduled report](https://documentation.qonversion.io/api-reference/scheduled-reports/get-scheduled-report.md): Returns details for a single scheduled report.
- [List available destinations](https://documentation.qonversion.io/api-reference/scheduled-reports/list-available-destinations.md): Returns all available report destinations (email, S3, GCS, etc.).
- [List scheduled reports](https://documentation.qonversion.io/api-reference/scheduled-reports/list-scheduled-reports.md): Returns all scheduled reports for the authenticated project.
- [Send test report](https://documentation.qonversion.io/api-reference/scheduled-reports/send-test-report.md): Triggers a test send for a scheduled report. Returns 202 Accepted.
- [Update scheduled report](https://documentation.qonversion.io/api-reference/scheduled-reports/update-scheduled-report.md): Partially update a scheduled report. Omit any field to keep its current value; at least one field must be supplied.
- [Create a screen](https://documentation.qonversion.io/api-reference/screens/create-a-screen.md): Deprecated — the Screens product surface has been removed; this API remains available for existing integrations only. Creates a new screen skeleton for the authenticated project.
- [Delete a screen](https://documentation.qonversion.io/api-reference/screens/delete-a-screen.md): Deprecated — the Screens product surface has been removed; this API remains available for existing integrations only. Permanently deletes a screen by ID.
- [Duplicate a screen](https://documentation.qonversion.io/api-reference/screens/duplicate-a-screen.md): Deprecated — the Screens product surface has been removed; this API remains available for existing integrations only. Creates a copy (duplicate) of an existing screen. The duplicated screen is returned with a new `id` and status `draft`. No request body is required.
- [Get a screen](https://documentation.qonversion.io/api-reference/screens/get-a-screen.md): Deprecated — the Screens product surface has been removed; this API remains available for existing integrations only. Returns a single screen by ID.
- [Get per-screen analytics](https://documentation.qonversion.io/api-reference/screens/get-per-screen-analytics.md): Deprecated — the Screens product surface has been removed; this API remains available for existing integrations only. Returns analytics metrics for a single screen. Supports optional time-range, environment, currency, and unit filters.
- [Get screens analytics overview](https://documentation.qonversion.io/api-reference/screens/get-screens-analytics-overview.md): Deprecated — the Screens product surface has been removed; this API remains available for existing integrations only. Returns aggregated analytics metrics across all screens for the authenticated project. Supports optional time-range, environment, currency, and unit filters.
- [List screens](https://documentation.qonversion.io/api-reference/screens/list-screens.md): Deprecated — the Screens product surface has been removed; this API remains available for existing integrations only. Returns a paginated list of screens for the authenticated project. Screens are ordered by creation date (newest first) and include every screen visible in the Qonversion dashboard (s…
- [Publish a screen](https://documentation.qonversion.io/api-reference/screens/publish-a-screen.md): Deprecated — the Screens product surface has been removed; this API remains available for existing integrations only. Publishes a screen, setting its status to `published`. No request body is required.
- [Update a screen](https://documentation.qonversion.io/api-reference/screens/update-a-screen.md): Deprecated — the Screens product surface has been removed; this API remains available for existing integrations only. Updates a screen's name. All mutable fields must be provided.
- [Create a segment](https://documentation.qonversion.io/api-reference/segments/create-a-segment.md): Creates a new segment. Returns 201 with the created segment and Location header.
- [Delete a segment](https://documentation.qonversion.io/api-reference/segments/delete-a-segment.md): Deletes a segment by ID. Returns 204 on success. System segments cannot be deleted (422).
- [Get a segment](https://documentation.qonversion.io/api-reference/segments/get-a-segment.md): Returns a single segment by ID.
- [List segments](https://documentation.qonversion.io/api-reference/segments/list-segments.md): Returns a paginated list of segments for the authenticated project. Segments are ordered by creation date (newest first).
- [List system segments](https://documentation.qonversion.io/api-reference/segments/list-system-segments.md): Returns all predefined system segments. System segments are read-only and cannot be modified or deleted.
- [Update a segment (full replace)](https://documentation.qonversion.io/api-reference/segments/update-a-segment-full-replace.md): Replaces all fields of a segment. All fields are required.
- [Create user properties](https://documentation.qonversion.io/api-reference/user-properties/create-user-properties.md): Sets properties for a user. Supports partial success - returns both saved properties and errors.
- [List properties for a user](https://documentation.qonversion.io/api-reference/user-properties/list-properties-for-a-user.md): Returns all stored properties for the specified user (up to 100 per user). The response is always a single page — there is no cursor pagination, so `has_more` is always `false` and `next_cursor` is always `null`. Qonversion-defined keys are prefixed with `_q_` (e.g., `_q_email`).
- [Retrieve user properties](https://documentation.qonversion.io/api-reference/user-properties/retrieve-user-properties.md): Retrieves all properties for a given user. Up to 100 properties per user.
- [Set (upsert) properties for a user](https://documentation.qonversion.io/api-reference/user-properties/set-upsert-properties-for-a-user.md): Upserts one or more properties for the specified user (1-100 items per call). Each property is identified by a key; existing values are overwritten. Supports partial success: as long as **at least one** property passes validation, the response is 200 with successfully saved properties under `saved_p…
- [Create a user](https://documentation.qonversion.io/api-reference/users/create-a-user.md): Create a new Qonversion user. The server generates the `QON_…` user id and returns it in the response body and the `Location` header.
- [Get a user](https://documentation.qonversion.io/api-reference/users/get-a-user.md): Returns a single user by ID.
- [Retrieve a user](https://documentation.qonversion.io/api-reference/users/retrieve-a-user.md): Retrieves a Qonversion user by their ID.
- [Changelog](https://documentation.qonversion.io/changelog.md): Latest updates and improvements to the Qonversion platform
- [Account Overview](https://documentation.qonversion.io/docs/account-overview.md): A single page that aggregates analytics across all projects in your organization.
- [Migrating from Adapty to Qonversion](https://documentation.qonversion.io/docs/adapty-migration-guide.md): We have prepared this guide to help you move your infrastructure seamlessly from Adapty to Qonversion. Although this guide is comprehensive and should enable you to transfer the entire infrastructure smoothly, feel free to reach out to support if you have any questions.
- [Adjust](https://documentation.qonversion.io/docs/adjust.md): Send iOS and Android in-app subscription events to Adjust with Qonversion
- [AI Image Generation](https://documentation.qonversion.io/docs/ai-image-generation.md): Just describe what you want, choose a style, and let the AI handle the rest.
- [Localization](https://documentation.qonversion.io/docs/ai-localization.md): Translate all text in your No-Code screens into multiple languages, manually or with AI.
- [Amazon S3](https://documentation.qonversion.io/docs/amazon-s3.md): Send raw data reports directly to your Amazon S3 bucket
- [Amplitude](https://documentation.qonversion.io/docs/amplitude.md): Send in-app subscription and purchases events to Amplitude
- [Analyse experiments](https://documentation.qonversion.io/docs/analyse-experiment.md): Monitor your experiment results with real-time subscription analytics
- [Analytics](https://documentation.qonversion.io/docs/analytics.md): Access in-app subscription analytics in Qonversion dashboards with customizable filters, grouping, and currency conversion to track revenue and subscriber metrics.
- [Analytics Mode](https://documentation.qonversion.io/docs/analytics-mode.md): Implement subscription analytics in 20 minutes without changing your existing in-app purchases flow.
- [Refund Keeper Analytics Overview](https://documentation.qonversion.io/docs/analytics-overview.md): Refund Keeper doesn't just automate refund defense - it gives you full visibility into your refund activity and savings, all in one place.
- [Android 4.+ migration guide](https://documentation.qonversion.io/docs/android-4-migration-guide.md): Historical migration guide for upgrading the Qonversion Android SDK to major version 4.+: instance-based initialization, renamed entities, and updated purchase and entitlement methods.
- [Android 6.+ migration guide](https://documentation.qonversion.io/docs/android-6-migration-guide.md): Historical migration guide for upgrading the Qonversion Android SDK to major version 6.+: renamed public methods, entities, and packages, with a before/after reference table.
- [Android SDK 6.x to 7.x migration guide](https://documentation.qonversion.io/docs/android-7-migration-guide.md): We've upgraded the Google Play Billing Library dependency to version 6 in this release, which has led to major changes in the product and subscription management parts of our SDK. These are described below.
- [Android SDK 7.x to 8.x migration guide](https://documentation.qonversion.io/docs/android-8-migration-guide.md): We've upgraded the Google Play Billing Library dependency to version 7 in this release, leading to several changes in our SDK. These are described below.
- [Android In-App Products Setup](https://documentation.qonversion.io/docs/android-in-app-products.md): Create and configure Android in-app products and subscriptions in Google Play Console, including base plans, offers, pricing, and activation.
- [Android](https://documentation.qonversion.io/docs/android-sdk.md): Install Qonversion Android SDK to implement in-app subscriptions, validate user receipts, get subscription analytics, and third-party integrations.
- [Set up Google Play for Qonversion](https://documentation.qonversion.io/docs/android-store-setup.md): How to create a Google Play service account, grant Qonversion access to the Google Play Developer API, and connect Real-Time Developer Notifications — the prerequisites for processing Android purchases through Qonversion.
- [Android test devices](https://documentation.qonversion.io/docs/android-test-devices.md): Set up Android test devices, emulators, and license test accounts to safely test Google Play in-app purchases and subscriptions.
- [Creating an App in Google Play Console](https://documentation.qonversion.io/docs/app-creation-in-google-play-console.md): Walk through creating and configuring a new app in the Google Play Console before connecting it to Qonversion.
- [Publish your Android App](https://documentation.qonversion.io/docs/app-publication-in-google-play-console.md): If you want to test in-app purchases, your app must be published (either production, alpha or beta channels, ).
- [App-Specific Shared Secret](https://documentation.qonversion.io/docs/app-specific-shared-secret.md): App-Specific Shared Secret is a key to receive receipts for auto-renewable in-app subscriptions. See how to generate the app's shared secret below.
- [App Store Connect API Key](https://documentation.qonversion.io/docs/app-store-connect-api-key.md): How to create an App Store Connect API key and connect it to Qonversion so we can sync your product catalog and read your subscription grace period configuration.
- [App Store Privacy](https://documentation.qonversion.io/docs/app-store-privacy.md): Understand what data is being collected by Qonversion for App Store reporting purposes
- [App Store Promoted Purchases](https://documentation.qonversion.io/docs/app-store-promoted-purchases.md): Promoting Your In-App Purchases on the App Store Page and Search Results
- [App Store Small Business Program](https://documentation.qonversion.io/docs/app-store-small-business-program.md): Set up your App Store Small Business Program details in Qonversion
- [Apple App Store](https://documentation.qonversion.io/docs/apple-app-store.md): Overview of Qonversion's Apple App Store guides: offer codes, App Store privacy, promoted purchases, the Small Business Program, Family Sharing, promotional offers, and migrating from SwiftyStoreKit.
- [Apple Family Sharing](https://documentation.qonversion.io/docs/apple-family-sharing.md): Apple Family Sharing allows a user to share a subscription with up to 5 other family members. Family Sharing can help increase customer engagement and improve retention of your app.
- [Apple Promotional Offers](https://documentation.qonversion.io/docs/apple-promotional-offers.md): Learn how to work with Apple Promotional Offers using Qonversion SDKs
- [Apple Ads Integration](https://documentation.qonversion.io/docs/apple-search-ads.md): Integrate Apple Search Ads attribution with Qonversion to measure in-app subscription revenue at the ad campaign level.
- [Apple Ads](https://documentation.qonversion.io/docs/apple-search-ads-analytics.md): Attribution and analytics dashboard for Apple Ads tracking
- [AppMetrica](https://documentation.qonversion.io/docs/appmetrica.md): Send in-app subscription and purchases events to AppMetrica
- [AppsFlyer](https://documentation.qonversion.io/docs/appsflyer.md): Send Qonversion in-app subscription events to AppsFlyer for accurate revenue tracking of trials, conversions, renewals, and refunds.
- [App Store Offer Codes](https://documentation.qonversion.io/docs/appstore-offer-codes.md): Implement Apple offer code redemption in your app using the Qonversion presentCodeRedemptionSheet API on iOS 14 and later.
- [Asapty](https://documentation.qonversion.io/docs/asapty.md): Send in-app subscription and purchases events to Asapty
- [Awards](https://documentation.qonversion.io/docs/awards.md): Award badge templates showcasing App Store recognition and achievements. These components build trust by highlighting your app's accolades and editorial features.
- [Branch](https://documentation.qonversion.io/docs/branch.md): Send iOS and Android in-app subscription events to Branch with Qonversion.
- [Braze](https://documentation.qonversion.io/docs/braze.md): Automatically send Qonversion in-app subscription and purchase events to Braze for customer engagement, messaging, and analytics.
- [Capacitor](https://documentation.qonversion.io/docs/capacitor.md): Install Qonversion Capacitor Plugin to validate user receipts, and get in-app subscription analytics and third-party integrations.
- [Carousels](https://documentation.qonversion.io/docs/carousels.md): Carousel templates provide swipeable, multi-slide layouts for showcasing content in an engaging, interactive format. Use carousels for onboarding flows, feature highlights, category navigation, and visual galleries.
- [How to check user entitlements](https://documentation.qonversion.io/docs/check-permissions.md): Check a user's entitlements with the checkEntitlements method of the Qonversion SDK to gate access to premium features, read the renewal state, and inspect the Entitlement and Transaction objects.
- [CleverTap](https://documentation.qonversion.io/docs/clevertap.md): Send in-app subscription events to CleverTap to engage and win back your subscribers
- [Cohorts](https://documentation.qonversion.io/docs/cohorts.md): Cohort analytics allows you to see a complete picture of how your subscriptions evolve over their lifetime
- [Components](https://documentation.qonversion.io/docs/components.md): Every screen in the No-Code Builder is made up of components — reusable, modular elements that define structure, content, and behavior.
- [Conditional Logic](https://documentation.qonversion.io/docs/conditional-logic.md): Dynamically change component styles based on device, user properties, product context, and custom variables
- [Cordova](https://documentation.qonversion.io/docs/cordova.md): Install Qonversion Cordova Plugin to validate user receipts, and get in-app subscription analytics and third-party integrations.
- [Cordova 4.+ migration guide](https://documentation.qonversion.io/docs/cordova-4-migration-guide.md): Historical migration guide for upgrading the Qonversion Cordova SDK to major version 4.+: updated initialization, renamed methods, and revised purchase and entitlement APIs.
- [Cordova SDK 4.x to 5.x migration guide](https://documentation.qonversion.io/docs/cordova-5-migration-guide.md): We've upgraded the Google Play Billing Library dependency on Android to version 6 in this release, which has led to major changes in the product and subscription management parts of our SDK. These are described below.
- [Cordova SDK 5.x to 6.x migration guide](https://documentation.qonversion.io/docs/cordova-6-migration-guide.md): We've upgraded the Google Play Billing Library dependency for Android to version 7 in this release, leading to several changes in our SDK. These are described below.
- [Create Products](https://documentation.qonversion.io/docs/create-products.md): Qonversion Product is a cross-platform entity representing products from Apple, Google, Stripe, or Paddle. This mapping helps you provide users with access to premium content after making a purchase.
- [CTA Buttons](https://documentation.qonversion.io/docs/cta-buttons.md): Call-to-action button templates designed to drive conversions. Each template includes a pre-styled button with optional supporting text, icons, and visual effects.
- [Custom Actions](https://documentation.qonversion.io/docs/custom-actions.md): Define your own actions in No-Code screens and handle them in your app code.
- [Custom Proxy Server](https://documentation.qonversion.io/docs/custom-proxy-server-for-sdks.md): Qonversion SDKs support Proxy URL settings. For example, you can use this feature for the following tasks
- [Customer Details](https://documentation.qonversion.io/docs/customer-details.md): This tab contains a wealth of information about your customers and their interactions with your app or subscription business, such as the total amount spent, subscription events, status, and other attributes.
- [Customers](https://documentation.qonversion.io/docs/customers.md): Analyze subscriber cohorts with metrics like active trials, subscriptions, churn rate, and payments for users acquired in a chosen date range.
- [Deferred Purchases](https://documentation.qonversion.io/docs/deferred-purchases.md): Handle deferred and pending in-app purchases caused by SCA confirmation, parental controls, or other interruptions using entitlement update listeners.
- [Displaying No-Codes](https://documentation.qonversion.io/docs/displaying-no-codes.md): First, you need to initialize the SDK. To do this, use the same project key that you use to initialize the Qonversion SDK.
- [How to display products with the Qonversion SDK](https://documentation.qonversion.io/docs/displaying-products.md): Fetch cross-platform Qonversion Products with the SDK, read every field of the Product object, and check a user's trial and introductory offer eligibility on iOS and Android.
- [Edit Entitlements](https://documentation.qonversion.io/docs/edit-entitlements.md): Grant users premium content access manually without a purchase, via the Qonversion dashboard or REST API, for testing, support, or promotions.
- [Enable Refund Keeper](https://documentation.qonversion.io/docs/enable-refund-keeper.md): A short guide on how to Enable Refund Keeper in Qonversion and start saving revenue today.
- [Create Entitlements](https://documentation.qonversion.io/docs/entitlements.md): Learn how to configure and control your app users' access with Qonversion Entitlements.
- [Events](https://documentation.qonversion.io/docs/events-analytics.md): Visualize in-app user actions — trials, subscriptions, renewals, cancellations, and refunds — through the Qonversion Events Chart dashboard.
- [Facebook Ads](https://documentation.qonversion.io/docs/facebook.md): Send in-app subscription and purchases data to Facebook Analytics and Ads Manager
- [Fallbacks](https://documentation.qonversion.io/docs/fallbacks.md): This ensures your No-Code screens remain available even when a network connection is lost or your app cannot reach Qonversion’s servers. Think of it as a backup plan that automatically loads a locally stored version of your screen when the live one can’t be fetched.
- [Feature List](https://documentation.qonversion.io/docs/feature-list.md): Feature list templates for showcasing product benefits, plan comparisons, and value propositions. These components help users understand what they're getting before making a purchase decision.
- [Stop experiments](https://documentation.qonversion.io/docs/finish-experiment.md): Roll your experiment out once you accepted or rejected the hypothesis
- [Firebase](https://documentation.qonversion.io/docs/firebase.md): Send Qonversion revenue events including purchases, trial conversions, subscription renewals, and refunds to Firebase for user behavior tracking.
- [Flutter 5.+ migration guide](https://documentation.qonversion.io/docs/flutter-5-migration-guide.md): Historical migration guide for upgrading the Qonversion Flutter SDK to major version 5.+: updated initialization, renamed methods, and revised purchase and entitlement APIs.
- [Flutter 7.+ migration guide](https://documentation.qonversion.io/docs/flutter-7-migration-guide.md): Historical migration guide for upgrading the Qonversion Flutter SDK to major version 7.+: renamed entities and methods with a before/after reference for updating your integration.
- [Flutter SDK 7.x to 8.x migration guide](https://documentation.qonversion.io/docs/flutter-8-migration-guide.md): We've upgraded the Google Play Billing Library dependency on Android to version 6 in this release, which has led to major changes in the product and subscription management parts of our SDK. These are described below.
- [Flutter SDK 8.x to 9.x migration guide](https://documentation.qonversion.io/docs/flutter-9-migration-guide.md): We've upgraded the Google Play Billing Library dependency for Android to version 7 in this release, leading to several changes in our SDK. These are described below.
- [Flutter](https://documentation.qonversion.io/docs/flutter-sdk.md): Install Qonversion Flutter SDK to validate user receipts, and get in-app subscription analytics and third-party integrations.
- [Creating Screens](https://documentation.qonversion.io/docs/getting-started.md): Once your store connection and SDK setup are complete, you can start designing your first screen inside the Builder. Each screen is made of modular components that you can arrange, style, and connect to your products — visually, with no code.
- [Migrating from Glassfy](https://documentation.qonversion.io/docs/glassfy-migration-guide.md): Step-by-step guide to migrate your in-app subscription infrastructure from Glassfy to Qonversion — store configuration, products and entitlements, Remote Configs, SDK setup, and user-base migration.
- [Google Ads](https://documentation.qonversion.io/docs/google-ads.md): Optimise your Google App campaigns based on Qonversion events
- [Google Cloud Storage](https://documentation.qonversion.io/docs/google-cloud-storage.md): Send raw data reports directly to your Google Cloud storage
- [Google Developer Notifications](https://documentation.qonversion.io/docs/google-developer-notifications.md): Enable Google Real-Time Developer Notifications to speed up event delivery and make Qonversion analytics for Android subscriptions more real-time.
- [Google Play Store](https://documentation.qonversion.io/docs/google-play.md): Welcome to the Google Play Store Resources section. This concise guide provides the technical insights and tools to optimize your Android app's performance. Sell digital products and content in your Android apps with one-time and subscription in-app offers. Qonversion makes implementing Google Play'…
- [Google Play Data Safety](https://documentation.qonversion.io/docs/google-play-data-safety.md): The Data safety section on Google Play is a simple way for you to help people understand what user data your app collects or shares, as well as showcase your app’s key privacy and security practices.
- [Google Play Product Details](https://documentation.qonversion.io/docs/google-play-product-details.md): Google Play products have a deeply nested structure of objects, containing different information. In our Android and Cross-platform SDKs, we have represented several wrapping classes, containing all the information received from Google Play Billing Library. Below are the specifications of those clas…
- [Upgrade and Downgrade in Google](https://documentation.qonversion.io/docs/google-upgrade-downgrade-or-change-subscription.md): When upgrading or downgrading a subscription, you can set the update policy, or how the change affects your subscribers. The following table lists available update policies:
- [Qonversion SDK Errors Details](https://documentation.qonversion.io/docs/handling-errors.md): Here you can find the descriptions of errors that may be returned from the Qonversion SDK. These descriptions are intended to help you troubleshoot any issues quicker.
- [How Qonversion Works](https://documentation.qonversion.io/docs/how-qonversion-works.md): Qonversion provides the complete toolset to build, analyze, and grow your mobile subscription business. There are two modes of using Qonversion:
- [In-App Purchase API Key](https://documentation.qonversion.io/docs/in-app-purchase-api-key.md): How to create an In-App Purchase API key and connect it to Qonversion so we can validate transactions, detect refunds, look up subscription status, and read transaction history.
- [Send Paddle Purchases to Qonversion](https://documentation.qonversion.io/docs/initiate-purchase-paddle.md): Link every Paddle purchase to a Qonversion user — via the web SDK or your server — so Qonversion can grant entitlements and attribute revenue.
- [Send Stripe Purchases to Qonversion](https://documentation.qonversion.io/docs/initiate-purchase-stripe.md): Create a Stripe Checkout Session on your server and report the completed purchase to Qonversion so entitlements and revenue analytics stay in sync.
- [Installing the SDKs](https://documentation.qonversion.io/docs/install-sdk.md): Install the Qonversion SDK for iOS, Android, Flutter, React Native, Unity, Cordova, Capacitor, Web, and macOS platforms.
- [Installation](https://documentation.qonversion.io/docs/installation.md): Connect your app to the Qonversion SDK for the No-Code Builder to handle screen display, product data, analytics, and purchase tracking.
- [Integrations](https://documentation.qonversion.io/docs/integrations-overview.md): Send your in-app subscription data to destinations like AppsFlyer, Amplitude, and other major mobile platforms.
- [iOS 3.+ migration guide](https://documentation.qonversion.io/docs/ios-3-migration-guide.md): Historical migration guide for upgrading the Qonversion iOS SDK to major version 3.+: updated initialization, renamed methods, and revised purchase and entitlement APIs.
- [iOS 5.+ migration guide](https://documentation.qonversion.io/docs/ios-5-migration-guide.md): Historical migration guide for upgrading the Qonversion iOS SDK to major version 5.+: renamed entities and methods with a before/after reference for updating your integration.
- [iOS App Extensions](https://documentation.qonversion.io/docs/ios-app-extensions.md): Learn how to enable data sharing in Qonversion for Apple App Extensions.
- [iOS App-Specific Shared Secret](https://documentation.qonversion.io/docs/ios-app-specific-shared-secret.md): Generate and obtain your app-specific shared secret from App Store Connect to enable Qonversion receipt validation for iOS subscriptions.
- [iOS App Store Info Fields](https://documentation.qonversion.io/docs/ios-app-store-info-fields.md): How to find your Bundle ID, App Store ID, and App-Specific Shared Secret in App Store Connect — the three required fields for connecting your iOS app to Qonversion.
- [Apple Server-to-Server Notifications](https://documentation.qonversion.io/docs/ios-s2s-notifications.md): How to forward Apple's server-to-server notifications to Qonversion so renewal, refund and subscription-status events arrive in real time.
- [iOS](https://documentation.qonversion.io/docs/ios-sdk-setup.md): Install Qonversion iOS SDK to implement in-app subscriptions, validate user receipts, get subscription analytics, and send subscription events to third-party integrations.
- [[Jul 2024] Migration guide. Google Play Billing Library 7.](https://documentation.qonversion.io/docs/jan-2024-migration-guide-google-play-billing-library-6-copy.md): We have released a major update to our Android and cross-platform Qonversion SDKs with new Google Play Billing Library support and several improvements. This article enumerates the steps necessary to migrate from previous SDK versions to the ones displayed in the table below:
- [[Jan 2026] Migration guide. Capacitor 1.](https://documentation.qonversion.io/docs/jan-2026-migration-guide-capacitor-1.md): In this major release of the Qonversion Capacitor Plugin, we've made crucial changes to support No-Codes along with the new purchase method, plugin migration to the Qonversion organization in NPM, and some others.
- [Overview](https://documentation.qonversion.io/docs/jan-2026-migration-guide-cordova-7.md): In this major release of the Qonversion Cordova Plugin, we've made crucial changes to support No-Codes along with the new purchase method, plugin migration to the Qonversion organization in NPM, and some others.
- [[July 2025] Migration guide. Google Play Billing Library 8.](https://documentation.qonversion.io/docs/july-2025-migration-guide-google-play-billing-library-8.md): Google Play has recently launched a new major version of its billing library. We have incorporated all the updates in our latest major Android SDK - version 9. This article outlines the steps required to transition from the previous SDK version to the newest one.
- [Kids Mode](https://documentation.qonversion.io/docs/kids-mode-sdk.md): Easily enable Kids Mode in Qonversion SDK to comply with Apple and Google policies. No IDFA, GAID, or ad data collected.
- [Kochava](https://documentation.qonversion.io/docs/kochava.md): Send iOS and Android in-app subscription events to Kochava with Qonversion.
- [Launch experiments](https://documentation.qonversion.io/docs/launch-experiments.md): Plan, configure, and launch monetisation experiments with flexible A/B testing solution
- [Launch A/B test from Remote Config](https://documentation.qonversion.io/docs/launch-test-from-remote-config.md): Iterate with monetization A/B tests without app releases
- [License testing](https://documentation.qonversion.io/docs/license-testing.md): Set up Gmail license test accounts in Google Play Console to test Android in-app purchases and subscriptions without real charges.
- [Overview](https://documentation.qonversion.io/docs/llmtxt.md): We've added a special file—llms.txt—to help AI tools like ChatGPT, Google Gemini, Claude, and Perplexity better understand and process the content of our website.
- [macOS / Catalyst](https://documentation.qonversion.io/docs/macos-catalyst.md): Qonversion SDK to handle in-app purchases for macOS / Catalyst
- [Mailchimp](https://documentation.qonversion.io/docs/mailchimp.md): Send iOS and Android subscription events to Mailchimp to trigger personalized emails
- [How to make purchases with the Qonversion SDK](https://documentation.qonversion.io/docs/making-purchases.md): Make in-app purchases with the Qonversion SDK: start a purchase, handle the success/cancel/pending/error result, restore purchases, and use Android offers, subscription updates, and iOS multi-quantity options.
- [MCP Server](https://documentation.qonversion.io/docs/mcp-server.md): Connect AI assistants to your Qonversion project data via the Model Context Protocol
- [Migrate Offerings to Remote Configs](https://documentation.qonversion.io/docs/migrate-offerings-to-remote-configs.md): Move your paywall product management from legacy Offerings to Remote Configs
- [[Dec 2022] Migration Guide](https://documentation.qonversion.io/docs/migrate-to-the-actual-qonversion-sdk-version-december-2022.md): We have released a major update for our Qonversion SDK with several new features, improvements, and design fixes. This article provides the necessary steps to migrate from previous SDK versions to the ones displayed in the table below:
- [Migrating from RevenueCat](https://documentation.qonversion.io/docs/migrating-from-revenuecat-to-qonversion.md): We have prepared this guide to help you move your infrastructure seamlessly from RevenueCat to Qonversion. Although this guide is comprehensive and should enable you to transfer the entire infrastructure smoothly, feel free to reach out to support if you have any questions.
- [Migrating In-App Subscriptions](https://documentation.qonversion.io/docs/migrating-subscriptions.md): How to integrate Qonversion with existing subscriber base
- [Mixpanel](https://documentation.qonversion.io/docs/mixpanel.md): Send in-app iOS and Android subscription and purchase events to Mixpanel
- [Monitoring](https://documentation.qonversion.io/docs/monitoring.md): Real-time analytics for your mobile app with in-app subscriptions
- [Lottie Component Source](https://documentation.qonversion.io/docs/no-code-component-lottie-src.md): How to obtain a link for a Lottie animation to use within the Qonversion No-Code Builder.
- [Overview](https://documentation.qonversion.io/docs/no-codes.md): Build, test, and update in-app screens — instantly.
- [Screen Analytics](https://documentation.qonversion.io/docs/no-codes-analytics.md): Track how your no-code screens perform — impressions, conversions, revenue, and more.
- [Non-Subscription Purchases](https://documentation.qonversion.io/docs/non-subscription-purchases.md): Use Qonversion to handle non-consumable and consumable in-app purchases
- [[Nov 2025] Migration guide. iOS 6.0.0](https://documentation.qonversion.io/docs/nov-2025-migration-guide-ios-600.md): In this major release of our Qonversion iOS SDK, we've incorporated numerous essential updates.
- [Offline SDK mode](https://documentation.qonversion.io/docs/offline-sdk-mode.md): Qonversion SDKs work when there is no internet connection on the device, or Qonversion API is inaccessible for a short time. Please take a look at the details of this mode below.
- [OneSignal](https://documentation.qonversion.io/docs/onesignal.md): Send in-app subscription events to OneSignal to win back your subscribers
- [Paddle Credentials](https://documentation.qonversion.io/docs/paddle-credentials.md): Where to get your Paddle API key and where to paste it in the Qonversion dashboard.
- [Paddle Integration](https://documentation.qonversion.io/docs/paddle-integration.md): Connect your Paddle account to Qonversion to manage cross-platform subscribers and provide unified analytics for web payments.
- [Pause experiments](https://documentation.qonversion.io/docs/pause-experiments.md): Pause your experiment to analyse exposed users thoroughly
- [Overview](https://documentation.qonversion.io/docs/paywall-experiments.md): A/B testing to validate your monetization hypothesis for every paywall element from UI to pricing
- [PostHog](https://documentation.qonversion.io/docs/posthog.md): Send in-app subscription and purchases events to PostHog
- [Product Blocks](https://documentation.qonversion.io/docs/product-blocks.md): Product block templates for subscription and purchase selection screens. Each template includes two products (yearly and monthly) with automatic select-product state handling.
- [Product Setup & Store Connection](https://documentation.qonversion.io/docs/product-setup-store-connection-1.md): Connect your in-app products from App Store, Google Play, Stripe, or Paddle so they can be used in the No-Code Builder.
- [Properties Reference](https://documentation.qonversion.io/docs/properties-reference.md): Every component in the No-Code Builder has configurable properties that define how it looks, behaves, and interacts with other elements.
- [Purchase Loader](https://documentation.qonversion.io/docs/purchase-loader.md): Show a custom loader while a purchase is processing, instead of the SDK's default system spinner.
- [Pushwoosh](https://documentation.qonversion.io/docs/pushwoosh.md): Send in-app subscription events to Pushwoosh to win back your subscribers
- [Welcome](https://documentation.qonversion.io/docs/qonversion-platform.md): Developer-focused overview of the Qonversion platform: SDKs, APIs, No-Code Builder, A/B testing, Remote Configs, and integrations.
- [[Aug 2023] Migration Guide](https://documentation.qonversion.io/docs/qonversion-sdk-major-version.md): We have released a major update for our Qonversion SDK with several new features, improvements, and design fixes. This article provides the necessary steps to migrate from previous SDK versions to the ones displayed in the table below:
- [[Jan 2024] Migration guide. Google Play Billing Library 6.](https://documentation.qonversion.io/docs/qonversion-sdk-major-version-copy.md): We have released a major update to our Android and cross-platform Qonversion SDKs with new Google Play Billing Library support, several improvements, and various design fixes. This article enumerates the steps necessary to migrate from previous SDK versions to the ones displayed in the table below:
- [Overview](https://documentation.qonversion.io/docs/quickstart.md): Quick start guide that walks you through setting up Qonversion: choose a mode, create a project, install the SDK, and implement Analytics or Subscription Management Mode.
- [Rate Limits](https://documentation.qonversion.io/docs/rate-limits.md): Our SDKs include rate limit checks for API requests from the following versions. It's aimed at protecting our API from unexpected DoS attacks from SDKs due to unintended usage.
- [Raw Data Export](https://documentation.qonversion.io/docs/raw-data-reports.md): Download your raw data for the specific period, schedule report sending to your Email, Slack channel or Webhook.
- [React Native 4.+ migration guide](https://documentation.qonversion.io/docs/react-native-4-migration-guide.md): Historical migration guide for upgrading the Qonversion React Native SDK to major version 4.+: updated initialization, renamed methods, and revised purchase and entitlement APIs.
- [React Native 6.+ migration guide](https://documentation.qonversion.io/docs/react-native-6-migration-guide.md): Historical migration guide for upgrading the Qonversion React Native SDK to major version 6.+: renamed entities and methods with a before/after reference for updating your integration.
- [React Native SDK 6.x to 7.x migration guide](https://documentation.qonversion.io/docs/react-native-7-migration-guide.md): We've upgraded the Google Play Billing Library dependency on Android to version 6 in this release, which has led to major changes in the product and subscription management parts of our SDK. These are described below.
- [React Native SDK 7.x to 8.x migration guide](https://documentation.qonversion.io/docs/react-native-8-migration-guide.md): We've upgraded the Google Play Billing Library dependency for Android to version 7 in this release, leading to several changes in our SDK. These are described below.
- [React Native](https://documentation.qonversion.io/docs/react-native-sdk.md): Building subscriptions with Qonversion React Native SDK is simple. Learn more about  and  for free now.
- [Refund Keeper](https://documentation.qonversion.io/docs/refund-keeper.md): Stop losing money on refunds with Qonversion Refund Keeper. Automate data sharing with Apple to reduce unjustified refunds and protect your earnings.
- [Create Remote Config](https://documentation.qonversion.io/docs/remote-config.md): Create Remote Configs to manage your onboarding flows, paywall UI, or pricing settings, avoiding extra app releases
- [How targeting and assignment works](https://documentation.qonversion.io/docs/remote-config-targeting.md): The mechanics behind who gets which Remote Config: first-match by priority, deterministic rollout, sticky assignments, re-evaluation, and how user properties and identify interact with targeting
- [Revenue](https://documentation.qonversion.io/docs/revenue.md): Analyze subscription revenue metrics including sales, proceeds, refunds, ARPU, MRR, and ARR in the Qonversion Revenue dashboard.
- [Sample Apps](https://documentation.qonversion.io/docs/sample-apps.md): Explore iOS and Android sample applications demonstrating Qonversion Subscription Management mode and AppsFlyer integration.
- [Scheduled Reports](https://documentation.qonversion.io/docs/scheduled-reports.md): Automate recurring raw-data export of subscription events to cloud storage, email, Slack, or webhooks on a schedule.
- [Screens Preloading](https://documentation.qonversion.io/docs/screens-preloading.md): When showcasing your No-Code screens with Qonversion, there is typically a delay as the content is fetched from our API. This latency can impact user experience, making it crucial to minimize the time it takes for screens to become visible. To address this challenge, we offer a screen preloading fea…
- [Segment](https://documentation.qonversion.io/docs/segment.md): Send in-app revenue events to your Segment account
- [[Sep 2025] Migration guide. React Native 10.](https://documentation.qonversion.io/docs/sep-2025-migration-guide-react-native-10.md): In this major release of the Qonversion React Native SDK, we've made crucial changes to support No-Codes and The New Architecture along with the React 19+ versions.
- [Server Notifications](https://documentation.qonversion.io/docs/server-notifications.md): Server Notifications are notifications sent from supported stores to Qonversion and are configured in the dashboard settings. These notifications contain updates on purchases, cancellations, refunds and conversions so we can ensure we send events promptly.
- [Singular](https://documentation.qonversion.io/docs/singular.md): Send iOS and Android in-app subscription events to Singular with Qonversion
- [Slack](https://documentation.qonversion.io/docs/slack.md): Send Qonversion subscription and in-app purchase events to your Slack workspace through a webhook-based integration.
- [Social Proof](https://documentation.qonversion.io/docs/social-proof.md): Social proof templates help build trust and credibility by showcasing customer testimonials, ratings, and reviews. These components are designed to increase conversion by highlighting positive user experiences.
- [Fixing Russian Federation traffic blocking](https://documentation.qonversion.io/docs/solving-russian-federation-traffic-blocking.md): Resolve Qonversion API access issues in the Russian Federation by configuring a proxy URL during SDK initialization for uninterrupted service.
- [SplitMetrics Acquire](https://documentation.qonversion.io/docs/splitmetrics.md): Send in-app subscription and purchases events to SplitMetrics Acquire
- [Splitting rules](https://documentation.qonversion.io/docs/splitting-rules.md): Launch A/B experiments with the clear picture of what is going on under the hood.
- [Store Product Price Changes](https://documentation.qonversion.io/docs/store-product-price-changes.md): Understand how subscription price changes are handled on the App Store and Google Play, and how they affect existing subscribers and new users.
- [StoreKit testing in Xcode](https://documentation.qonversion.io/docs/storekit-testing-in-xcode.md): Set up and test in-app purchases with a StoreKit Configuration file in Xcode together with Qonversion: create the file, export its public certificate, upload it to the Dashboard, run test purchases, and clear the test data afterwards.
- [Stripe Integration](https://documentation.qonversion.io/docs/stripe-integration.md): Connect your Stripe account to Qonversion to manage cross-platform subscribers and track analytics for web payments.
- [Subscription Management Mode](https://documentation.qonversion.io/docs/subscription-management-mode.md): This guide is for implementing subscription-based access management with Qonversion (Subscription Management mode).
- [Subscriptions](https://documentation.qonversion.io/docs/subscriptions.md): Track active, new, and churned paid subscriptions with analytics on subscription movement and cancellation rates.
- [Success and Failure Actions](https://documentation.qonversion.io/docs/success-failure-actions.md): Configure custom behaviors after purchase or restore actions complete.
- [Migrate from SwiftyStoreKit](https://documentation.qonversion.io/docs/swiftystorekit-alternative.md): Migrate your app from SwiftyStoreKit to Qonversion
- [System Reliability](https://documentation.qonversion.io/docs/system-reliability.md): At Qonversion, reliability has always been our priority. We have multiple protection mechanisms that allow us to avoid any downtimes and provide a reliable in-app subscription management service SLA. These mechanisms can be categorized into three levels:
- [Tenjin](https://documentation.qonversion.io/docs/tenjin.md): Send iOS and Android in-app subscription and purchase events to Tenjin with Qonversion.
- [Test Purchases — Apple](https://documentation.qonversion.io/docs/test-purchase-apple.md): Verify your Apple App Store integration end to end with a sandbox tester account and a test purchase reported to Qonversion.
- [Test Purchases — Google Play](https://documentation.qonversion.io/docs/test-purchase-google.md): Verify your Google Play integration with a license-tester test purchase and confirm the transaction reaches your Qonversion dashboard.
- [Test Purchases — Paddle](https://documentation.qonversion.io/docs/test-purchase-paddle.md): Verify your Paddle integration with a sandbox test purchase — Paddle keeps Production and Sandbox fully separate, so testing runs against the Paddle sandbox environment.
- [Test Purchases — Stripe](https://documentation.qonversion.io/docs/test-purchase-stripe.md): Verify your Stripe integration with a test-mode purchase using Stripe test cards and confirm it reaches your Qonversion dashboard.
- [Overview](https://documentation.qonversion.io/docs/testing.md): Test in-app purchases and subscriptions after implementing Qonversion SDKs
- [Restore behavior](https://documentation.qonversion.io/docs/transferring.md): Two available behaviors exist for reassigning the same subscription to different users:
- [Trials](https://documentation.qonversion.io/docs/trials.md): Qonversion provides in-depth analytics of your in-app trial offers
- [Troubleshooting](https://documentation.qonversion.io/docs/troubleshooting.md): Solutions to common Qonversion SDK and dashboard errors: product-not-found, receipt validation, store credentials, StoreDetails, billing, and Google RTDN issues.
- [Troubleshooting - Active store not found](https://documentation.qonversion.io/docs/troubleshooting-active-store-not-found.md)
- [Troubleshooting - Invalid access token received](https://documentation.qonversion.io/docs/troubleshooting-invalid-access-token-received.md)
- [Troubleshooting - Invalid Store Credentials Error](https://documentation.qonversion.io/docs/troubleshooting-invalid-store-credentials-error.md): Fix invalid store credentials errors by verifying your iOS shared secret and Android service account permissions in Google Play Console.
- [Tutorials](https://documentation.qonversion.io/docs/tutorials.md): Watch video tutorials for implementing in-app purchases and subscriptions with Qonversion on iOS, Android, Flutter, and more.
- [Unity 4.+ migration guide](https://documentation.qonversion.io/docs/unity-4-migration-guide.md): Historical migration guide for upgrading the Qonversion Unity SDK to major version 4.+: updated initialization, renamed methods, and revised purchase and entitlement APIs.
- [Unity 6.+ migration guide](https://documentation.qonversion.io/docs/unity-6-migration-guide.md): Historical migration guide for upgrading the Qonversion Unity SDK to major version 6.+: renamed entities and methods with a before/after reference for updating your integration.
- [Unity SDK 6.x to 7.x migration guide](https://documentation.qonversion.io/docs/unity-7-migration-guide.md): We've upgraded the Google Play Billing Library dependency on Android to version 6 in this release, which has led to major changes in the product and subscription management parts of our SDK. These are described below.
- [Unity SDK 7.x to 8.x migration guide](https://documentation.qonversion.io/docs/unity-8-migration-guide.md): We've upgraded the Google Play Billing Library dependency for Android to version 7 in this release, leading to several changes in our SDK. These are described below.
- [Unity](https://documentation.qonversion.io/docs/unity-sdk.md): Install Unity SDK to validate user receipts, get in-app subscription analytics, and 3-rd party integrations.
- [Upgrade and Downgrade a Subscription](https://documentation.qonversion.io/docs/upgrade-and-downgrade-a-subscription.md): Let users upgrade, downgrade, or crossgrade between subscriptions on iOS and Android using ranking levels and proration update policies.
- [User Identifiers](https://documentation.qonversion.io/docs/user-identifiers.md): Share your User ID with Qonversion to manage user access on various devices and platforms.
- [User Properties](https://documentation.qonversion.io/docs/user-properties.md): Set and retrieve custom and predefined user attributes for segmentation, analytics, and third-party platform integrations.
- [New users](https://documentation.qonversion.io/docs/users.md): View analytics on new user acquisition, trial conversion rates, and paid subscription conversion by install cohort.
- [Users and Access](https://documentation.qonversion.io/docs/users-and-access.md): Users and Access section to manage the team roles in your Qonversion project.
- [Using No-Codes with custom purchases handling](https://documentation.qonversion.io/docs/using-no-codes-with-custom-purchases-handling.md): By default, Qonversion No-Codes utilize the Qonversion SDK for managing purchases. This implies that you should operate Qonversion in subscription management mode. However, if you have your own purchasing infrastructure, you can manage purchases and restores from No-Code screens on your end. It’s as…
- [Variables](https://documentation.qonversion.io/docs/variables-1.md): Variables let you display dynamic product data — such as price, currency, and trial period — directly inside your paywall or onboarding screen.
- [watchOS/visionOS](https://documentation.qonversion.io/docs/watchosvisionos.md): Install Qonversion SDK to implement in-app subscriptions, validate user receipts, get subscription analytics, and send subscription events to third-party integrations.
- [Web 1.+ migration guide](https://documentation.qonversion.io/docs/web-1-migration-guide.md): Historical migration guide for upgrading the Qonversion Web SDK to major version 1.+: updated initialization, renamed methods, and revised purchase and entitlement APIs.
- [Web Funnel — Sell subscriptions on the web](https://documentation.qonversion.io/docs/web-funnel.md): Build a web checkout funnel with the No-Code Builder and let users pay on the web (Stripe) and unlock the subscription in your mobile app.
- [Web Funnel — Redeem web purchases in your app](https://documentation.qonversion.io/docs/web-funnel-redemption.md): Let users who purchased on your web funnel unlock the subscription inside your mobile app via a redemption deep link. Grant-first: the entitlement is already granted server-side; the SDK just refreshes it.
- [Web SDK](https://documentation.qonversion.io/docs/web-sdk.md): Send Web purchases data to manage cross-platform user access: Web, iOS, Android.
- [Webhooks](https://documentation.qonversion.io/docs/webhooks.md): Send in-app subscription and purchase events to your server with webhooks
- [API v3 (legacy)](https://documentation.qonversion.io/reference/overview.md): Legacy: the v3 REST API is superseded by API v4. This page summarizes v3 concepts, authentication keys, and a resource-to-v4 mapping for existing integrations. New integrations should use v4.
- [Analytics](https://documentation.qonversion.io/reference/v4/analytics.md): Expose Qonversion dashboard data via the v4 API: charts, KPIs, cohorts, LTV curves, and AI-written narrative insights.
- [Authentication](https://documentation.qonversion.io/reference/v4/authentication.md): How to authenticate with the Qonversion REST API v4
- [Automations](https://documentation.qonversion.io/reference/v4/automations.md): Deprecated: the Automations product surface has been removed from Qonversion. The API remains available for existing integrations only. Event-driven automations that fire push notifications or show screens in response to user events.
- [Customers](https://documentation.qonversion.io/reference/v4/customers.md): Aggregated customer records, properties, permissions, and metrics
- [Entitlements](https://documentation.qonversion.io/reference/v4/entitlements.md): Create entitlement definitions and grant or revoke user access
- [Events](https://documentation.qonversion.io/reference/v4/events.md): Browse the catalog of event types Qonversion tracks for use in custom dashboards, automations, and external integrations.
- [Experiments](https://documentation.qonversion.io/reference/v4/experiments.md): Paywall and offering experiments, groups, and user assignment
- [Exports](https://documentation.qonversion.io/reference/v4/exports.md): Asynchronous data exports (customers, events, purchases)
- [Handling Errors](https://documentation.qonversion.io/reference/v4/handling-api-errors.md): HTTP response codes and error format for the Qonversion REST API v4
- [Identities](https://documentation.qonversion.io/reference/v4/identities.md): Link Qonversion users to your own authentication system
- [Integrations](https://documentation.qonversion.io/reference/v4/integrations.md): Configure third-party integrations with marketing, analytics, attribution, and messaging platforms through the v4 API.
- [Offerings](https://documentation.qonversion.io/reference/v4/offerings.md): Legacy: Offerings are superseded by Remote Configs. Bundles of products shown to users in paywalls; kept available for existing integrations. Migrate new work to Remote Configs.
- [Overview](https://documentation.qonversion.io/reference/v4/overview.md): The Qonversion REST API v4 consolidates customer, analytics, experiment, segment, and integration management with an agent-first design.
- [Products](https://documentation.qonversion.io/reference/v4/products.md): Manage products configured in the Qonversion dashboard
- [Project Settings](https://documentation.qonversion.io/reference/v4/project-settings.md): Project-level configuration, secret, and store credentials
- [Purchases](https://documentation.qonversion.io/reference/v4/purchases.md): Retrieve a user transaction history from the App Store, Play Store, and Stripe for subscriptions and one-time purchases.
- [Remote Configurations](https://documentation.qonversion.io/reference/v4/remote-configurations.md): Server-driven configuration payloads delivered to the SDK
- [Scheduled Reports](https://documentation.qonversion.io/reference/v4/scheduled-reports.md): Recurring analytics reports sent to external destinations
- [Screens](https://documentation.qonversion.io/reference/v4/screens.md): Deprecated: the Screens product surface has been removed from Qonversion. The API remains available for existing integrations only. No-code paywall screens — CRUD, publish, duplicate, and analytics.
- [Segments](https://documentation.qonversion.io/reference/v4/segments.md): Create rule-based user segments from properties and purchase history for targeting experiments, reports, and remote configs.
- [User Properties](https://documentation.qonversion.io/reference/v4/user-properties.md): Manage user-level attributes for segmentation and analytics
- [Users](https://documentation.qonversion.io/reference/v4/users.md): Retrieve Qonversion users and manage their properties, purchases, and entitlements

## OpenAPI Specs

- [rest-api-v4](https://documentation.qonversion.io/api-reference/rest-api-v4.yaml)
- [rest-api](https://documentation.qonversion.io/api-reference/rest-api.yaml)
- [analytics-api](https://documentation.qonversion.io/api-reference/analytics-api.yaml)
- [openapi](https://documentation.qonversion.io/api-reference/openapi.json)