Please note traffics sources may change their tracking options from time to time -- if this article is for any reason outdated or you find errors in it, please let us know.

Step 1: Add SourceKnowledge as a traffic source

Firstly, add SourceKnowledge as a traffic source. You can use our available template:

Under the tracking fields tab, you can see how we are templating data passing from this source. The settings here define the link that we will generate for use in your ads later:

Step 2: Configure conversion tracking

Note: our template already has conversion tracking set up, but we'd like to guide you through how you'd find this in the traffic source anyway.

Head over to SourceKnowledge, sign in and navigate to the reporting page.

You will need to create an advertiser first, then create a campaign.

Once you create a campaign, you're able to set the tracking URL, and they provide a link to their postback URL documentation.

In FunnelFlux in the traffic source settings, you can go to the Conversion Tracking tab. We already have something configured here:

On conversion, FunnelFlux will take the collected data for a user, such as a unique click ID, and fire this postback URL to the source.

Step 3: Setting up a campaign in SourceKnowledge

The last step is to wire everything together and run a campaign.

To do this, you'll need to create a funnel then generate an "entrance link" to use in your SourceKnowledge ads, which will point the user to your funnel, as well as pass data from the source.

Go to your funnel > click on the traffic node (assuming this is where you want to send users). Click on the Redirect Links tab and choose SourceKnowledge as the traffic source:

This will generate a URL to use in your ads, which will pass extra information that comes from the Configure Tracking Fields part of your traffic source config -- hopefully you may recognise some of the parameters that you saw earlier.

Take this URL and use it for your ads in SourceKnowledge, like so:

This URL is already set to pass click IDs for conversion tracking, as well as their "subid" token. We have not set it to pass other tokens as listed here...

...as most of these values are tracked automatically on our side anyway (e.g. IP/UA, which resolve to specific countries, cities, ISPs, etc.). There's generally little need to pass these from traffic sources unless ISP-level optimisation is critical.

Also note that when you generate links in the funnel builder, there is no need to save these.

Our links are fully dynamic and funnels can accept traffic at any time, from any source, to any point in the funnel. So when you close the sidebar > click the traffic node (or any node for that matter) > go to Redirect Links, it will always be empty and waiting for you to pick a source to create a link for.

This is often a point of confusion for users, as other trackers tend to create unique "campaign" links every time that have unique IDs. No need in FunnelFlux, just grab links whenever you need them.

Once you run a campaign on SourceKnowledge, be mindful to check if conversions are passing through. 

You can always manually convert an offer hit to test this, and can always debug/correct the configuration if there is an issue -- just reach out to our support if you need help.

IMAGE