Follow up on the latest improvements and updates.


custom events
We have FINALLY released the long-awaited custom events feature.
You can now find information on these in the tracking codes area, set aliases under system settings, and can see our help article here.
This is an initial release so not all aspects are finished, but you can now:
  1. Send 1-10 custom events back to FunnelFlux via postback URL and JavaScript
  2. Send optional revenue with those events
  3. Set aliases for use in the reporting UI
  4. In all reporting pages, you can see custom event count, event revenue, completion rates per visit, revenue per custom event, and cost per custom event
We have some upcoming further changes to complete custom event implementation:
  • Ability to set postbacks for each one in traffic source conversion tracking (an obvious feature that we should release in the coming days)
  • Ability to trigger custom events in the funnel builder as users perform an action
  • Ability to upload custom events via API much like conversions
  • Addition of custom events to the raw events reporting
  • Adding total revenue columns to reporting to sum all revenue sources, and updating ROI/P&L metrics to use these as well (right now, "revenue" is actually
    revenue only).
Please note custom events have the following limitations:
  1. Custom events can only happen once per user. Our current database design prevents duplicates of custom events. We intend to change this in the future, as we feel there's many scenarios where you want to send custom events multiple times.
  2. Custom events cannot pass unique transaction ID data
  3. You can only trigger custom events using their number when using postbacks/JS. We won't allow triggering by alias (e.g. event_name=lead), because if you ever changed aliases in our UI you could break existing events or make them switch to new event columns in our database, fragmenting your data.
Other important changes
In order to make custom events more convenient, we also made a significant change to our hit design.
Previously, only hits (views) to offers could convert. We have now made it possible for all page view events to convert, i.e. lander views as well.
Other fixes/updates
  • We added a "disable VID append" feature to data passing. This is for rare cases where VID may break a downstream system and you want to disable our auto-appending of it on redirect
  • We have added some initial logics to prevent excessive sessions sizes, which is happening to some odd traffic originating from TikTok/Pangle (we think somehow they are caching cookies across users and causing the same VIDs to get used when they should not)
  • We have updated various API schema to use new restrictToMetrics associated with custom events
  • Improved some issues with reporting which were causing updated asset changes to not reflect in the UI (e.g. you delete an asset, it reappears).
We've made a number of small changes and additions as below:
  • We have added a
    prefix that you can use with cost tokens for when a CPM bid value is passed, rather than a cost per click. Thus if cost is passed as
    , our system will take
    value / 1000
    as the incoming cost. See documentation here.
  • We added currency conversion to our Facebook Ads UI, which will note if your account is not in USD and will convert spend values to USD if so (thus, we are assuming your FunnelFlux revenue reporting is in USD). We plan to add this to the Google UI shortly as well.
  • The FB app is still going through approval hurdles with Facebook (they are a bit ridiculous) but can be readily used by reaching out to us to be added as a tester
  • We now have encode/encrypt functions you can add to tokens for when passing data to a page (e.g. an affiliate offer). Available functions are base64, bin2hex, rot13 and md5. Only the latter is irreversible, the others are encoding not encrypting. You can see our documentation here.
  • Patched the 404 URL in system settings, which was failing to redirect as expected
Bug fixes
  • Fixed an issue with URL tracking field filters
  • Fixed a datepicker issue on the dashboard that was crashing the app
  • Improved our memory caching in our edge servers to better handle extremely large assets, such as funnels with a huge number of nodes
  • Fixed an issue with unique metric calculations
  • Fixed an issue stopping funnels/funnel groups from archiving and unarchiving correctly
FB UI released
We have now released another integrated reporting UI, this time for Facebook/Meta.
It functions in the same way as the Google UI -- you can connect your FB user via the sign in button, then choose from your ad accounts and corresponding FunnelFlux traffic source to do data merging.
Right now this is the initial release, so we have not yet added breakdowns or status changing via the UI - but these will come soon.
We have also released a number of small reporting fixes:
  • Reverted our heatmap reporting to an old method which calculated cost correctly per node
  • Patched an issue that was causing unique metrics to recalculate and be incorrect on expanding your tree data in reporting
  • Fixed CPM/CPC/CTR not working properly in the Google Ads UI
