Leadbit and ClickFlare Integration Guide

• The offer URL sends the ClickFlare click ID to Leadbit in sub1.
• The postback URL sends it back to ClickFlare with the payout and the lead’s ID.

​

How the data flows

Ad click
  → https://trk.yourdomain.com/cf/r/CAMPAIGN?...
     (ClickFlare records the click and generates the click ID)
  → [optional lander → CTA uses the ClickFlare click URL]
  → https://leadbit-domain.com/ABCD?sub1=CF_CLICK_ID
     (Leadbit stores the ClickFlare click ID in sub1)
  → Visitor submits the order form: Leadbit records a new lead
  → Call center confirms the order: the lead is approved
  → Leadbit fires your postback:
     https://trk.yourdomain.com/cf/cv?click_id=CF_CLICK_ID&payout=25.00&txid=LEADBIT_LEAD_ID
     (ClickFlare matches the conversion to the original click)

​

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.
• A Leadbit affiliate account with access to the offer you want to run.

​

What the Leadbit template contains

​

Setup

1

Set up your own tracking domain

Add a custom tracking domain before anything else, for example trk.yourdomain.com. The postback URL is built on this domain, so changing it later means updating the postback in Leadbit too. See Tracking domains.

2

Report conversions by postback time

Go to Settings → General Settings and set Conversion registration time reporting to Postback Timestamp.On COD offers, the approval comes in long after the click, and Leadbit postbacks can also be delayed. With the default Visit Timestamp, ClickFlare reports the conversion on the day of the original click, so past days keep changing as approvals arrive, and the dates don’t match Leadbit’s. See Conversion registration time.

This is an account-wide setting. It changes the date conversions are reported on for every campaign.

3

Create the campaign

Go to Campaigns → New Campaign, choose Redirect tracking, pick your traffic source and select your tracking domain. See Creating a campaign.

4

Create the Leadbit affiliate network

While creating the offer for the campaign, create a new affiliate network in its Affiliate Network field. You can also create it first under Affiliate Networks → + New. Either way:

1. Search for Leadbit and pick the template.
2. Check that Click Id is {sub1}, Payout is {cost} and Transaction ID is {id}.
3. Leave Event Type empty.
4. Under Conversion tracking, select your own Tracking Domain and keep S2S Postback URL as the tracking method.
5. Set Payout currency to the currency your Leadbit offers pay in.

ClickFlare builds the postback URL from these fields:

https://trk.yourdomain.com/cf/cv?click_id={sub1}&payout={cost}&txid={id}

Copy the postback URL and save the network.

Leadbit has a separate {currency} macro, which the template doesn’t use. Most COD offers pay in USD, but some may not. Check each offer’s currency in Leadbit and make sure it matches the Payout currency on the network.

5

Create a source and a flow in Leadbit

Leadbit needs a source and a flow before it gives you a link.

1. Open Sources and click Create new source. Pick the type, the Kind (traffic type), and enter a Title and Description. Both are required. Save.
2. Go to Offers and click Create tracking URL next to the offer.
3. In the Flow section, enter a flow name and select your source.
4. In the Landing section, tick the landers Leadbit should use.
5. Click Save flow.

6

Copy the tracking link

Open the Tracking URLs tab and click the link icon next to your flow. The Get code pop-up shows the link and a sub1 field. You have two options:

• Copy the bare link and let ClickFlare add sub1 in the next step. This is the simplest.
• Type {cf_click_id} into the sub1 field. The link updates to include sub1={cf_click_id}.

7

Create the offer in ClickFlare

In the offer form:

1. Name the offer.
2. Select the Leadbit affiliate network you just created.
3. Paste the Leadbit link into Offer URL.
4. If the link has no sub1 yet, turn on Append Click ID to Offer Url. ClickFlare adds sub1={cf_click_id}, which is the parameter Leadbit expects.

The link ClickFlare sends visitors to then looks like this:

https://leadbit-domain.com/ABCD?sub1={cf_click_id}

Use one way only. If you filled the sub1 field in Get code, leave the toggle off, or sub1 appears twice.

Write {cf_click_id} with braces. Without them Leadbit stores the literal text cf_click_id, the postback returns that text, and the conversion cannot be matched to a click.

Set the payout to Auto so ClickFlare uses the payout value from the postback.

8

Add the global postback in Leadbit

In older guides the global postback is under Profile → Global Postback in the right-hand menu (some call it Tools → Global postback). Then:

1. Click Edit global postback.
2. Paste the ClickFlare postback URL into the Postback URL field.
3. Tick only the approved (confirmed) status. Leave every other box unticked. See Which statuses to tick.
4. Choose whether the postback applies to your existing flows or only to new ones. To cover a flow you already created, apply it to existing flows.
5. Save.

Voluum’s Leadbit guide says to tick all six boxes. Don’t do that with ClickFlare. ClickFlare doesn’t read the status, so every ticked case, including rejected leads, arrives as a conversion with a payout.

Each flow also has a Statistics transmission setup section with separate postback fields, one per conversion step. If you set the postback per flow instead of globally, paste the ClickFlare URL into the approved field only.

9

Check the transaction ID macro

Next to the postback field, Leadbit lists the macros it supports. Check that {id} is there. If you only see {transactionid}, use that in Transaction ID instead and copy the new postback URL into Leadbit. If neither is listed, ask your Leadbit manager which macro holds the lead ID.

10

Add a lander (optional)

If you use your own lander instead of Leadbit’s, its CTA must use the ClickFlare click URL, not the Leadbit link. ClickFlare then adds the click ID when it redirects to the offer. See Paths with landers and offers.

11

Save the campaign and launch

Save the campaign, copy the campaign URL from the Tracking tab and use it in your ads. Before you spend money on traffic, run the checks in Verify the setup.

​

Which statuses to tick

​

Recommended: approved only

​

Why ticking everything breaks your numbers

• 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.

​

Optional: new and approved

• Leads that are approved later should be counted once, if {id} stays the same for a lead across statuses. The approval then replaces the new-lead postback. Leadbit doesn’t document this, so compare the two postbacks for one lead in ClickFlare’s Logs → Event Logs.
• Leads that are never approved stay counted. No later postback replaces them.
• The payout on a new lead is unknown. Whether Leadbit fills {cost} on a new-lead postback isn’t documented. Check one first.

​

Why the transaction ID matters

• Two leads from the same click (for example a visitor who orders twice) have different IDs, so ClickFlare counts both.
• A resent postback for the same lead carries the same ID, so ClickFlare doesn’t count it twice.

​

Verify the setup

​

Troubleshooting

​

FAQ

​

Related