Integration guide

For advertisers — incoming postback

When you're approved as an advertiser, we'll give you two things:

• A click ID macro embedded in the landing-page URL we redirect users to. Most commonly this looks like ?aff_click_id={clickid} or ?cid={clickid}. Whatever the parameter name, capture and store it server-side keyed to the user.
• A postback URL like:

copy
https://tracksn.com/postback?clickid={CLICK_ID}&event={EVENT}&payout={PAYOUT}&txid={USER_ID}&status=approved&secret=YOUR_SECRET

Substitute {CLICK_ID} with the value you stored, {EVENT} with the conversion type, and so on. All other braces stay literal.

Postback parameters

Examples

Signup conversion (lead, $5 payout):

copyGET https://tracksn.com/postback?clickid=ad933e25...&event=signup&payout=5&txid=user_4821&secret=YOUR_SECRET

Deposit conversion (same user, paid commission $50):

copyGET https://tracksn.com/postback?clickid=ad933e25...&event=deposit&payout=50&txid=user_4821&secret=YOUR_SECRET

Response

{
  "ok": true,
  "clickid": "ad933e25...",
  "status": "approved",
  "payout": 50,
  "outgoing_postback": {
    "url": "https://affiliate.example.com/pb?...",
    "status": 200
  }
}

HTTP 200 with "ok": true means the conversion was recorded. HTTP 401 means a wrong/missing secret. HTTP 404 means the clickid doesn't exist (most often: testing without an actual prior click).

For affiliates — tracking links + outgoing postback

You receive two things from us:

• A click URL to send your traffic to.
• A postback URL we'll fire when one of your users converts. You define this URL when you onboard; we substitute macros into it on every conversion.

Click URL

copyhttps://tracksn.com/c?offer={offer_id}&aff={your_aff_id}&pubid={pubid}&subid={subid}

Replace {pubid} and {subid} with your traffic-source macros (Meta's {{campaign_id}}, Google's {campaignid}, TikTok's __CID__, etc.). We don't care about the exact format — whatever string you pass is stored as-is and echoed back to your postback.

Click URL behavior:

• We generate a unique clickid, store the click (IP, geo, device, OS, browser, referer, timestamp), and 302-redirect the user to the offer's landing page with the clickid macro substituted in.
• The redirect typically completes in under 100ms.
• You can also use /i.gif?offer=...&aff=...&pubid=...&subid=... as a 1×1 transparent pixel for view-through impression tracking.

Outgoing postback

When the advertiser confirms a conversion for one of your clicks, we fire a single GET to your configured postback URL. We replace any {macro} tokens with real values:

Example postback URL you'd give us:

copyhttps://your-network.com/postback?clickid={subid}&payout={payout}&status={status}&event={event}

(Yes — you typically pass our {subid} back as your "clickid" because that's where you put your own click identifier when you generated the click URL. Do whatever matches your stack.)

All macros, in one place

Macros use {name} syntax (lowercase, alphanumeric). Unknown macros are left as-is so they're easy to spot in logs. Values are URL-encoded automatically when substituted.

Endpoints reference

Questions?

Email oshri1amsalem@gmail.com or reply to the thread you got onboarded through.