Google Ads UI improved
We're working on our integrated UIs and making them more awesome. Google is the guinea pig for this with more to come -- our Facebook UI is almost ready.
Here's what we have added to the Google UI:
  • The UI has been simplified to put setting in a side panel
  • You can now choose to break down by search keywords (at the campaign or ad set level)
  • You can now see the status of assets/keywords
  • You can filter to show assets by their status
  • You can also pause, resume and delete all assets, including keywords, from the FunnelFlux UI
With these changes the UI is much more useful and lets you analyse keywords directly, as well as take optimisation decisions.
We intend to add some other breakdowns later, but felt keywords were the most important for users.
Other UI updates
  • Improved our integrations area. We intend to add sections here to manage the ad accounts you have connected with our upcoming reporting UIs
  • Improved some aspects of the billing page, including how it shows event data
  • Fixed some issues with the CSV-based cost updates function, which broke when column names didn't match traffic source URL tracking field names by case
  • Fixed a few UI bugs
Backend updates
  • Made various improvements to how well redirects were handled while under high load and when autoscaling was in progress
  • Fixed an issue that was causing invalidations of asset updates (e.g. changing a funnel) to not propagate, because of odd data created by API users 😅
  • Patched a JS issue that was causing the JS improvement of tracking to underpeform
  • Fixed some reporting issues that were causing some queries to fail, or return the wrong visitor counts
Google Reporting UIs
We are working on some new
integrated reporting UIs
that pull data from a traffic source and merge it with FunnelFlux data in one table.
The benefit of this is being able to show accurate ad spend data, alongside things like ad impressions, clicks and CTR.
You can find our help documentation here.
We intend to expand this further in the future with breakdowns e.g. keyword -- and likewise for other sources we add. We intend to add Facebook, TikTok and Microsoft Ads in the short-term.
The feature is currently in beta, feedback welcome!
We have added a beta feature for generating links that rotate keywords, specifically for search arbitrage.
This feature currently uses your own Cloudflare Worker to accomplish rotation, though this is easy to set up, you copy/paste code we provide, and the costs are low.
We plan to internalise this feature in the future but wanted to provide a solution for users as soon as possible.
You can find the feature under the Labs section.
We have released several new metrics that are available on the reporting page - under the "Flow Metrics" tab.
These new metrics calculate visitor percentages and conversion rates relative to the top of the table tree, and the immediate parent.
They will be extremely useful for understanding conversion rates in visitor journey reports.
See our documentation here for more info.
You can now upload cost data from a CSV in the Update Costs section.
This should streamline regular cost updates, and this also allows updating over multiple dates in one upload.
Currently you'll need to rename headers in the CSV file to match tracking fields you are segmenting by, and clearly label the cost column.
Uploads are limited to 5000 rows at this time.
In the future, we plan to add templates for common traffic sources so that you can directly upload their exports without manipulation.
You can check our help documentation for more info.




Reporting improvements

We've done a bit of refactoring of the reporting page to make it perform better, and have rolled out some new features/updates recently.
See the list below for the changes.
New features
  • Custom tracking fields are now available by ID, which will let you group across traffic sources by c1 -> c2 -> c3 and so on
  • The restrict data feature (the filter button in reporting) now lets you apply global filtering based on attributes, separate to what might be included in your report. This will let you filter all data to e.g. United States only, without needing to group by country in reporting first. These filters let you both include and exclude
  • The restrict data settings and inline filters are now included in your saved view config -- making saved views much more useful for your frequent reports
  • The "open in reporting" button from quick stats now applies global filters, so the reporting page loads the exact data expected
  • The funnel builder now uses better reporting queries for heatmaps, which should lead to less discrepancies
  • Improved the ROI highlighting styling in tables
  • Fixed the styling of heatmap stats data to be more friendly
  • Fixed poor styling with hiding of the graph on the dashboard
  • Fixed a minor billing issue that was causing some user's usage overages not to sync (and therefore display correctly in the UI)
We have now migrated to our new billing model and have released changes to our manage subscription page, allowing you to see clearly what your event usages are and any billing.
The domains page has also been updated to correctly update domain addons as you add and remove them. These changes are pro-rated so you don't need to worry about getting overcharged -- you are charged for as long as a domain is in use. If you remove one, credits for the unused time are added to the account, impacting your next billing.
We have also added the duplicate node function, CPVi/RPVi metrics, and updated reporting to allow restrict data filtering to be applied globally to any report -- useful if you want to filter to only specific data (e.g. country = US, even though you are not using country in the groupings).
Load More