Connecting your tracking link

How it works Concept

Every offer + affiliate pair has its own unique tracking link:

https://smthprj.xyz/t/<slug>

When someone opens that link:

1. The server records a click and generates a unique click_id, along with IP, user-agent, and referer.
2. The link's click count increases by one — visible immediately to both the partner and the affiliate.
3. The visitor is 302-redirected to the offer's destination URL, with these params appended: ?click_id=...&offer_id=...&affiliate_id=...

Later, when a real conversion happens on the partner's site (a sale, lead, signup), the partner's site must send a postback — a server-side request carrying that same click_id plus the partner's api_key — so the conversion is authenticated and credited to the right affiliate.

Getting your link

A link only exists once an offer is live and an affiliate has been approved on it. The full lifecycle:

Where to place it

Treat it like a normal URL — it doesn't point straight at the partner's site, it routes through the tracking domain smthprj.xyz, which redirects (302) instantly to the real landing page. This adds no noticeable delay for the visitor.

• Use it directly in ads, posts, newsletters, bio links — same as any URL.
• You can append your own UTM parameters; they pass through to the landing page alongside click_id.
• Avoid placing it where a link preview is fetched automatically without a real visit (some messaging apps) — most don't trigger a real click, but verify on a specific channel before a large campaign.

How a click is counted

A click is recorded the moment a GET request hits /t/<slug> — i.e. at the moment of the redirect itself, before the visitor even sees the partner's site. One visit = one click.

Attribution window Cookie days

Each offer has a configurable attribution period — Cookie days (30 days by default, set when the offer is created). A postback sent with a valid click_id is credited regardless of how it was generated — attribution is based on the click_id itself, not a cookie in the visitor's browser.

Setting up a postback

A postback is a server-to-server request your site, CRM, or checkout sends to us at the moment of conversion. The base template a partner sees and copies from Settings → Global postback URL:

https://somethingproject.com/api/postback?api_key={api_key}&click_id={click_id}&status={status}&amount={amount}&commission={commission}

Replace {click_id}, {status}, etc. with the actual macros from your platform (Keitaro, a landing page builder, your own backend), or with real values if you're calling it directly from code.

Postback parameters

Both GET and POST are supported. Parameter names are read identically from the query string or the request body.

Conversion statuses & earnings

The status you send determines whether the conversion contributes to an affiliate's earned balance:

Every conversion you send still appears in the partner's Conversions list and in the total/pending counters regardless of status — but only confirmed/approved/paid roll up into the affiliate's earned commission.

Integration examples

Direct call from your backend (Node.js)

await fetch(
  "https://somethingproject.com/api/postback" +
  "?api_key=" + SOMETHING_API_KEY +   // from Settings → API & Webhooks
  "&click_id=" + clickId +
  "&status=confirmed" +
  "&amount=" + orderAmount +
  "&commission=" + commissionAmount +
  "¤cy=USD"
);

// Or pass the key as a header instead of a query param:
await fetch("https://somethingproject.com/api/postback?click_id=" + clickId + "&status=confirmed", {
  method: "POST",
  headers: { "X-API-Key": SOMETHING_API_KEY },
});

cURL (for testing or a server script)

curl "https://somethingproject.com/api/postback?api_key=sp_live_xxx&click_id=clk_xxx&status=confirmed&amount=99&commission=10"

Webhook from a payment provider / CRM

If your payment provider or CRM supports outgoing webhooks on payment, point it at the same URL with the real click_id substituted in. You'll need to persist that click_id on your side at the moment the visitor lands (e.g. a hidden form field or localStorage) and carry it through to the order.

Test your setup Recommended

https://somethingproject.com/api/postback?api_key=YOUR_API_KEY&click_id=YOUR_CLICK_ID&status=confirmed&amount=10&commission=1

Troubleshooting