Articles on: Tracking Setup

Creating Custom Offer Sources

FunnelFlux includes templates for many popular affiliate networks and offer sources. However, if no template exists for the network you want to use, you will need to create a custom offer source. This guide walks you through the process step by step.


The core idea is simple: you need to figure out how the network structures its URLs and postback tokens, then map those to FunnelFlux's data passing and conversion tracking fields.


When you need a custom source

You need a custom offer source when:

  • The network or platform you work with is not available in FunnelFlux's built-in template library
  • You are working with a proprietary or lesser-known offer source
  • You want to understand the underlying mechanics of data passing (useful even if a template exists)


In most cases, setting up a custom source involves:

  1. Using the platform's link builder to understand the URL parameters they use
  2. Checking their UI or documentation, particularly to confirm if there is a specific field for unique click IDs
  3. Checking their postback/conversion tracking section for setting postback URLs, and finding the tokens they use
  4. Reviewing documentation for those tokens


Once you fully understand how this tracking works, it is straightforward to set up.


Step 1: Understand the network's URL structure

Start by going to the network's interface and using their link builder or offer URL generator. The goal is to identify the URL parameter names they use for passing data.


For example, take this affiliate network where we are generating an offer URL:



Here they have fields for adding "Sub IDs", a common name for extra URL parameters.


To test, add placeholder values (like "TEST") to these fields and observe how the tracking link updates. In this example, it produced:

https://afflat3e1.com/trk/lnk/F6FAF815-F539-4507-BC22-1593EC1A2A6E/?o=7527&c=918277&a=663127&k=4E135562644B11EB0D8C0ED3200EA953&l=6239&s1=TEST&s2=TEST&s3=TEST&s4=TEST&s5=TEST

From this URL, you can identify that s1, s2, s3, s4, and s5 are the parameter names this network uses for sub ID fields.


Key things to look for:

  • The parameter names (e.g., s1, sub1, aff_sub, clickid, etc.)
  • Whether there is a dedicated parameter for external click IDs
  • How many sub ID slots are available


Step 2: Set up data passing in FunnelFlux

Now that you know the parameter names, go to FunnelFlux and create a new custom offer source (Assets > Offer Sources > Create New > Create Custom Source).


In the data passing section, map FunnelFlux tokens to the network's parameter names. For the example above, the configuration would look like this:



The critical requirement: you must pass {hit} through one of the parameters that the network will store and return to you later via a postback. This is the unique tracking ID that FunnelFlux uses to attribute conversions.


In this example, {hit} is being passed through the s4 parameter. You can use any available sub parameter for this, but you must remember which one you chose -- you will need it in the next step.


Step 3: Find the network's postback tokens

Now you need to find the tokens (sometimes called "macros") that the network uses in postback URLs. These tokens let the network dynamically insert stored values when it fires a postback to FunnelFlux.


Go to the network's postback or conversion tracking configuration area. Look for a section that lists available macros or tokens:



Clicking "see available macros" reveals the tokens this network supports:



You need to identify:

  1. The token for the parameter where you stored {hit} -- In this example, we passed {hit} via s4, and the network's token for that value is #S4#. The token format varies by network (e.g., {{s4}}, #s4#, %s4%, {s4}, etc.).
  2. The revenue/payout token -- The token the network uses to pass back the conversion revenue amount. In this example, it is #RATE#.
  3. The transaction ID token (if available) -- A unique conversion identifier from the network's side, useful for deduplication.


Step 4: Configure conversion tracking

With the tokens identified, scroll down to the conversion tracking section of your offer source in FunnelFlux. Enter the network's tokens in the appropriate fields:

  • Hit ID token -- The network's macro for the sub parameter where you stored {hit} (e.g., #S4#)
  • Revenue token -- The network's macro for payout/revenue amount (e.g., #RATE#)
  • Transaction ID token -- The network's macro for their unique conversion ID, if available


This generates the correct postback URL:



Copy this postback URL and place it in the network's postback configuration. Ideally, set it as a "global" postback URL so it applies to all offers automatically, rather than needing to configure it per offer.


Full example walkthrough

Here is the complete process summarized with the example network above:

  1. Inspected the link builder -- Added test values to Sub ID fields, observed the URL produced parameters s1 through s5.
  2. Configured data passing in FunnelFlux -- Mapped FunnelFlux tokens to the network's parameters, making sure to pass {hit} through s4.
  3. Found the network's postback macros -- Checked the postback configuration section and found:
  • #S4# retrieves the value stored in sub parameter s4
  • #RATE# provides the conversion payout amount
  1. Configured conversion tracking -- Entered #S4# as the hit ID token and #RATE# as the revenue token. No transaction ID was needed for this network.
  2. Placed the postback URL -- Copied the generated postback URL from FunnelFlux and added it as a global postback in the network.


Tips and common pitfalls

  • Always verify which parameter carries {hit} -- If you pass {hit} through s4 but use the token for s3 in your postback, conversion tracking will not work.
  • Check token formatting carefully -- Different networks use different delimiters. A token might be {s4}, {{s4}}, #S4#, %s4%, [S4], or something else entirely. Copy the exact format from the network's documentation.
  • Use a dedicated click ID field when available -- Some networks have a specific parameter for external click IDs (e.g., clickid, externalid). If one exists, prefer it over a generic sub ID slot, as it may receive special handling.
  • Set postbacks globally -- Most networks allow a global postback URL that fires for all offers. This saves time and avoids missing conversions due to per-offer misconfiguration.
  • Test with a real click -- After setup, send a test click through the funnel and trigger a test conversion (if possible) to confirm the full round-trip works.

Updated on: 05/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!