Webhooks

You can use Webhooks to notify your server anytime an event happens.

Qonversion Webhooks send real-time data to your HTTP endpoints. You can monitor user subscription events and react immediately. For example, you can monitor when your users cancel their subscription and offer them a discount using email.

Setting up webhook URL

To set up Webhooks, go to Integrations ➡ Webhooks.

Register your URL and Qonversion will send a request. If the endpoint server returns a 200 response code, the integration is activated.

Request Format

Qonversion sends POST request to webhook URL every time an event occurs. The request header contains Authorization-Token Value as Basic authorization field. Use that to protect your server from unwanted requests.

Request Header:

Authorization: Basic {Header Authorization-Token}
Accept: application/json

Request Body:

{
   "event_name": "trial_converted",
   "user_id": "3YjIDEUDaf_5g4IdWw6zcMlLgfg_YQp2",
   "custom_user_id": "",
   "advertiser_id": "9FD1767D-8B48-45BD-A2F4-1C08B08E56F2",
   "time": 1560641088,
   "product_id": "com.myapp.subs.9.99.trial",
   "revenue": {
      "value": 7.99,
      "currency": "EUR",
      "value_usd": 9.99
   },
   "properties": {
      "_q_email": "[e-mail]"
   },
   "device_id": "0E66565D-4F3A-E366-B3D4-B5DDAC6BBE2E"
}

Column	Required	Description
event_name	yes	Event name provided in the integration config. More about the events tracked read here
user_id	yes	Qonversion unique user identifier
custom_user_id	yes	Unique user identifier provided by SDK
advertiser_id	yes	IDFA or AAID
time	yes	The time App Store or Google Play charged the user's account or Qonversion detected event, in the UNIX epoch time format, in seconds. Read more about event time here
product_id	yes	App Store or Google Play product identifier
revenue	no	Dictionary with transaction revenue details. Only events with value contain that field. More about tracked events read here.
properties	yes	User properties provided by SDK. Read more about properties here
device_id	yes	identifierForVendor or Settings Secure Android ID

Retries between Qonversion and Destination Server

Qonversion increases deliverability to your server with retries. Retries happen automatically if your server is not responding. This substantially improves data delivery rate.

Qonversion internal systems retry failed destination calls for 24 hours with an increasing backoff after each attempt. This is how retries are scheduled if your server is unavailable:

Attempt	Delay
1	Immediately
2	5 minutes
3	4 hours
4	8 hours
5	24 hours