Skip to main content
Galaksion traffic source template Galaksion is a self-serve ad network selling push, in-page push, popunder, native and interstitial traffic. You can buy it on CPC, CPM or CPA, and its CPA Goal tool optimizes CPC and CPM campaigns toward a target cost per conversion. This guide sets up Galaksion as a traffic source in ClickFlare. It covers passing Galaksion’s click data into your reports and sending conversions back to Galaksion so its optimization has data to work with. You do everything from the campaign editor. The Galaksion traffic source is created inline, without leaving the campaign.

​
At a glance

​
How it works

1

Galaksion sends the click

A visitor clicks your ad. Galaksion opens your ClickFlare campaign URL and fills in its macros: the click ID in click_id, the cost in cost, plus the zone, campaign and creative.
2

ClickFlare stores the Galaksion click ID

ClickFlare saves the value of click_id as the visit’s External ID, records the cost, and redirects the visitor to your lander or offer.
3

The conversion reaches ClickFlare

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

ClickFlare posts it back to Galaksion

ClickFlare fires the Galaksion postback. It replaces {trackingField2} with the campaign ID captured on the click and {external_id} with the stored Galaksion click ID. Galaksion uses cid to identify the campaign and the click ID to match the original click.
The mirror to keep straight: in the campaign URL you write ClickFlare’s parameter (click_id) and Galaksion’s macro for the click ID. The template does this for you. In the postback URL you write Galaksion’s parameters (cid and click_id) and ClickFlare’s tokens ({trackingField2} and {external_id}). The template does this for you too.

​
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 its affiliate network set up to post conversions back to ClickFlare. See Creating an Offer and Adding an Affiliate Network.
  • Get your Galaksion postback URL. In Galaksion, go to Campaigns and click the Postback button. Copy the URL from the popup and check its cid value. Step 2 explains what to do if it is a fixed value.
  • Set up the postback before launch if you buy CPA or use CPA Goal. Both run on the conversions Galaksion receives.
  • Decide which conversion Galaksion should receive. If your funnel has several steps, for example a registration and a first deposit, choose the one Galaksion should optimize on.

​
Step 1 – Create the campaign and the Galaksion traffic source

  1. Go to Campaigns and click New.
  2. In Traffic Source, open the dropdown and click + New Traffic Source.
  3. Type galaksion in the search box and select the Galaksion template.
  4. Enter a Name, for example Galaksion.
  5. Leave Cost currency on USD unless your Galaksion account is billed in another currency.
The template fills in the Parameters table for you: The Galaksion template's Parameters table in ClickFlare, with Galaksion's macros pre-filled Each tracking field becomes a column you can group reports by. The Source row is the one you will use most. It carries the zone ID, not a source name. Zones are where Galaksion’s traffic comes from, so this column tells you which zones convert and which to exclude.
The template writes the click ID macro as [:click_id] and the other macros in curly braces. Before you launch, check the macro list Galaksion shows when you create a campaign. If Galaksion’s click ID macro is written differently, replace the TS Token in the External ID row with Galaksion’s version. Without a real click ID in click_id, Galaksion cannot match any conversion.
Galaksion’s own tracking guide for iGaming offers writes its macros as {zone_id}, {campaign_id} and {creative_id}. The template uses {zoneid} and {cid} for the first two. If the Source or Campaign ID column shows the macro as text after launch, replace those TS Tokens with {zone_id} and {campaign_id}. To pass more Galaksion data, click Add Parameter, give it a name and parameter, and enter the Galaksion macro as the TS Token. ClickFlare assigns the next free tracking field. The same Galaksion guide also lists {device} and {os}. Check the macros your Galaksion account offers before adding them.

​
Step 2 – Set up the postback

The postback is what sends conversions to Galaksion. It lives on the traffic source, so every campaign that uses this Galaksion traffic source sends conversions the same way.

​
Get your postback URL from Galaksion

  1. In Galaksion, go to Campaigns.
  2. Click the Postback button.
  3. Copy the postback URL from the popup.
Galaksion’s postback has this format:
cid identifies you to Galaksion. click_id is the click ID Galaksion passed in the campaign URL.

​
Add it to the traffic source in ClickFlare

  1. Back 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 Galaksion template's postback
  1. Compare it with the URL from the popup. If Galaksion’s URL has extra parameters, keep them.
  2. 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.
  3. Click Save. You are back in the campaign editor with the Galaksion traffic source selected.
cid carries {trackingField2}, the Campaign ID row from Step 1. ClickFlare captures the {cid} macro on the click and sends it back in the postback.
If the postback settings in your Galaksion account show a fixed cid value for your account, use that value instead of {trackingField2}.
The postback sends no payout. Galaksion’s documented format has only cid and click_id. If the URL in your Galaksion popup includes a payout parameter, keep it and fill it with ClickFlare’s {payout} token. 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 to Not Tracked, so ClickFlare uses the cost Galaksion passes. See Cost.
  3. Choose Redirect or Direct tracking. Redirect is the usual choice for push and popunder 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 Galaksion macro from the template, for example click_id=[:click_id] and source={zoneid}. If you use a lander, its call-to-action must link to the ClickFlare click URL, not to the offer directly. Otherwise the visit reaches the offer without a ClickFlare click ID, and the conversion cannot be traced back to Galaksion. See Creating a Campaign in ClickFlare.

