Changelog

Follow up on the latest improvements and updates.

RSS

Data Mapping
Some traffic sources only pass IDs for campaigns or custom fields, so your reports show numbers instead of names.
You can now upload the names yourself. On a traffic source, open the Data Mapping section and choose which fields to map (campaign, Field 1, Field 2). Then go to Updates → Data Mapping and upload a CSV of IDs and names.
Screenshot_19
Reports then show those names wherever that traffic source's IDs appear. New uploads merge with the names you already have, and you can clear a field at any time. Names that come from a connected ad platform are never changed.
If a traffic source already syncs names from its integration, Data Mapping is off for it, since the integration already provides names.
Improved
Referring page in tokens and webhooks
  • Page redirect and postback URL pickers now include Referring Page ID and Referring Page Name tokens.
  • Referring-page tokens resolve to the page directly before the current one, even when other funnel steps sit between them.
  • Webhook payloads include the referring page ID and name at the top level. They are always present, and blank when there is no earlier page.
  • Action webhooks now report the page the visitor clicked on, even when a rotator sits between the action and the webhook.
One conversion route per traffic source
Traffic sources now keep an explicit Classic or Integrations conversion mode, so a conversion is never sent through both.
Webhook and integration logs
  • Integration logs now correctly obfuscate all credential values
  • Queue history keeps its delivery details when a queued item is merged or reopened.
Fixed
  • Google Ads accounts saved with dashes in their ID (123-456-7890) could fail to sync campaign names. All Google Ads syncs now accept both forms.
  • In the funnel builder, creating or editing a webhook from an action now opens the webhook panel in front of the action dialog, not behind it.
For developers
  • Webhook payloads now report
    schema_version
    "1.1"
    . If your receiver checks for exactly
    "1.0"
    , accept
    "1.1"
    too.
  • Funnel group API routes now accept and return
    idFunnelGroup
    and
    funnelGroupName
    . The older
    idCampaign
    /
    campaignName
    still work for now.
  • Data Mapping is also available through the Assets API. See the Data Mapping guide.
  • The webhook reference no longer lists a
    time_on_page
    field in the hit object. Webhooks never sent it.
New
Funnel Cleanup
Funnels that have been edited for a long time can carry many deleted nodes.
These are kept so that links pointing at them keep working, but they make large funnels heavier.
In the funnel builder, open Funnel Settings → Advanced Settings to see how many active, archived and deleted nodes a funnel has, and its saved size.
When a funnel carries a lot of deleted nodes, the card recommends a cleanup.
image
"Clean save" saves the funnel without its deleted nodes.
Short links or external pages that point directly at a deleted node will stop working after a clean save, so check those first.
Improved
Google Ads conversions without a click ID
Conversions that only carry PII identifiers, with no Google click ID, are now sent to Google Ads via the new integration (before this was intended, but not working correctly).
Google may not be able to match every one of these, so expect a lower match rate on them than on conversions with a click ID.
Cleaner traffic data
  • Bot traffic and hits marked to be ignored are now excluded from analytics for the whole visit, including the visitor's later page views and events. Server-to-server conversions are still recorded.
  • Traffic from Alibaba's various ISPs is now labelled as filtered traffic.
Support chat keeps your history
We found and identified a bug in the support chat that was causing chats to disappear over time. Support chat now stays with you after you log out and back in, and shows the same conversation on any browser or device you log in from.
Fixed
  • An action click could occasionally be recorded as coming from the previous page if the visitor moved on quickly. Clicks are now always attributed to the page they were made on.
  • Path tracing in the funnel builder no longer flickers when you move the mouse between nodes.
  • Funnel builder nodes have clearer borders in dark mode.
Updated Traffic Filtering
Traffic filtering is now one setting shared by the report builder, dashboard, asset reports, quick stats and campaign analysis. Filtered, known proxy and hosting traffic is hidden by default, and your choice is saved in your browser.
image
Manual cost updates no longer spread cost onto filtered, known proxy or hosting traffic by default. New options let you include that traffic when doing updates via API.
Improved
Dashboard Settings now has separate Chart Settings and Filtering tabs.
image
  • In Quick Stats, the combined URL Data report is now called All Fields and has its own icon.
  • Report filters for Connection Type, Device Type and Filtered Status now accept the display label or the ID.
  • Unknown values return a clear error, and the Unknown device filter includes visits with no device data.
