Skip to main content
Traffic Nomads traffic source template Traffic Nomads is an ad network focused on iGaming: casino, sports betting and other gambling offers. It sells pop, push, in-page push, banner and native traffic. This guide sets up Traffic Nomads as a traffic source in ClickFlare. It covers passing Traffic Nomads’ click data into your reports and sending conversions, with payout, back to Traffic Nomads so its optimization and your stats agree. You do everything from the campaign editor. The Traffic Nomads traffic source is created inline, without leaving the campaign.
The Traffic Nomads template’s postback sends the wrong click ID. Before you save, change {click_id} to {external_id}. Step 2 shows the exact URL.

​
At a glance

​
How it works

1

Traffic Nomads sends the click

A visitor clicks your ad. Traffic Nomads opens your ClickFlare campaign URL and fills in its macros: the click ID in clickid, plus the publisher, the zone, the campaign, the device and the country.
2

ClickFlare stores the Traffic Nomads click ID

ClickFlare saves the value of clickid as the visit’s External ID, saves the publisher ID in tracking field 1, and redirects the visitor to your lander or offer.
3

The conversion reaches ClickFlare

Your casino, sportsbook or affiliate network posts the conversion back to ClickFlare, matched on the ClickFlare click ID.
4

ClickFlare posts it back to Traffic Nomads

ClickFlare fires the Traffic Nomads postback, replacing {external_id} with the stored Traffic Nomads click ID, {payout} with the revenue and {trackingField1} with the publisher ID. Traffic Nomads matches it to the original click.
The mirror to keep straight: in the campaign URL you write ClickFlare’s parameter (clickid) and Traffic Nomads’ macro ({clickid}). The template does this for you. In the postback URL you write Traffic Nomads’ parameter (clickid) and ClickFlare’s token ({external_id}). Both sides happen to call the parameter clickid. The value in braces is what changes.

​
Before you start

  • Set up your own tracking domain. Run the campaign and the postback on your own custom domain. Shared domains get flagged by networks and blocked by browsers. See Custom Domains.
  • Have an offer ready in ClickFlare, and the operator or affiliate network set up to post conversions back to ClickFlare. See Creating an Offer and Adding an Affiliate Network.
  • Have a Traffic Nomads advertiser account. You log in at partners.trafficnomads.com.
  • Decide which conversions Traffic Nomads should receive. In iGaming the event that pays is the first-time deposit (FTD), which can arrive days after the click. Registrations arrive fast but say little about player quality. Decide now whether to send the FTD, the registration, or both. See Sending the right event.

​
Step 1 – Create the campaign and the Traffic Nomads traffic source

  1. Go to Campaigns and click New.
  2. In Traffic Source, open the dropdown and click + New Traffic Source.
  3. Type traffic nomads in the search box and select the Traffic Nomads template.
  4. Enter a Name, for example Traffic Nomads.
  5. Leave Cost currency on USD unless your Traffic Nomads account is billed in another currency.
The template fills in the Parameters table for you: The Traffic Nomads template's Parameters table in ClickFlare, with Traffic Nomads' macros pre-filled Each tracking field becomes a column you can group reports by. Pub ID and Zone are the ones you will use most. They tell you which publishers and zones bring depositors, so you can blacklist or bid up sources in Traffic Nomads.
Don’t change or remove the externalId row, and keep Pub ID on tracking field 1. The postback reads the publisher ID from {trackingField1}. If you move or delete that row, the postback sends an empty pubid.
To pass more Traffic Nomads data, click Add Parameter, give it a name and parameter, and enter the Traffic Nomads macro as the TS Token. ClickFlare assigns the next free tracking field. Check the macros your Traffic Nomads account offers before adding them. Traffic Nomads doesn’t publish a macro list.

​
Step 2 – Set up the postback

The postback is what sends conversions to Traffic Nomads. It lives on the traffic source, so every campaign that uses this Traffic Nomads traffic source sends conversions the same way.
  1. In the New Traffic Source form, scroll to Passing conversion info to traffic source.
  2. Turn on Traffic source postback URL. The template’s postback appears:
