![Perform[cb] and ClickFlare Integration](https://mintcdn.com/clickflare/gS923ib4WFySqxSL/images/integrations/covers/perform-cb.png?fit=max&auto=format&n=gS923ib4WFySqxSL&q=85&s=22226e68ab7e37b07778534b79b16a1c)
- The offer URL sends the ClickFlare click ID to Perform[cb] in
subid2. - The postback URL sends it back to ClickFlare with every conversion, together with the payout. In Perform[cb] it’s a Postback you add under Tracking Pixels.
At a glance
To set up Perform[cb] with ClickFlare:- Set up your domain and postback time.
- Create the Perform[cb] affiliate network.
- Pull your link from Perform[cb].
- Create the offer in ClickFlare.
- Add the Postback under Tracking Pixels.
How the data flows
subid2 on the way in and reads it back with the {subid2} macro on the way out. Its own {clickid} macro is Perform[cb]‘s click ID, not yours.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 approved Perform[cb] affiliate account. Offers marked ATR (Apply To Run) need approval before you can create a link for them.
What the PerformCB template contains
ClickFlare has a PerformCB affiliate network template. It fills in the Perform[cb] 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 Perform[cb] too. See Tracking domains.Report conversions by postback time
Create the campaign
Create the Perform[cb] affiliate network
- Search for PerformCB and pick the template.
- Name it, for example “Perform[cb]”.
- Keep Click Id
{subid2}and Payout{payout}. - Leave Transaction ID and 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 Perform[cb] pays you in.

Pull your link from Perform[cb]
lid is the Link ID. Pull a link for each Link ID you want to run.Create the offer in ClickFlare
- Name the offer.
- Select the Perform[cb] affiliate network you just created.
- Paste the Perform[cb] link into Offer URL and type
{cf_click_id}right aftersubid2=:
![The Offer URL field of the ClickFlare New Offer form with a Perform[cb] link ending in subid2={cf_click_id}](https://mintcdn.com/clickflare/b2lpDlx8sR69TsUK/images/integrations/perform-cb/clickflare-perform-cb-offer-url.png?fit=max&auto=format&n=b2lpDlx8sR69TsUK&q=85&s=1333ee79d61133f0e6f9bf603c4a8adb)
- Leave Append Click ID to Offer Url off when the link already has an empty
subid2=. The toggle would add a secondsubid2={cf_click_id}at the end, and the link would carrysubid2twice. Use the toggle only if your link has nosubid2at all.
payout value from the postback.Add the postback under Tracking Pixels
- Choose Postback as the format (server-to-server).
- Choose the scope: Global, Offer, Offer Group or Vertical. See Which pixel scope to pick.
- Choose the conversion point: Main Conversion for the offer’s payout.
- Paste the ClickFlare postback URL and save.
Add a lander (optional)
Save the campaign and launch
Which pixel scope to pick
Perform[cb] lets you place as many pixels as you like, and fires every pixel that applies to a conversion. A Global pixel fires along with any Offer pixel for the same conversion.Event conversions
Some Perform[cb] offers pay on an event after the main conversion, for example a purchase after a trial. Perform[cb] sends events through their own pixels, with the conversion point set to Event Conversion. Its{event_name} macro holds the name of the event.
By default ClickFlare keeps one conversion per click ID. An event arrives with the same click ID as the main conversion. Without a transaction ID, ClickFlare treats it as the same conversion and keeps the last one received, so the main conversion would disappear. Give event postbacks a txid that differs from the main one.
To track events:
- Create a custom conversion in ClickFlare, for example with the parameter
event. - In Perform[cb], add a second Postback pixel with the conversion point Event Conversion.
- Use the ClickFlare postback URL with
txidandctadded:
txid. Each event arrives with its name as the txid and counts in its own column.
{event_name} and ClickFlare keeps one of them. Perform[cb] has no per-conversion ID macro for affiliates. Ask your affiliate manager how repeat events are reported on that offer. Test one event before you scale.App install offers
For CPI and CPE offers, Perform[cb] usessubid1 for the click or transaction ID in its own guidance, and subid2 for the sub source. ClickFlare’s template uses subid2. Either works, as long as the offer URL and the postback use the same sub ID. If you follow Perform[cb]‘s app layout, put {cf_click_id} in subid1 and change Click Id to {subid1}.
Because of Apple’s App Tracking Transparency, some app conversions reach Perform[cb] without a click ID. Perform[cb] can send those through an aggregated (clickless) postback per campaign. ClickFlare needs a click ID to attribute a conversion, so clickless conversions won’t match a click. Ask your affiliate manager how many conversions on the offer arrive this way.
Verify the setup
Click through the campaign
subid2= followed by a real ClickFlare click ID, not the literal text {cf_click_id}, and only one subid2.Generate a test conversion
Check the conversion in ClickFlare
txid set to the event name.Troubleshooting
Conversions show in Perform[cb] but not in ClickFlare
Conversions show in Perform[cb] but not in ClickFlare
- The pixel doesn’t cover the offer. Check the scope (Global, Offer, Offer Group or Vertical) and that it fires on Main Conversion.
- The pixel is HTML, not Postback. Choose Postback for the ClickFlare URL.
- subid2 is empty in Perform[cb]. The offer URL has
subid2=with nothing after it, or the lander CTA links straight to Perform[cb] instead of using the ClickFlare click URL. - The click ID went into another sub ID. If the offer URL uses
subid1but the postback reads{subid2}, ClickFlare receives the wrong value. Both sides must use the same sub ID.
The postback returns Perform[cb]'s click ID
The postback returns Perform[cb]'s click ID
{clickid} instead of {subid2}. {clickid} is Perform[cb]‘s own click ID, which ClickFlare doesn’t know. Use click_id={subid2}.The main conversion disappeared when an event arrived
The main conversion disappeared when an event arrived
txid, so ClickFlare treated it as the same conversion. Add txid={event_name} and a ct value to the event postback.The payout is 0 or in the wrong currency
The payout is 0 or in the wrong currency
- Check that the postback has
payout={payout}and the offer’s payout is set to Auto in ClickFlare. - Set the affiliate network’s Payout currency in ClickFlare to the currency Perform[cb] pays you in.
FAQ
Does ClickFlare integrate with Perform[cb]?
Does ClickFlare integrate with Perform[cb]?
Why subid2?
Why subid2?
subid2 and uses subid1 for sub source information. ClickFlare’s template follows it. Use subid1, subid3, subid4 and subid5 for your own labels, such as the traffic source or placement.Does an Offer Group with several offers work?
Does an Offer Group with several offers work?
¶m1={offerid} to the postback if you want to see which Perform[cb] offer converted. See Postback parameters.Is this the same as the old Clickbooth setup?
Is this the same as the old Clickbooth setup?
track.clickbooth.com. If you used Clickbooth with another tracker, the setup is the same: the click ID in subid2 and {subid2} in the postback.Can I send the conversion back to my traffic source?
Can I send the conversion back to my traffic source?