Browse documentation

Postback & tracking URLs

Developer quick reference for the endpoints on your tracking domain — clicks, server-side clicks, S2S postbacks, pixels, impressions and the SDK endpoint — with their key parameters and answers.

Last updated October 12, 20263 min read

On this page

Server-to-server postback
Pixels
Server-side click
Click links
Outgoing partner postbacks

Tracking runs on your tracking domain (https://trackcrown.com), not on the REST API. This page is the developer's quick reference; the full guides are Affiliate tracking links, Server-to-server postback reference and Postback macros.

Endpoint	Purpose	Answer
`GET/HEAD/POST /c/{link_key}`	Transparent click (Google Ads tracking templates)	`302` to `url=`
`GET/HEAD/POST /r/{offer}/{affiliate}`	Partner tracking link	`302` to the offer (or `url=` when present)
`GET/HEAD/POST /click?oid=&aid=`	Partner link, query form	as `/r/`
`GET/HEAD/POST /s/{smart_link}`	Smart link	`302` to the chosen offer (or `url=`)
`GET/POST /clk`	Server-side click, no redirect	JSON
`GET /i/{offer}/{affiliate}`	Impression pixel	1×1 GIF
`GET/POST /pb` (also `/postback`, `/conversion`)	Server-to-server conversion	JSON
`GET /px`, `/px.gif`	Conversion image pixel	1×1 GIF
`GET /px.js`	Conversion pixel as a script	JavaScript
`POST /lp`	Landing-page SDK endpoint	JSON — see SDK reference
`GET /sdk.js`	Landing-page SDK	JavaScript

Server-to-server postback#

URL

https://trackcrown.com/pb?click_id={click_id}&event=sale&amount=49.90&txid=ORDER-1001&currency=USD&token=TOKEN

Parameter	Description
`click_id` (`transaction_id`, `tid`)	The click ID. Or identify the click with `gclid`, `gbraid`, `wbraid` or `msclkid` — the latest click of the workspace with that ID is used.
`token`	Required. The workspace postback token, or the postback token of the offer's advertiser.
`event`	Event code; default `default`.
`amount` (`sale_amount`)	Sale amount, for percentage payouts and revenue.
`revenue`, `payout`	Override the resolved amounts (`payout` only with the workspace token).
`txid` (`adv_txid`, `order_id`)	Advertiser order ID, used for de-duplication and status updates.
`status`	`approved`, `pending` or `rejected`.
`currency`	ISO code; other currencies are converted with the daily ECB rate.
`offer_id` (`offer`), `aff_id` (`affiliate_id`, `aff`)	Needed only when there is no click ID.
`adv1` … `adv5`	Free values stored with the conversion.
`email`, `em`, `phone`, `ph`	For e-mail attribution and the conversion APIs (hashed before sending).
`coupon_code` (`coupon`)	Coupon attribution.
`conversion_id`	Update an existing conversion (status, money).
`first_click_id`	First-touch attribution.
`test=1`	Validate and answer without storing.

Answers are 200 with {"ok":true,"conversion_id":"…","status":"approved"} or {"ok":false,"error":"…"} (so advertiser systems do not retry duplicates), 401 for a missing or wrong token and 400 for a malformed request. A postback that targets an existing conversion (by conversion_id, by txid on the same offer, or by click ID + event) updates it and answers {"ok":true,"updated":true,…}.

Pixels#

HTML

<img src="https://trackcrown.com/px?offer_id=OFFERCODE&event=sale&amount=49.90&txid=ORDER-1001" width="1" height="1" alt="" />

/px takes the same parameters as /pb without token. Pixel conversions are accepted only when the offer's conversion method is any or pixel. The click ID comes from the parameter, or from the first-party atk_cid cookie on the tracking domain when the workspace sets that cookie at click time. /px.gif is an alias for placements that require a .gif URL; /px.js returns a script that fires the pixel.

Server-side click#

For flows where the visitor never passes your tracking domain:

URL

https://trackcrown.com/clk?oid=OFFERCODE&affid=AFFCODE&token=TOKEN&sub1=abc&ip=203.0.113.7&user_agent=Mozilla%2F5.0…

JSON

{ "transaction_id": "0192a6c3f1e04b7e9c2d8a1f3b5c7d9e", "offer_id": 12, "affiliate_id": 7, "error_code": 0 }

error_code: 0 ok · 1 invalid token · 2 unknown offer · 3 unknown affiliate · 4 offer not active · 5 affiliate not approved · 6 targeting · 7 click cap · 8 workspace not active. Use transaction_id as the click ID in later postbacks.

Click links#

All click paths accept sub IDs (sub1–sub10, source_id and aliases), ad-platform click IDs and ValueTrack values, mapped as in the ValueTrack reference. With url=, every click path is transparent: one 302 to exactly that URL, refused with 403 when the host is not allowed. See Transparency & certification.

Outgoing partner postbacks#

Partners receive conversions through the postback URLs they (or you) configure, with macros such as {click_id}, {payout}, {sub1} and {status} expanded. Manage them in the panel, the partner portal or /api/v1/postbacks (API reference). Every delivery is in the postback log.

Every refusal and error code of these endpoints is listed in Error and reason codes.

Something unclear or missing in this article?Tell us