Postback Configuration (S2S)
Server-to-Server (Postback) callbacks allow your system to receive reward notifications directly from the offerwall via HTTP requests. When a user successfully completes an offer and earns a reward, TarGo sends an HTTP GET request to your configured postback URL
Parameter Configuration
| Parameter | Format | Description |
|---|---|---|
{user_id} | String / Integer | The unique user identifier you passed to the offerwall (USER_ID). Used to credit the correct user in your system. |
{tx_id} | String | Unique transaction ID for the reward event. Used to prevent duplicate credits. |
{reward} | Float | The amount of virtual currency you should credit to the user (after applying your multiplier). |
{payout} | Float (USD) | The conversion is in USD. This amount will be credited to your account balance |
{status} | Integer | Event status: 1 = Approved, 2 = Reversed / Chargeback (if fraud or invalid). |
| {offer_name} | string | Name of the offer |
| {offer_id} | string | ID of the offer |
{event_id} | String / Integer | Offer or survey internal event ID. Useful for tracking specific events. |
{event_name} | String | Name of the completed event |
{ip} | IP Address | IP address of the user at the moment of completion. Useful for fraud analysis. |
{country_code} | ISO-3166 Code | User's country code |
{timestamp} | Unix Timestamp | The UNIX timestamp (in seconds) representing when the user initially clicked the offer. |
{sub1} | String | Your sub1 value passed in offerwall link |
{sub2} | String | Your sub2 value passed in offerwall link |
*We automatically add *&hash={hash}
to all postback URLs. If you want to verify the request and ensure security, please validate thehash**parameter.
Response
Our system considers a postback successfully processed only if your server responds with HTTP status code 200 and the response body contains either1** or**OK.
Any other response will be treated as a failed postback. If a postback fails, our system will automatically retry sending it once every 6 hours, up to a maximum of 5 retries per postback.
After 5 failed attempts, the system will stop retrying, and you must contact your account manager to resend all failed postbacks manually.
Last updated 4 weeks ago
Built with Documentation.AI