Skip to main content
Everflow and ClickFlare Integration Everflow is the platform behind many affiliate networks and advertiser programs. As a partner (affiliate), you log in to the network’s own Everflow portal, for example yournetwork.everflowclient.io, pick offers, generate tracking links and add postbacks. To track Everflow offers in ClickFlare, two links have to carry the ClickFlare click ID in both directions:
  • The offer URL sends the ClickFlare click ID to Everflow in sub2.
  • The postback URL sends it back to ClickFlare with every conversion, together with the payout and a unique transaction ID.
This guide covers the full setup, why the postback needs txid={conversion_id}, how to report Everflow events (for example Lead and Sale) as separate conversion types, and how to check that it all works.

​
How the data flows

The two links mirror each other:
Offer URL = their parameter + your token. Postback URL = your parameter + their macro. Everflow writes the click ID into sub2 on the way in and reads it back with the {sub2} macro on the way out. If either side uses a different sub ID, conversions cannot be matched.

​
What you’ll need

  • An active ClickFlare account with your own tracking domain set up. Shared domains get flagged by ad platforms and networks. See Tracking domains.
  • A partner account on the network’s Everflow portal, approved for the offer you want to run.
  • If you want to report Everflow events separately (Lead, Sale, Deposit and so on): a custom conversion in ClickFlare for each event.

​
What the Everflow template contains

ClickFlare has an Everflow affiliate network template. It fills in the three Everflow macros ClickFlare needs: the click ID, the payout and the transaction ID. The Everflow template in ClickFlare: Click Id maps {sub2} to click_id, Payout maps {payout_amount} to payout, and Transaction ID is set to {conversion_id}, which maps to txid
Do not use {transaction_id} as the transaction ID. In Everflow, {transaction_id} is Everflow’s own click ID: it stays the same for every conversion and event on that click, so it does not stop deduplication.

​
Setup

Everything in ClickFlare is done from inside the campaign editor. Create the offer and the affiliate network inline as you go.
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 Everflow too. See Tracking domains.
2

Report conversions by postback time

Go to Settings → General Settings and set Conversion registration time reporting to Postback Timestamp.ClickFlare General Settings with Conversion registration time reporting set to Postback Timestamp, and the Default report time zone below itEverflow reports a conversion on the day it happened. With the default Visit Timestamp, ClickFlare reports it on the day of the original click instead, so a conversion that comes in days after the click lands on a different date in each platform. With Postback Timestamp, both report it on the same day. See Conversion registration time.
This is an account-wide setting. It changes the date conversions are reported on for every campaign, not only Everflow ones.
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.For the redirect between ClickFlare and Everflow, keep the default 302 unless you have a reason not to. See Transition modes.
4

Create the Everflow 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 Everflow and pick the template.
  2. Name the network. If you work with several Everflow-based networks, use the network’s name (for example “Everflow - NetworkName”). Each network has its own Everflow portal and its own postback.
  3. Check that Transaction ID is {conversion_id}. The template fills it in. If you are editing an Everflow network you created earlier and the field is empty, type it in.
  4. Leave Event Type empty.
  5. Under Conversion tracking, select your own Tracking Domain and keep S2S Postback URL as the tracking method.
  6. Set Payout currency to the currency of your Everflow offers.
ClickFlare builds the postback URL from these fields:
The Conversion tracking section of the Everflow network in ClickFlare, showing the generated postback URL with click_id={sub2}, payout={payout_amount} and txid={conversion_id}Copy the postback URL and save the network.
5

Add the postback in Everflow

Log in to the network’s Everflow portal and go to Postbacks → + Postback. Then set:Everflow's Add Postback form: Conversion type, Global level, Postback delivery method, and the ClickFlare postback URL in the Postback URL fieldClick Add. Everflow highlights each recognised macro in the URL. If {sub2}, {payout_amount} or {conversion_id} is not highlighted, check its spelling.
Use Global unless some offers need a different postback. If you add both a Global and a Specific postback, check in Everflow which one fires for that offer, so the same conversion is not sent twice.
Leave Delay Postback off. It holds the postback for up to 5 minutes, which only delays the conversion in ClickFlare.
6