​
Step 4 – Create the campaign in Galaksion

  1. In Galaksion, go to Campaigns and click Create Campaign.
  2. Paste the ClickFlare campaign URL into the Link field.
  3. Choose the ad format, targeting, pricing model and bid as usual.
  4. Submit the campaign.
New Galaksion campaigns go to moderation. Start the campaign only after it is approved. Paste the URL exactly as ClickFlare gives it. Galaksion replaces each macro when the ad is clicked.

​
Step 5 – Test the integration

Galaksion’s own guidance is to check that the postback works before the campaign goes live.
  1. Launch the campaign with a low budget, or wait for the first approved clicks.
  2. In ClickFlare, open the campaign report and group by Source. Real zone IDs, not {zoneid}, mean the macros are being replaced.
  3. Open a visit and check its External ID. A real value means the click ID macro works. [:click_id] as text means it doesn’t. See the Warning in Step 1.
  4. Complete the offer the way a real visitor would, or wait for the first real conversion.
  5. In ClickFlare, go to Logs → Postback Status and filter by the campaign. A successful request to postback.report confirms ClickFlare sent the postback. Check that the logged URL contains a real campaign ID in cid and a real click ID in click_id.
  6. In Galaksion, check the campaign’s statistics. The conversion should appear there too.

​
Sending only one event

Galaksion’s postback format has no event parameter. Galaksion recommends tracking at least one key event, such as a registration or a first deposit.
Map the postback to the event Galaksion should optimize on, for example an ftd custom conversion. Earlier steps still show in ClickFlare. They just don’t reach Galaksion.For CPA buying and CPA Goal, the event you send is the one Galaksion counts as a conversion.
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 passes cost per click. The cost row sends the {cost} macro, and ClickFlare records the value as the visit’s cost. On the campaign, set the Cost Model to Not Tracked so ClickFlare uses the cost passed in the URL.
Compare the Cost column with your Galaksion spend after launch. If {cost} arrives empty or as text, or the numbers don’t match, switch the Cost Model to CPC and enter your price per click. On CPM campaigns, enter your CPM bid divided by 1,000 as the cost value.
For Galaksion CPA campaigns, set the Cost Model to CPA, with your price per conversion. The template has no cost integration attached. When the recorded spend differs from your Galaksion spend, correct it with a manual cost upload. See Cost Models.

​
Delayed revenue

If you run search arbitrage (RSOC or AFD) behind Galaksion, the feed reports revenue hours or days after the click. Galaksion’s postback carries no payout, so delayed revenue doesn’t change what Galaksion sees. You can still send the conversion once it arrives. See Sending Delayed Revenue to Traffic Sources.

​
Troubleshooting

  • cid is empty or shows {cid} as text in Logs → Postback Status. The Campaign ID column had no real value on the click. See the Source or Campaign ID question below.
  • Your Galaksion account shows a fixed cid value. Use it instead of {trackingField2}.
  • Traffic source postback URL is off on the Galaksion 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: the logged URL shows exactly what ClickFlare sent.
Galaksion didn’t replace the click ID macro. Check the macro list in your Galaksion account and put Galaksion’s click ID macro in the TS Token of the External ID row. Then copy the campaign URL from ClickFlare again and update it in Galaksion.
Galaksion didn’t recognize {zoneid} or {cid}. Replace them with {zone_id} and {campaign_id}, the spelling in Galaksion’s own tracking guide, then update the URL in Galaksion. See Traffic Source Tokens Arriving Empty.
  • The campaign’s Cost Model is not Not Tracked, so ClickFlare ignores cost.
  • {cost} arrived empty. Use the CPC Cost Model with your bid instead.
For the general checklist, see Conversions not showing.
FREQUENTLY ASKED QUESTIONS
Q1: Is cid in the postback my Galaksion campaign ID?
A1: In the template, yes. cid carries {trackingField2}, the campaign ID Galaksion’s {cid} macro sent on the click. If the postback settings in your Galaksion account show a fixed cid value for your account, use that value instead.
Q2: Can I use the same Galaksion traffic source for all my Galaksion campaigns?
A2: Yes. The postback sends the campaign ID captured on each click, so one postback works for all of them. Create a second traffic source only if a campaign needs a different postback, for example a different event.
Q3: Why doesn’t the postback send payout?
A3: Galaksion’s documented postback has no payout parameter. Galaksion counts conversions. Your revenue and ROI stay in ClickFlare.
Q4: Should I use Redirect or Direct tracking with Galaksion?
A4: Redirect is the usual choice and works with every format. Use Direct only if Galaksion must see your lander’s domain as the destination. See Direct Campaign Tracking.
Q5: Does the template work for Galaksion’s CPA and CPA Goal campaigns?
A5: Yes. Both depend on the conversions Galaksion receives. For CPA buying, set the campaign’s cost model to CPA in ClickFlare.

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.