
- The offer URL sends the ClickFlare click ID to AdCombo in
clickid. - The postback URL sends it back to ClickFlare with the payout and the order’s transaction ID.
How the data flows
clickid, lowercase with no underscore.What you’ll need
- An active ClickFlare account with your own tracking domain set up. Shared domains get flagged by networks and blocked by browsers. See Tracking domains.
- An AdCombo affiliate account with access to the offer you want to run. Offers with the VIP access type need approval first.
What the AdCombo template contains
ClickFlare has an AdCombo affiliate network template. It fills in the AdCombo macros ClickFlare needs.
Setup
Everything in ClickFlare is done from inside the campaign editor. Create the offer and the affiliate network inline as you go.Set up your own tracking domain
trk.yourdomain.com. The postback URL is built on this domain, so changing it later means updating the postback in AdCombo too. See Tracking domains.Report conversions by postback time
Create the campaign
Create the AdCombo affiliate network
- Search for AdCombo and pick the template.
- Check that Click Id is
{clickid}, Payout is{revenue}and Transaction ID is{trans_id}. - Leave Event Type empty.
- Under Conversion tracking, select your own Tracking Domain and keep S2S Postback URL as the tracking method.
- Set Payout currency to the currency AdCombo pays you in.

Get the tracking link in AdCombo
- Straight from the offer. Open the Offers tab and select the offer. The tracking link fills in on the offer page. Copy it with the copy button.
- Through a campaign. In My Campaigns, create a campaign with the offer. In the offer’s URL Builder tab, choose the landers or prelanders and click Create Campaign. The Tracking URL field updates. One campaign link can rotate several offers and landers.
subacc to subacc4). Keep them for your own values. Don’t put the click ID there: the template reads it from clickid.The link looks like this. The domain varies by account:Create the offer in ClickFlare
- Name the offer.
- Select the AdCombo affiliate network you just created.
- Paste the AdCombo link into Offer URL.
- Turn on Append Click ID to Offer Url. ClickFlare adds
clickid={cf_click_id}, which is the parameter AdCombo expects.

&clickid={cf_click_id} to the end of the URL and leave the toggle off. Use one way only, or clickid appears twice.Set the payout to Auto so ClickFlare uses the payout value from the postback.Add the postback in AdCombo
- Paste the ClickFlare postback URL into Postback for lead only.
- Leave Postback for reject empty. Postback for hold is optional; see Which postback field to use.
- Turn on Use only global postbacks if you want this postback to apply to all your AdCombo campaigns without adding it to each one.
- Save.
Add a lander (optional)
Save the campaign and launch
Which postback field to use
An AdCombo order moves through these stages. Each postback field fires on one of them:Recommended: Postback for lead only
Put the ClickFlare URL in Postback for lead and nowhere else. ClickFlare then receives a postback only for confirmed orders, so every conversion in your reports is one AdCombo pays you for, with the real payout. Cancelled and fake orders never reach ClickFlare. The trade-off is timing. Conversions show up only after the call-center cycle, hours or days after the click. Judge a campaign on yesterday’s or last week’s numbers, not the last hour.Why never Postback for reject
ClickFlare doesn’t read a status. Every postback it receives counts as a conversion. It decides whether a postback is a new conversion or an update by the click ID and the transaction ID:- Same click ID, same txid: the later postback replaces the earlier one. The last one received wins.
- Same click ID, different txid: both count as separate conversions.
{trans_id} stays the same for an order as it moves through statuses, the reject replaces your confirmed conversion and still counts as a conversion. If it changes, the reject is added as an extra conversion. Either way your reports show a sale that AdCombo didn’t pay for.
Optional: also Postback for hold
You can paste the same ClickFlare URL into Postback for hold to see order volume as soon as it comes in. Know what happens first:- Holds that are later confirmed should be counted once. The confirmed postback carries the same click ID and, most likely, the same
{trans_id}, so it replaces the hold. AdCombo doesn’t document that{trans_id}is the same across statuses. Compare the hold and lead postbacks for one order in ClickFlare’s Logs → Event Logs before you rely on it. - Holds that are later rejected stay counted. With no reject postback, nothing replaces them, so they stay in ClickFlare as conversions.
- The payout on a hold is unknown. Whether AdCombo fills
{revenue}on a hold postback, and with what, isn’t documented. Check a hold postback before trusting revenue in ClickFlare.
Why the transaction ID matters
By default ClickFlare keeps one conversion per click ID. If several postbacks arrive with the same click ID and no transaction ID, ClickFlare treats them as the same conversion and keeps only the last one received. Thetxid parameter tells ClickFlare which postbacks belong to the same conversion and which are different ones.
{trans_id} is AdCombo’s only transaction-type macro. When it resolves it is numeric, and it most likely identifies the order:
- Two orders from the same click have different
{trans_id}values, so ClickFlare counts both. - A resent postback for the same order carries the same
{trans_id}, so ClickFlare doesn’t count it twice.
Verify the setup
Click through the campaign
clickid= followed by a real ClickFlare click ID, not the literal text {cf_click_id}.Check the click in AdCombo
Check the postback
- Wait for the first confirmed order and look for it in ClickFlare.
- To check the URL itself right away, copy it, replace the macros with a real ClickFlare click ID from your test click, a payout and any test ID, and open it in your browser. This records a test conversion in ClickFlare.
Check the conversion in ClickFlare
txid and no literal macros.Troubleshooting
Confirmed orders show in AdCombo but not in ClickFlare
Confirmed orders show in AdCombo but not in ClickFlare
- The postback is in the wrong field. It must be in Postback for lead. A URL in Postback for hold alone fires only for new orders.
- The postback wasn’t applied to the campaign. If you rely on the global postback, check Use only global postbacks. If you use per-campaign postbacks, check the campaign’s Postback/Pixel tab.
- The click ID didn’t reach AdCombo. The offer URL is missing
clickid={cf_click_id}, or your lander’s CTA links straight to AdCombo instead of using the ClickFlare click URL. - The order hasn’t been confirmed yet. A hold fires nothing on the recommended setup.
ClickFlare receives a literal macro instead of a value
ClickFlare receives a literal macro instead of a value
{clickid} means the click ID wasn’t on the link the visitor actually clicked. Check the offer URL and your lander’s CTA. A literal cf_click_id means the offer URL has the token without braces.ClickFlare shows more revenue than AdCombo pays
ClickFlare shows more revenue than AdCombo pays
FAQ
Why clickid and not a Subaccount field?
Why clickid and not a Subaccount field?
clickid is AdCombo’s dedicated parameter for tracker click IDs, and it’s what the template reads back with {clickid}. Every major tracker uses it. The Subaccount fields (subacc to subacc4) stay free for your own data.Can I pass more data to AdCombo?
Can I pass more data to AdCombo?
&subacc={campaign_id}&subacc2={trackingField1}, and see them in AdCombo’s statistics. Keep clickid for the click ID.Can I send the conversion back to my traffic source?
Can I send the conversion back to my traffic source?