Skip to main content
ADW.NET and ClickFlare Integration ADW.NET monetizes search traffic. Its main direction is Display2Search: it sends users from advertising networks to relevant advertiser search keys. Its site lists a paid Google search feed and Yahoo and Bing hosted feeds for organic and type-in traffic. ADW.NET connects to ClickFlare through a postback. There is no API integration. The setup has two links:
  • The feed URL goes into ClickFlare as an offer, with the ClickFlare click ID in ADW.NET’s sub ID parameter.
  • The postback URL goes to ADW.NET. When a visit earns, ADW.NET fires it server to server with the same click ID and the revenue.
ADW.NET doesn’t publish its sub ID parameter or postback macros. Ask your ADW.NET account manager for both before you start. This guide marks them as REPLACE_SUBID and REPLACE_MACRO.

​
At a glance

To set up ADW.NET with ClickFlare:
  1. Create the campaign.
  2. Create the ADW.NET affiliate network.
  3. Create the offer with the feed URL.
  4. Send ADW.NET the postback URL.
Each step is explained in Setup.

​
How the data flows

Offer URL = their parameter + your token. Postback URL = your parameter + their macro. Whatever ADW.NET stores from the sub ID on the way in, it must send back in click_id on the way out.

​
What you’ll need

  • A ClickFlare account with your own tracking domain. Shared domains get flagged. See Tracking domains.
  • An ADW.NET account with a feed URL and postback support.
  • From your ADW.NET account manager:
    • the sub ID parameter that carries your click ID,
    • the postback macros for the click ID, the revenue and, if they have one, a unique conversion ID,
    • how often ADW.NET fires the postback and whether revenue can change later.

​
Setup

Everything in ClickFlare happens 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 first, for example trk.yourdomain.com. The postback URL is built on it, so changing it later means sending ADW.NET a new postback. See Tracking domains.
2

Create the campaign

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

Create the ADW.NET affiliate network

While creating the offer, create a new affiliate network in its Affiliate Network field and name it “ADW.NET”. Under Conversion tracking, select your own Tracking Domain and keep S2S Postback URL as the method. Set Payout currency to the currency ADW.NET pays you in.ClickFlare shows the postback URL for the network. It looks like this:
Copy it and save the network.
4

Create the offer with the feed URL

In the offer form:
  1. Name the offer, for example “ADW.NET - Google feed - US”.
  2. Select the ADW.NET affiliate network.
  3. Paste the feed URL from ADW.NET and add the sub ID parameter with the click ID token:
If the feed URL already has a ?, add the parameter with & instead.Set the payout to Auto so ClickFlare uses the revenue from the postback.
Keep the braces: {cf_click_id}. Without them ADW.NET stores the literal text cf_click_id and no conversion can be matched to a click.
5

Send ADW.NET the postback URL

Replace the placeholders with ADW.NET’s macros and send the URL to your account manager:
Ask ADW.NET to confirm the postback is active on your account.
6

Add a lander (optional)

If you send traffic through a lander first, its CTA must use the ClickFlare click URL, not the feed URL. ClickFlare then adds the click ID when it redirects to the feed.
7

Save the campaign and launch

Save the campaign, copy the campaign URL from the Tracking tab and use it in your ads. Run Verify the setup first.

​
Questions to ask ADW.NET

Feed revenue doesn’t always behave like an affiliate sale. Get answers to these before you scale, so your ClickFlare numbers mean what you think they mean:
  • When does the postback fire? On each paid click, or in batches later.
  • Is the revenue final? If it’s an estimate that changes after the fact, ask whether ADW.NET fires an updated postback, and with which ID.
  • Is there a unique conversion ID? With a txid, each postback for a click counts as its own conversion, and a resend with the same txid replaces the earlier one instead of adding to it. Without one, ClickFlare keeps one conversion per click ID.
  • Which currency? Set the same one as the affiliate network’s Payout currency.
If a postback misses conversions and ADW.NET can give you a report with revenue per click ID, import the missing rows with Conversion Upload. Each row needs a valid ClickFlare click ID.

​
Verify the setup

1

Click through the campaign

Open the ClickFlare campaign URL (with a lander, click the CTA). When the feed loads, check the first request to ADW.NET in the address bar or your browser’s network tab: the sub ID must carry a real click ID, not {cf_click_id}.
2

Fire a test postback

Copy that click ID and ask your account manager to fire a test postback with it. You can also call the postback yourself in a browser to check the ClickFlare side:
3

Check ClickFlare

The conversion should appear on the campaign with the revenue. In Logs → Event Logs, check the click ID and payout arrived as sent.

​
Troubleshooting

  • The postback isn’t active yet on ADW.NET’s side. Ask your account manager.
  • The sub ID in the offer URL is empty, or a lander CTA links straight to the feed.
  • The click ID went into one sub ID and the postback returns another.
See Troubleshooting S2S postbacks.
  • A literal macro means ADW.NET didn’t replace it. Check the spelling with your account manager.
  • A literal cf_click_id means the offer URL has the token without braces.
  • Check the payout currency on the affiliate network.
  • Without a txid, several postbacks for one click collapse into one conversion.
  • If ADW.NET adjusts revenue later and doesn’t post the change back, ClickFlare keeps the first value.

​
FAQ

Yes, through an S2S postback. You pass the ClickFlare click ID in ADW.NET’s sub ID, and ADW.NET fires ClickFlare’s postback URL with the click ID and revenue.
No. ADW.NET connects to ClickFlare through the postback only.
If ADW.NET supports more sub IDs, use them for values like the traffic source placement or ad ID. Keep one for the click ID.
Yes. Once ClickFlare records the conversion, it can pass it to the traffic source through that source’s postback or conversion API integration.

S2S postback

How postbacks work

Postback parameters

click_id, txid, ct

Postback issues

Troubleshoot S2S