Skip to main content
User properties are key–value attributes attached to a Qonversion user. They power segmentation, personalisation of no-code screens, and analytics. Qonversion-defined keys start with the _q_ prefix (e.g., _q_email, _q_custom_user_id).

​
Key concepts

  • Custom keys — Any string identifier you choose. Value is stored as a string.
  • System keys — Reserved keys prefixed with _q_ (e.g., _q_email, _q_app_version).
  • Upsert — POST replaces the value if the key already exists for the user.
  • Validation — Invalid rows in a batch are reported per-key; valid rows are applied.

​
Available endpoints

MethodEndpointDescriptionStatus
GET/users/{user_id}/propertiesList properties for a userUpdated — v3
POST/users/{user_id}/propertiesSet (upsert) properties for a userUpdated — v3

​
Authentication

All v4 endpoints require a Secret Key. See Authentication.