Get the offer's tracking link from Everflow

In Everflow, go to Offers, open the offer and click Offer Tracking Links. In the Tracking & Asset Generator:
  1. Keep Get Tracking Link(s) on Yes.
  2. Select Redirect Link.
  3. Open Additional Parameters and type {cf_click_id} in sub2.
  4. Copy the generated link. It ends in ?sub2={cf_click_id}. Everflow's Tracking & Asset Generator with Redirect Link selected, {cf_click_id} in the sub2 field, and the generated link ending in ?sub2={cf_click_id}
Use the Redirect Link, not Direct Linking. The redirect link goes through Everflow’s tracking domain, which records the click and stores sub2. A direct link sends the visitor straight to the advertiser’s page and relies on the advertiser’s own Everflow script to record the click.
7

Create the offer in ClickFlare

In the offer form:
  1. Name the offer.
  2. Select the Everflow affiliate network you just created.
  3. Paste the Everflow link into Offer URL.
The ClickFlare New Offer form with the Everflow redirect link and sub2={cf_click_id} in the Offer URL fieldIf you copied the link without sub2, turn on Append Click ID to Offer Url instead. ClickFlare then adds sub2={cf_click_id} from the Everflow template. Use one or the other, not both.
Write {cf_click_id} with braces. Without them Everflow 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 a lander (optional)

If you send traffic through a lander before the offer, the lander’s CTA must use the ClickFlare click URL, not the Everflow link. ClickFlare then adds the click ID when it redirects to the offer. See Paths with landers and offers. Without a lander, see Paths with offers only.
9

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.

​
Why the postback needs a unique txid

By default ClickFlare keeps one conversion per click ID. If Everflow sends several postbacks with the same click ID and no transaction ID, ClickFlare treats them as the same conversion, and you only see one of them (the last one received). Everflow often sends more than one postback per click:
  • Several events on one offer. For example a Lead followed by a Sale, or a Lead followed by a revenue adjustment the network adds later.
  • Multiple payouts per conversion. Offers with several payout rules can fire a postback for each.
  • Recurring or upsell conversions on the same visitor.
The txid parameter tells ClickFlare that each postback is a separate conversion. It works only when its value is different on every postback. That is why the macro matters:
{conversion_id} belongs to the conversion, so if Everflow sends the same conversion again it carries the same ID and ClickFlare does not count it twice. {random} changes on every send, so a resent postback becomes a second conversion.

​
Track Everflow events as custom conversions

If the offer has several events, you can report each one as its own conversion type in ClickFlare, for example Lead and Sale in separate columns. ClickFlare uses the ct parameter for this.
1

Create a custom conversion for each event

In ClickFlare, go to Settings → Custom Conversions and add one per event. For a Lead event, for example, name it Lead and add the parameter lead. See Custom conversions.
2

Add an Event postback for each event in Everflow

Go to Postbacks → + Postback and set:
  • Postback Type: Event
  • Postback Level: Specific
  • Offer and Event: the offer and the event this postback is for
  • Delivery Method: Postback
  • Postback URL: the ClickFlare postback URL with &ct= and the custom conversion parameter added at the end
Everflow's Add Postback form for an Event postback at Specific level, with Offer and Event selectors and the ClickFlare postback URL ending in &ct=leadRepeat for each event, changing only the ct value.
The ct value must exactly match a parameter of a custom conversion in ClickFlare. If it does not, ClickFlare records a regular conversion instead, and your main conversion column looks inflated.
Only if every Everflow event name on your offers is also a valid custom conversion parameter. Custom conversion parameters cannot contain spaces, while Everflow event names often do (for example “Revenue Backfill”), and names can differ in capitalisation between offers. A fixed ct value per event postback is the reliable option.
Yes, if every event can share one ct value or you leave ct out. A Global Event postback fires for all events on all offers with the same URL, so all events arrive in ClickFlare as the same conversion type. Keep txid={conversion_id} in it so the events are not deduplicated.
Not necessarily. Without ct, the offer’s base conversion is recorded as a regular conversion in ClickFlare. If you want it as a custom conversion as well (for example ct=lead), add the parameter to the Conversion postback and create the matching custom conversion.

