Articles on: Getting Started

Launch Your Campaign and Test

You have built your funnel, configured your traffic source, and added your pages and offers. Now it is time to go live. This guide walks you through getting your tracking links, launching on your traffic source, and testing the full flow end to end.


Pre-launch checklist

Before you send any traffic, confirm that each of these items is in place:

  • [ ] Custom domain added and verified -- active in Settings > Domains with valid DNS
  • [ ] Traffic source created -- tracking fields configured (especially campaign and external) and conversion postback URL set up
  • [ ] Offer source and at least one offer added -- correct offer URL and data passing configured
  • [ ] Landing page added -- FunnelFlux JavaScript snippet installed and action links working
  • [ ] Funnel built and saved -- all nodes connected and traffic source entry point defined


If anything is missing, set it up first. Testing an incomplete funnel will produce confusing results.


FunnelFlux generates tracking links inside the funnel builder. These links are dynamic -- you can generate them at any time.


Click the traffic source node in your funnel builder, select the source, and FunnelFlux generates a redirect link:



Copy this link and paste it as the destination URL in your traffic source. These links are generated on the fly -- the "save" and "discard" buttons in the funnel builder apply to node settings, not to the generated links.


If your traffic source does not allow redirects, click a page group node and switch to the direct link / JS tracking tab. Direct links have two parts: a base page URL and a tracking suffix.


For Google Ads, set the Final URL to your landing page and paste the tracking suffix into the Tracking template:





When a user clicks your ad, the traffic source combines the base URL and suffix -- the same result as the "Full direct URL" shown in FunnelFlux. Since direct links skip the tracker, features like server-side split testing are not available.


Setting up the campaign in your traffic source

With your link ready, go to your traffic source and create a new campaign.


For redirect links: paste the FunnelFlux redirect link as the destination URL, then configure your bid, targeting, and budget. The dynamic tokens in the URL should already be correct if you used a template.


For direct links: set the Final URL to your landing page address and add the tracking suffix to the Tracking template or URL suffix field. Then configure bid, targeting, and budget.


Do not launch to a wide audience yet. First, test it yourself.


Testing in incognito -- step by step

Always test your tracking before spending real money. Here is a reliable process.



Step 1: Open an incognito window

Use an incognito or private browsing window. This ensures you start with a clean session -- no existing cookies or cached data that could interfere with the test.


Paste your redirect link (or full direct URL) into the browser address bar and hit enter.


What to check:

  • Did the page load correctly? For redirect flows, you should land on your lander or offer after a brief redirect through your tracking domain.
  • Does the URL look right? Redirect flows should show a vid parameter on the landing page URL. Direct links should show the FunnelFlux tracking parameters.
  • If the page did not load, double-check your domain configuration, funnel connections, and page URLs.


Step 3: Click through the funnel

If your funnel includes a lander, click the call-to-action on your landing page. FunnelFlux should redirect you to the next step -- typically your offer page.


What to check:

  • Did the action link take you to the correct offer page?
  • Are data passing parameters in the offer URL populated with real values (not raw tokens like {hit})?
  • If the click does nothing, verify the FunnelFlux JavaScript is installed on your lander and the action link path is correct (e.g., /action/1).


Step 4: Verify data in FunnelFlux reporting

Open the Dashboard or Report Builder in FunnelFlux. You should see:

  • 1 visit -- from clicking the tracking link
  • 1 view -- the page load for your lander (or offer)
  • 1 click/action -- from clicking through on the lander


If you see visits but no views, your JavaScript may not be loading. If you see views but no clicks, check your action link configuration.


Step 5: Test conversion tracking (if applicable)

If your funnel includes conversion postbacks, verify the full loop:

  • Fire a test postback manually -- copy the postback URL from your offer source, replace the tokens with real values from your test click (like the hit ID from the offer URL), and open it in a browser or send it with curl
  • Complete a test conversion -- if possible on the network side, trigger a test conversion so the network fires the real postback


Check FunnelFlux reporting for a conversion event tied to your test visit.


Step 6: Repeat

Close the incognito window, open a fresh one, and run through the flow again. This confirms the experience is consistent. If your funnel uses split testing, you may land on different pages each time -- this is expected.


Key metrics to monitor post-launch

Once your campaign is live, these are the core metrics to watch:

  • Visits -- total traffic arriving at your tracking link
  • Views -- page loads confirmed by the JavaScript on your pages (should be close to visits; a large gap may indicate JS issues)
  • Clicks / Actions -- users clicking through from one step to the next (e.g., lander to offer)
  • CTR (Click-Through Rate) -- percentage of visitors who click through from your lander (clicks / views)
  • Conversions -- conversion events received via postback or other tracking methods
  • Revenue -- total revenue from conversions (if revenue values are passed in postbacks)
  • Cost -- total spend (if cost tracking is configured via dynamic tokens or manual entry)
  • Profit -- revenue minus cost


Use the Dashboard for a quick overview, or the Report Builder for detailed breakdowns by traffic source, campaign, page, country, device, and custom tracking fields.


Cross-checking with network reporting

Your FunnelFlux data will never match external reporting systems exactly. Small discrepancies are normal. Here is what to look for.


Offer views vs. network clicks: Compare offer views in FunnelFlux with the click count in your affiliate network. Expect the network count to be lower -- typically 80-95% of what FunnelFlux reports. Networks apply their own filtering and deduplication, and slow redirect times cause some visitors to drop off.


Conversion counts: These should be close between systems. If FunnelFlux shows fewer conversions than the network, check your postback configuration and data passing. If FunnelFlux shows more, this may indicate duplicate postback firing.


Traffic source clicks vs. FunnelFlux visits: The traffic source typically reports more clicks than FunnelFlux records as visits. Not every click completes the redirect -- users may close the browser or be filtered by bot detection.


Subid verification: Check the subid breakdowns in your network's reporting. If you see raw tokens like {hit} as literal text, your data passing is not resolving -- check the offer URL configuration in FunnelFlux.


If conversions appear in the network but not in FunnelFlux, the issue is almost always either the hit ID not reaching the network, or the postback URL on the network side not being configured correctly.


Next steps

With your campaign live and data flowing, you are ready to start optimizing. Use FunnelFlux's reporting to identify which traffic segments, creatives, and landing pages perform best, and adjust your campaigns accordingly.

Updated on: 05/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!