Fixed
We found that some Facebook, Hetzner and Byteplus network traffic was not being filtered when it should have been. That traffic is now filtered, and we will update past traffic from those networks to filtered as well.
Integrations Improvements
  • Ad-platform sync and conversion delivery now report provider errors more precisely and handle very long retry delays safely.
  • Microsoft Ads conversion delivery now waits the time Microsoft asks for before retrying.
  • Google Ads conversion delivery is more resilient to network failures.
You can now connect your Meta, Google Ads, TikTok and Microsoft Ads accounts directly to FunnelFlux Pro.
Log in to the ad platform once under Settings > Integrations > Traffic Sources, link the ad account to a traffic source, and we take it from there: conversions go back to the platform, and costs and campaign names come into your reports.
Traffic Source Integrations settings with Google Ads, Meta, TikTok and Microsoft Ads connections
Send conversions to the ad platform
  • Map your conversions and custom events to platform events on each traffic source.
  • Pick your Meta or TikTok pixel straight from the connected account, and pick Google Ads and Microsoft Ads conversion goals from a list loaded from your ad account.
  • No more postback URLs, access tokens or custom scenarios to set up by hand.
  • If a connection expires or is disconnected, conversions are held and sent once you reconnect, within each platform's limit for late conversions.
A traffic source's Integrations tab, linked to an ad account
Event mapping from FunnelFlux conversions to platform events
Automatic cost data
  • Campaign spend is imported every hour for all four platforms.
  • Each finished day is checked again once the platform has finalised its numbers, so your costs match the platform's own reporting.
Campaign, ad set and ad names
  • Reports show the names from your ad account instead of raw campaign, ad set and ad IDs.
Cost sync and name sync settings for a Meta traffic source
Integration Logs
  • A new Queue view shows conversions waiting to be sent, such as Google Ads conversions during their 6-hour delay, and any that are held or failed.
  • Event Logs has clearer columns and filters, and shows "not mapped" when an event has no destination.
  • For Meta, the Included Data column shows which customer details were sent with each event.
Integration Logs Queue view with queued Google Ads conversions
Setup guides
Start with Using traffic source integrations, then follow the guide for your platform: Google Ads, Meta, TikTok or Microsoft Ads.
If you already send conversions with a custom scenario, it keeps working. We recommend moving to the native integration for cost sync, name sync and Integration Logs.
Other changes
  • Fixed a tracking issue where, with a visitor active in two funnels, lander views from one funnel could be recorded against an offer in the other.
  • Filters and view settings in Integration Logs and Postback Logs now stay as you left them when you navigate away and back, and the Success filter works correctly.
  • Page toolbars fit narrow screens instead of cutting off controls.
  • Billing: add-ons that aren't available yet are hidden, and inactive plans show as disabled.
ImprovednewUser InterfaceTracking

Middleware Nodes Pro

We have rolled out an upgraded tier to Middleware Nodes.
These come with increased timeouts, data passing options, and a new loading page feature.
Screenshot_1
With loading pages, you can create templates that display to users while middleware is processing.
These are hosted dynamically on our side, on the tracking domain, and help bridge long wait times from more complex middleware processes.
Other changes
  • Unified the apply/refresh button across the app to be simpler,
  • Reorganised the quick stats buttons/quick reports to be a little cleaner
  • A few small UI tweaks to make things nicer
We have now added incoming logs to the existing postback logs page:
Screenshot_15
Now you can review logs about the incoming postbacks you are receiving from offer sources and useful debugging info like:
  • The event types
  • Whether they validated or failed (and why)
  • The IP/user-agents sending the events
  • Revenue