​
Verify the setup

1

Click through the campaign

Open the ClickFlare campaign URL (with a lander, also click the CTA). When the offer loads, the first request goes through Everflow’s tracking domain. In your browser’s address bar or network tab, check that it has sub2= followed by a real ClickFlare click ID, not the literal text {cf_click_id}.
2

Check the click in Everflow

In Everflow, open Reporting for the offer and look for the click and check that its sub2 value is the ClickFlare click ID.
3

Generate a test conversion

Ask your affiliate manager to fire a test conversion for your click, or complete the offer if that is allowed.
4

Check the conversion in ClickFlare

The conversion should appear on the campaign, with the payout from Everflow. In Logs → Event Logs, check that the conversion arrived with the txid from Everflow. If you set up events, check that each event appears under its custom conversion.

​
Compare numbers between ClickFlare and Everflow

When the conversion counts or revenue for a day do not match, check these two settings before anything else: Compare the same date range, the same offer and the same conversion type (base conversions or a specific event). If the numbers still differ, look up individual conversions: the txid in ClickFlare’s Logs → Event Logs is the Everflow conversion ID, so you can match each one to its row in Everflow.

​
Troubleshooting

The two platforms are not using the same date for the conversions. Set ClickFlare to Postback Timestamp and compare in the same time zone. See Compare numbers between ClickFlare and Everflow.
Work through these in order:
  • The postback is not active, or is limited to another offer. In Everflow, open Postbacks and check that a postback is Active and covers this offer (Global, or Specific for this offer).
  • sub2 is empty in Everflow. The offer URL is missing sub2={cf_click_id}, or the lander CTA links straight to Everflow instead of using the ClickFlare click URL.
  • The click ID went into another sub ID. If the offer URL uses sub1 (or anything else) but the postback reads {sub2}, ClickFlare receives an empty click ID. Both sides must use the same sub ID.
  • The postback uses an old tracking domain. If you changed your tracking domain in ClickFlare, update the postback URL in Everflow.
See Troubleshooting S2S postbacks for the general checks.
The postback has no txid, or its value is the same on every event. Add txid={conversion_id} to the postback URL in Everflow, in every postback you created (Conversion and Event). See Why the postback needs a unique txid. Conversions that were already deduplicated are not restored.
The ct value in the postback does not match any custom conversion parameter in ClickFlare. Compare them character by character, including capitalisation, and make sure the custom conversion was created before the postbacks arrived.
  • Check that the postback has payout={payout_amount} and the offer’s payout is set to Auto in ClickFlare.
  • Some Everflow events pay nothing, for example a revenue adjustment row with a 0.00 payout. Those arrive with payout=0.
  • {payout_amount} is in the offer’s currency. Set the affiliate network’s Payout currency in ClickFlare to the same currency.
  • A literal {sub2} means the macro is misspelt in the Everflow postback, so Everflow did not replace it. Check that Everflow highlights it as a macro.
  • A literal cf_click_id means the offer URL in ClickFlare has the token without braces. It must be {cf_click_id}.

​
FAQ

sub2 is the ClickFlare template’s default, and the postback reads it back with {sub2}. Any sub ID from sub1 to sub5 works as long as the offer URL and the postback use the same one. If you change it, change it in the ClickFlare affiliate network (Click Id token), the offer URL and the Everflow postback.
Yes, one per network. Each network has its own Everflow portal, so you add a postback in each one. Separate affiliate networks also keep the reporting per network in ClickFlare.
Yes. Use the other sub IDs in the offer URL, for example sub3={campaign_id}&sub4={trackingField1}. Everflow shows them in its reports. Keep sub2 for the click ID.
Yes. Once ClickFlare records the Everflow conversion, it can send it to the traffic source through the traffic source’s postback or conversion API integration. Nothing changes on the Everflow side.

Custom conversions

Report each event

Postback parameters

click_id, txid, ct

Postback issues

Troubleshoot S2S