Skip to main content
A Customer is the v4 aggregated view of a user: their identifiers, properties, permissions, and lifetime metrics. Customer endpoints are intended for dashboards and server-side flows that need a consolidated picture — most client SDK flows should continue to use the User APIs.

​
Key concepts

  • Customer ID — The canonical ID for the customer (equivalent to the Qonversion User ID).
  • Permissions — Access rights granted to the customer (granular alternative to entitlements).
  • Properties — Same key–value model as user properties, but aggregated per customer.
  • Metrics — Aggregated counters (total customers, active subscriptions, churn, etc.) exposed via /v4/customers/metrics.
  • GDPR delete — DELETE /v4/customers/{customer_id} permanently removes all data for a customer.

​
Available endpoints

MethodEndpointDescriptionStatus
GET/customersList customersNew
GET/customers/metricsGet customer metricsNew
DELETE/customers/{customer_id}Delete a customer (GDPR)New
GET/customers/{customer_id}Get a customerNew
GET/customers/{customer_id}/permissionsList customer permissionsNew
POST/customers/{customer_id}/permissionsGrant a permission to a customerNew
DELETE/customers/{customer_id}/permissions/{permission_id}Revoke a customer permissionNew
POST/customers/{customer_id}/propertiesSet customer propertiesNew

​
Authentication

All v4 endpoints require a Secret Key. Deleting a customer (GDPR) and granting or revoking permissions are privileged operations in the manifest sense, but the token type is the same as for reads. See Authentication.