This will make it much easier to debug why you might be missing conversions, and whether your postback setup is correct.
Middleware Nodes
Screenshot_2
  • Added Middleware as a new funnel node type, letting funnels call an external service during routing and continue based on the response.
  • Added Middleware Configs as a manageable asset type with categories, duplication, archive/unarchive, and move-category support.
  • Added route-based middleware behavior with default fallbacks, priorities, response conditions, and clearer validation when a route setup is invalid.
  • Added Middleware Logs and summary reporting so users can inspect executions, outcomes, destinations, timing, and routing decisions.
Page Group Categories
  • Added category support for global lander groups and offer groups.
  • Reporting can now group and filter these page groups by category, including consistent "Uncategorized" handling.
UI Improvements
  • Added Middleware creation, editing, picking, funnel-node placement, and reporting screens.
  • Improved Logic Script editor and form state behavior.
  • Fixed stale validation for webhook and visitor-tag nodes after adding an outgoing connection.
  • Added page-group category management in the UI.
Reliability and Accuracy
  • Fixed a streamer retry edge case that could publish identical duplicate events, improving conversion and revenue accuracy during retry bursts. This affected <0.1% of conversions. We will review removing old duplicates.
We are rolling out a really cool feature that we think a lot of technical users will really appreciate.
Logic Nodes
Screenshot_11
They are called Logic Nodes, which run a Logic Script:
Screenshot_12
You can now run Go-based edge code fragments to do complex routing in a single node.
For those of you with complex routing situations, where you want to route based on referrer patterns, ISP blacklists, zone IDs etc., you can now fully codify it and easily use AI to create highly functional routing scripts.
You can see me demonstrate below:
Our help docs are here, and detailed API docs here.
This includes prompt snippets/instructions to give AI to streamline creation.
Let us know what you think!
2FA Now Available
We have added support for enabling 2FA on your account to better secure user access.
It is available under system settings > login settings.
Screenshot_10
Improved Automatic Filtering
We have added ISP-based filtering to our pipeline that will automatically add a "filtered" flag to visits coming from an internal non-human ISP list.
This in paticular will reduce the amount of spammy visits you see from Facebook/TikTok review agents.
These visits get marked as "filtered" and can still be shown in the report builder later (see next section).
Right now, we have identified about 35 key ISPs that are high volume, across multiple countries, and meet various other criteria.
We will also be back-dating all analytics data to apply filtered status for these.
If you find certain ISPs in your own analysis that are problematic 100% of the time, please let us know.
Reporting UI/UX Improvements
Screenshot_32
Carrying on from the feature above, we have reorganised the report builder to make it a little cleaner, and have added a new settings area.
Screenshot_33
Here, you can toggle whether or not to show "filtered" data.
Additionally, you can toggle to hide visits where the connection type is Hosting Provider or Known Proxy.
These are usually annoying in stats data, so we have enabled this setting by default.
The entrance/event time attribution toggle has also moved here.
We are excited today to launch webhook nodes in beta to all users. These are available on all plan levels.
Webhook nodes allow you to emit webhooks as users move through your funnel.
Screenshot_25
These webhooks can go to third-party systems like Zapier, Make.com, or n8n to automate workflows and trigger events in other systems.
A simple use case for marketers... E-mail submits!
Now you can create any style of form you want on a page to capture user data, then submit that data directly to your funnelflux action link.
The webhook node can then handle sending that to a system like Zapier where you can connect the data to any email system. No more clunky email provider forms in your landers, complete flexibility.
Running some sort of survey? Push the answers to FunnelFlux, then send the results on the side to a webhook that writes data to a Google Sheet or database for later analysis.
Doing host-and-post? Push the data to FunnelFlux and then to your own function that handles pushing it by API to some third-party.
The accessibility and ease of AI-assisted coding makes this easy, and lets you use FunnelFlux to orchestrate your flow of data.
This is one of the first steps towards my vision of FunnelFlux becoming not just a tracker, but a powerful funnel orchestration platform.
In addition to the nodes, you can trigger one or more webhooks on action connections -- much like you can for conversions and custom events.
webhook_on_action
We have also added webhook support to traffic sources in the conversion tracking section.
Screenshot_26
You can see our guiding document here and you can read our technical documents here that cover schema.
Happy tracking!
Zeno from FunnelFlux
Load More
→