Routy

Partner postbacks

A partner postback tells a partner's own tracker (Voluum, Bemob, Binom, Keitaro…) that one of their clicks converted. Each time a conversion of the chosen type comes in for that partner, Routy calls the URL you set here, so the partner sees the conversion in their own tool without logging in to Routy.

Postback URL

Paste the postback URL the partner's tracker gives them, then swap the parts the tracker wants filled in for placeholders. A placeholder is a name wrapped in ${…}. Type $ in the field to pick one from the list. On every conversion Routy replaces each placeholder with that conversion's value before calling the URL.

https://tracker.example.com/postback?cid=${externalClickId}&payout=${eventValue}

is called as

https://tracker.example.com/postback?cid=abc123&payout=25.5

The name on the left of = belongs to the tracker. Keep whatever their instructions say (cid, clickid, subid…). Only the placeholder on the right comes from Routy.

Which click ID?

This is the one most often set up wrong. Three names look alike and mean different things:

Name What it is Where you see it
cid The parameter a tracker adds to your tracking link to pass its own click ID in to Routy On the tracking link: …?cid=abc123
${externalClickId} That same click ID, sent back out In the postback URL
${clickId} Routy's own ID for the click, a long code like a1b2c3d4-e5f6-… In the postback URL

A partner's tracker almost always wants its own click ID back, because that's how it matches the conversion to the click. So the usual setup is:

  • the partner's tracker sends clicks to the tracking link with cid=<its click ID>;
  • the postback URL sends it back with ${externalClickId}.

Use ${clickId} only when the partner asks for Routy's click ID. A tracker that gets ${clickId} receives an ID it has never seen and can't match the conversion.

There is no ${cid} placeholder. cid is the name of a parameter on the link, not a value Routy can send, so ${cid} is sent empty.

Conversion type

Each postback fires for one conversion type, for example FTD. If the partner wants to hear about more than one type, add a postback for each. Only conversion types that can be sent as postbacks are listed.

Editing and deleting

Use the pencil on a postback to change its URL or conversion type. A partner can have only one postback per conversion type, so if another of their postbacks already uses the type you pick, the save is refused: change or delete that one first.

Use the bin to delete a postback. It stops firing straight away and there is no undo. Its conversion type is then free for a new postback.

Placeholders

Names aren't case-sensitive, values are URL-encoded for you, and a misspelt name is sent empty without an error. The form warns you when a name isn't on these lists.

Conversion

Placeholder Value Example
${clickId} Routy's click ID a1b2c3d4-e5f6-7890-abcd-ef1234567890
${externalClickId} The click ID the partner's tracker passed in cid on the tracking link abc123
${eventName} The conversion type's name without spaces FTD
${eventValue} The conversion's value 25.5
${currencyCode} Currency of the value EUR
${eventTime} When the conversion happened (UTC) 2026-09-11T10:30:00Z
${eventTimeStamp} The same, as Unix milliseconds 1789122600000
${conversionId} Routy's conversion ID 98765
${conversionTypeId} Conversion type ID 3
${conversionType} Conversion type name First Deposit
${webhookEventId} ID of this delivery, the same across its retries, so the tracker can de-duplicate 5001

Click & attribution

Placeholder Value
${clickDate} / ${clickTimeStamp} When the click happened, as a date / as Unix milliseconds
${parameterA} / ${parameterB} Sub-IDs A and B from the tracking link
${source} GoogleAds or Facebook when the click carried a gclid or fbclid, otherwise the landing page's source
${gclid}, ${fbclid}, ${fbc}, ${msclkid}, ${obclid} Ad-platform click IDs
${clientUserAgent} The visitor's user agent

Where it came from

Placeholder Value
${trafficSourceId} / ${trafficSource} Traffic source ID / name
${accountId} / ${account} Account ID / name
${brandId} / ${brand} Brand ID / name
${brandLinkId} / ${brandLink} Brand link ID / name
${programId} / ${program} Affiliate program ID / name

Common questions

"The partner's tracker can't match our conversions"

Check which click ID the URL sends. If it sends ${clickId}, change it to ${externalClickId} (see Which click ID?).

"The click ID arrives empty"

${externalClickId} is only filled when the click came in with cid= on the tracking link. If the partner's tracker appends its click ID under another name (clickid, subid…), ask them to send it as cid instead. The same goes for gclid, fbclid and the sub-IDs: they're only there when the original click had them.

When to escalate to engineering

Contact support if:

  • the tracking link carries cid= but ${externalClickId} still arrives empty;
  • the partner reports no postbacks at all for conversions you can see in Routy.