The Traffic source postback URL switched on, showing the Traffic Nomads template's postback It sends three values:
  1. Replace {click_id} with {external_id}. The result:
{external_id} is the Traffic Nomads click ID ClickFlare stored from the clickid parameter in Step 1. That is the value Traffic Nomads can match.
  1. In the dropdown on the left, choose the ClickFlare event that should fire the postback. Keep Conversions to send every conversion. If your final action is a custom conversion (for example ftd), choose that instead.
  2. Click Save. You are back in the campaign editor with the Traffic Nomads traffic source selected.
{click_id} is a real ClickFlare token, so ClickFlare fills it in without error. It just fills in the wrong ID. The postback returns successfully and Traffic Nomads silently fails to match any conversion. Always use {external_id} here.
payout is read in the currency of your Traffic Nomads account. If your operator pays in EUR or another currency, see Multicurrency in ClickFlare. If your Traffic Nomads account manager gives you a different postback host or format, use theirs, with {external_id} as the click ID and {payout} as the payout. To learn what each postback token does, see How to Configure a Traffic Source S2S Postback URL.

​
Step 3 – Finish the campaign and copy its URL

  1. Name the campaign.
  2. Set the Cost Model. Start with Not Tracked to test the template’s cost row, or use CPC with your bid. See Cost.
  3. Choose Redirect or Direct tracking. Redirect is the usual choice for pop and push traffic.
  4. Click Next and, on Destination, add your lander (optional) and your offer.
  5. Save, open Tracking, select your own tracking domain and copy the campaign URL.
The campaign URL already contains every Traffic Nomads macro from the template, for example clickid={clickid} and zone={zone}. If you use a lander or pre-lander, its call-to-action must link to the ClickFlare click URL, not to the casino or sportsbook directly. Otherwise the visit reaches the offer without a ClickFlare click ID, and the deposit cannot be traced back to Traffic Nomads. See Creating a Campaign in ClickFlare.

​
Step 4 – Create the campaign in Traffic Nomads

  1. Log in to your Traffic Nomads advertiser account.
  2. Create a campaign and choose the format: pop, push, in-page push, banner or native.
  3. Paste the ClickFlare campaign URL into the campaign’s URL field.
  4. Set targeting, budget and bid as usual, and upload your creatives.
  5. If you want Traffic Nomads to optimize on deposits, set up its second-event tracking and FTD Magnet AI as your account manager describes. See Sending the right event.
Paste the URL exactly as ClickFlare gives it. Traffic Nomads replaces each {...} macro when the ad is clicked.

​
Step 5 – Test the integration

  1. Launch the campaign with a low daily budget.
  2. In ClickFlare, open the campaign report and group by Zone and Pub ID. Real values mean the macros are filling in. If you see the literal text {zone}, the URL was edited or pasted in the wrong field.
  3. Check that the visits have an External ID. An empty External ID means {clickid} didn’t reach ClickFlare, and no postback can work.
  4. When the first conversion arrives, go to Logs → Postback Status and filter by the campaign. Open the request to node2.trafficnomads.com and check the clickid value: it must match the visit’s External ID, not the ClickFlare click ID.
  5. Check that the conversion shows in your Traffic Nomads stats. If it doesn’t, contact Traffic Nomads support with the click ID from the postback log.

​
Sending the right event

Traffic Nomads tracks a first event and a second event, for example a sign-up and a first-time deposit. Its FTD Magnet AI optimizes on deposits, and it can only do that if you send the deposit back.
  1. In ClickFlare, create a custom conversion for each step, for example registration and ftd.
  2. Ask your Traffic Nomads account manager, or support@trafficnomads.com, for the postback format of the second event. It isn’t publicly documented.
  3. On the Traffic Nomads traffic source, click + Another postback URL for the second event and paste that URL, with {external_id} as the click ID and {payout} as the payout.
  4. Map each postback to its ClickFlare event: registration to the first, ftd to the second.
