Overview
DARO sends an HTTP/HTTPS GET request to your server when users complete rewarded video ads. Callbacks send immediately after completion but may delay up to several minutes depending on network conditions. Use the timestamp parameter to verify time difference between impression and callback. Retry Logic: DARO retries up to 2 times if your server doesn’t respond within 5 seconds.
Callback URL Example
Callback URL Request Example
Query Parameters
Parameters included as query strings in callback URL. Optional parameters (custom_data and user_id) pass as null if not set.
| Query Parameter | Description | Example | Data Type |
|---|---|---|---|
| ad_unit_id | Mediation ad unit ID (UUID v4) | fa1c6d2f-5016-467d-b54c-672299c7db4c | String |
| custom_data (optional) | Custom data (URL encoded). Recommended to keep string size under 8192 characters. | my%20custom%20data | String |
| key | Verification key generated through the following process: 1. Initialize HMAC SHA256 with ‘Callback Verification Key’* 2. Generate digest with transaction_id 3. Hex encode | b46635e51e76778ec15856720114c4edd6b6c3c7aeeb2a1b51dc346640cbca45 | String |
| timestamp | Timestamp when ad was loaded (integer, Epoch Time) | 1546300800 | Int |
| transaction_id | Unique transaction ID, 32-character hex | 0d0f748fcd0d4a4a9f6ac809216564b1 | String |
| user_id (optional) | Publisher-defined user ID (URL encoded); maximum length 8192 characters | 7634657898 | String |
- Find your callback verification key at https://dashboard.daro.so/service/account
Set Publisher-Defined User ID and Custom Data
Setuser_id and custom_data on the client side using platform-specific SDK methods. These optional values send with the callback.
Platform Guides:

