FunnelFlux is an advertising tracking platform.

Thus you’ll need a source of advertising i.e. users clicking on ads of some type, before you can make anything start moving.

This could be Facebook, display/banner ads, a mobile DSP, Google Adwords or links used in blog posts. Either way, we need to configure each “source” in FunnelFlux individually so that we can categorise the incoming traffic.

Head over to the Sources > Traffic Sources section and click [New Traffic Source]. 

You should see a dialog like this:

Here you can use a pre-existing template supplied by us for commons sources or create your own.

Let’s run through the different sections:

  • Name - we’ll let you handle this one
  • Cost type - here you define how your traffic source bills you. Usually it will be cost per entrance (CPE), i.e. cost per each person entering FunnelFlux - a clicker. The other option, CPA, is rare and occurs for traffic sources that bill you only when your traffic converts. We do not recommend putting a default cost here.
  • Tracking fields - a lot of tracking is based on passing data in querystrings e.g. ...page.html?name=bob&age=27&location=US. Here we are configuring the default structure we want to use for a specific traffic source.

    What you do here is up to you and should be based on what information you would like to pass from your traffic source to FunnelFlux, and likely what dynamic parameters (macros, tokens, etc.) you are able to use for that source. For those you will need to consult your traffic source documentation.

    For sources which have no dynamic tokens, we recommend setting up fields like creative, campaign, and so on, then putting "REPLACE" in each of the second boxes -- this will make your FunnelFlux URLs for this traffic source have obvious REPLACE placeholders that remind you to change them manually later.
  • Fire conversions back to the traffic source - this area will depend on your traffic source and whether it supports conversion tracking, and whether you would like to turn this on. The most common type of conversion tracking with advertising platforms is postback URL tracking, where you need to pass unique click IDs from your traffic source to your tracker and later send these back to acknowledge a conversion happening.
  • Postback type - In the case of using a postback, you will likely need to pass a unique tracking ID from your traffic source to FunnelFlux, then automate passing of this stored value back to the traffic source. For example, if the traffic source uses the unique token %clickid%, you may configure the traffic source with this field:

Then, in the postback field, you would pass this back using the corresponding FunnelFlux token for the custom “uniqueid” field. Any custom field you create for a traffic source has a FunnelFlux token of {trackingfield-fieldname}, in this case, {trackingfield-unqiueid}, i.e.

Once finished, save your traffic source. 

This configuration is dynamic - you can change at any time and the links FunnelFlux generates will update. 

Keep in mind that if you remove existing fields and change the custom field configuration, links you previously created may now have an incorrect format that results in FunnelFlux dropping data.

For example, you have the custom field “adID = something”. You later delete this field. Existing links that may still be passing data under the adID parameter would still work, but the data would no longer be logged as FunnelFlux is not expecting this parameter anymore.

Did this answer your question?