Registration-to-deposit rates vary several times over between zones. Two zones with the same cost per registration can bring very different numbers of depositors. If Traffic Nomads only sees registrations, it optimizes toward zones that register but don’t deposit.Deposits can land days after the click. Don’t cut zones on day-two data. Read the report by click date and give each cohort time to mature.
If Traffic Nomads should only learn from deposits, keep a single postback and map it to the ftd custom conversion. Registrations still show in ClickFlare. They just don’t reach Traffic Nomads.To send a postback only for some conversions, for example only those above a certain payout, use Event filter under the postback to add conditions.

​
Cost

The template has a Cost row: it reads cost from a URL parameter named payout, filled with the macro {payout}. The naming is confusing. On the click side this is meant to be the price of the click, not your revenue. Traffic Nomads doesn’t publish {payout} as a click macro, and other trackers’ Traffic Nomads setups use no cost macro at all. So check it before relying on it:
  1. Set the campaign’s Cost Model to Not Tracked, so ClickFlare reads the cost from the URL.
  2. After the first visits, compare ClickFlare’s Cost column with your Traffic Nomads spend.
  3. If the cost is zero or wrong, switch the Cost Model to CPC and enter your bid. For CPM buying, enter your CPM bid divided by 1,000. A pop impression is roughly one visit.
For campaigns bought on a CPA basis, set the Cost Model to CPA, with your price per conversion. When the recorded spend differs from your Traffic Nomads spend, correct it with a manual cost upload. See Cost Models.

​
Delayed revenue

Deposits and redeposits often arrive long after the click. ClickFlare can pass revenue that arrives later back to the traffic source. See Sending Delayed Revenue to Traffic Sources.

​
Troubleshooting

  • The postback still has clickid={click_id}. Change it to clickid={external_id}.
  • Traffic source postback URL is off on the Traffic Nomads traffic source.
  • Disable sending postbacks to traffic source is on in the campaign.
  • The postback is mapped to a different event than the one the conversion logged. Check Logs → Event Logs to see which event was recorded.
  • Check Logs → Postback Status: a failed request shows the status code Traffic Nomads returned.
The postback reads the publisher from {trackingField1}. The Pub ID row was moved, removed, or arrived empty. Keep it as the first tracking field, and check that the Pub ID column has values in your report.
The {payout} macro in the Cost row wasn’t filled in by Traffic Nomads. Switch the campaign’s Cost Model to CPC and enter your bid. See Cost.
The macros were not replaced, usually because the URL was edited or pasted somewhere Traffic Nomads doesn’t process macros. Paste the campaign URL from ClickFlare unchanged. See Traffic Source Tokens Arriving Empty.
For the general checklist, see Conversions not showing.
FREQUENTLY ASKED QUESTIONS
Q1: Can I use the same Traffic Nomads traffic source for all my Traffic Nomads campaigns?
A1: Yes. The postback is set once on the traffic source and every campaign using it sends conversions the same way. Create a second Traffic Nomads traffic source only if a campaign needs a different postback, for example a different event setup.
Q2: What’s the difference between {click_id} and {external_id}?
A2: {click_id} is the ID ClickFlare gives each click. You send it to your offer, and the offer sends it back to ClickFlare. {external_id} is the ID Traffic Nomads gave the click, stored by ClickFlare. Postbacks to Traffic Nomads always need {external_id}.
Q3: Why does the postback send pubid?
A3: It tells Traffic Nomads which publisher the conversion came from, alongside the click ID. ClickFlare fills it from the Pub ID tracking field captured on the click.
Q4: Should I use Redirect or Direct tracking with Traffic Nomads?
A4: Redirect is the usual choice and works with every format. Use Direct only if Traffic Nomads must see your lander’s domain as the destination. See Direct Campaign Tracking.
Q5: Does ClickFlare pull my Traffic Nomads spend automatically?
A5: No. There is no Traffic Nomads cost integration in ClickFlare. Use the template’s cost row if it fills in, or the CPC cost model, and correct gaps with a manual cost upload.

Traffic source postbacks

Every token you can use in a postback.

Custom conversions

Split registrations and deposits into separate events.

Cost models

How CPC, CPA and RevShare costs are calculated.

Conversions not showing

The general checklist when postbacks don’t arrive.