Documentation

Conversions and postbacks

Updated 17 Nov 2026

The affiliate network calls /postback/<network key> with the click id. Approved, pending, rejected, refunded, and trash are the stored statuses. A click can only be booked by the network that owns the offer it was sent to.

The URL you give the network

Each network has a key. The admin’s default postback URL, when you have not set a custom template, is:

https://<default-domain>/postback/<network key>?cid={click_id}&payout={payout}&txn_id={transaction_id}&status={status}

The handler accepts GET and POST. The click id may be named click_id, cid, clickid, or subid. Payout may be payout, amount, or revenue. The transaction id may be txn_id, transaction_id, or order_id. You can also send goal. If goal is omitted, the offer’s default goal is used, or sale.

An optional signature is the header X-Velotrak-Signature: HMAC-SHA256 of the sorted key=value pairs, using the network key as the secret. A wrong or unknown network key is 401.

Statuses

Stored statuses are approved, pending, rejected, refunded, and trash. Common aliases: sale becomes approved, lead becomes pending, reject and declined become rejected, chargeback and refund become refunded. An unknown status is booked as pending and flagged as a status anomaly.

A missing or invalid click id is not booked. A postback whose network is not the network of the click’s offer returns 403 with network_mismatch and is not booked. That includes a second network record you created for the same company, and it includes clicks that happened before you moved the offer. A status change the ledger does not allow returns 200 with ignored.

Reports treat approved payout as revenue, pending as pending revenue, and trash as trash revenue. Amount, currency, and excess anomalies can force an approved postback down to pending.

Browser pixel

GET or POST /track is the endpoint used by /velotrak.js. It reads click_id or the vt_cid cookie. The default goal is lead. The pixel inserts a conversion; it does not change an existing status. A click accepts at most 10 pixel conversions.

What you send back to the source

When a conversion is booked, an outbox job calls the traffic source’s postback URL template. Delivery retries are visible in the outbound log, next to CAPI rows. CAPI itself runs only for an approved conversion with no anomaly. Setup for Meta, TikTok, and Google is the CAPI page.