Add Your First Traffic Source

What is a traffic source?

A traffic source represents anything that sends visitors to your pages or marketing campaigns. This could be a paid platform like PropellerAds, Facebook, or Google Ads, or an organic channel like email or affiliates.

When you create a traffic source in FunnelFlux, you are telling the system three things:

1. Where traffic comes from -- so you can label and segment visitors in reporting
2. What URL parameters to expect -- so FunnelFlux knows which data to capture from incoming clicks
3. How to report conversions back -- so the traffic source can optimize delivery based on your results

Every funnel link you generate in FunnelFlux is tied to a traffic source. The source determines which parameters appear on the URL and how conversion data flows back to the platform that sent the traffic.

Creating a traffic source from a template

Navigate to Assets > Traffic Sources and click Create:

As you type, a list of templates will appear. Click any template tile to load its pre-configured settings, or click Create a custom source if your platform is not listed:

You can rename the source however you like. It is common to create multiple entries for the same platform -- for example, "Facebook (Account 1)" and "Facebook (Account 2)".

On General Settings, Category sits next to Cost Type and Default Cost per Entry. Category is optional (e.g. Social, Display, Push). Use Save & Create New if you want to create another source immediately after this one.

Example: PropellerAds

Let's walk through creating a source using the PropellerAds template. After selecting it, you should see something like this:

Notice how PropellerAds can pass cost dynamically using its {cost} token in the cost per entry field. Most traffic sources cannot pass real-time cost this way, but it is common for popup and push platforms. You can leave cost per entry blank if the traffic source does not support it.

Tracking fields

The tracking fields section defines the URL parameters FunnelFlux will append to your links. These parameters capture information from the traffic source about each click.

Reserved fields

The first two fields are reserved and cannot be removed:

• Campaign ID -- pass the traffic source's campaign ID here. This lets you break down reporting by campaign without manually tagging anything.
• External Click ID -- pass the traffic source's unique click ID here. This is critical for conversion postbacks, as it is the value FunnelFlux sends back to identify which click converted.

Each row has URL Parameter, Source Token, FunnelFlux Token, and an Append toggle.

Custom fields (c1-c20)

Beyond the reserved fields, you have up to 20 additional tracking fields. Use these to capture data you plan to analyze, such as:

• Publisher or zone ID
• Ad or creative ID
• Placement type

Each field has a URL Parameter (used in the URL), a Source Token (typically a dynamic token from the traffic source that gets replaced with real data at click time), and a FunnelFlux Token (e.g. {data-zone}) you can use later when passing that value to landers and offers.

For example, a PropellerAds link might end with:

...?campaign={campaignid}&external=${SUBID}&zone={zoneid}&country={country}

When a user actually clicks, PropellerAds replaces those tokens with real values:

...?campaign=98765&external=abc123def&zone=4455667&country=US

These values then appear in your FunnelFlux reporting under the corresponding tracking field columns.

Tip: You do not need to pass things like country, region, or device type through tracking fields. FunnelFlux detects these automatically from each visitor. Focus on passing IDs and dimensions that only the traffic source knows, such as campaign IDs, zone/publisher IDs, and click IDs.

Conversion tracking

Once FunnelFlux records a conversion, you need it to communicate that back to the traffic source so the platform can attribute the result and optimize. There are three methods available.

Postback URL

This is the most common method. A postback URL is a server-to-server request -- when a conversion happens, FunnelFlux sends an HTTP request to the traffic source's endpoint, passing the original click ID and conversion details.

The key tokens you can include in a postback URL are:

• {external} -- the click ID originally passed in via the external tracking field
• {payout} -- the revenue amount for the conversion
• {txid} -- the transaction ID associated with the conversion

For the postback to work, you must pass the traffic source's click ID into the external field on your tracking links. Without this, FunnelFlux has no way to tell the traffic source which click converted.

In the PropellerAds example, the template comes with a pre-filled postback URL [1]. You will see placeholder values like REPLACE_ME for account-specific IDs (such as aid and tid). Copy those values from your PropellerAds account's postback settings and paste them in.

Triggering Event [2] sits above Tracking Type inside Classic Event Tracking. By default this is set to "Conversions", meaning the postback fires when a standard conversion event occurs. You can also configure separate postbacks for custom events, which is useful when working with platforms like Meta, TikTok, or Google where you may want to send multiple event types. A Webhooks selector is also available on this tab.

Platform integrations (CAPI)

For Meta, TikTok, Google Ads, or Microsoft Ads, do not pick a Custom Scenario tracking type. Open the Integrations tab, pick the platform, then set Platform > Connection > Ad account. Map events under Conversion Tracking > Integrations.

These integrations handle conversion reporting for you without a manual postback URL.

For further guidance on available integrations, visit Settings > Integrations in your FunnelFlux account.

JavaScript (client-side tracking)

Some traffic sources require client-side tracking -- image pixels, iFrames, or JavaScript tags that load in the user's browser on a conversion page.

You can save HTML/JavaScript content alongside postback URLs, firing both when a conversion happens if needed. However, for client-side tracking to work, you must place the FunnelFlux conversion JavaScript on the page where the conversion occurs (typically a thank you or confirmation page).

In general, prefer server-side methods (postback URLs or CAPI integrations) over client-side tracking wherever possible. Server-side tracking is more reliable as it does not depend on the user's browser, ad blockers, or page load completion.

Advanced settings

Traffic sources include additional options for cost modifiers, revenue modifiers, and postback filtering. These are covered in the reference article: Advanced Traffic Source Settings.

Next steps

With a traffic source created, you are ready to add your landing pages and offers, then build your first funnel. FunnelFlux will use the traffic source configuration any time you generate links, ensuring the right parameters and conversion tracking are in place automatically.

Updated on: 15/10/2026