Discount FunnelFlux Pro | 14 Day Trial & 50% Off 1st Month

[Zeno (FunnelFlux)]

Tag nodes are around the corner and we have lots of UX improvements to roll out just before that.

You'll see more info on tag nodes soon -- they are one of the first new node types we are rolling out over the next few months.

Here are some of the sleek UX improvements we have made. Much of this came from realising some users encode a lot of info into names of pages, and searching can get iffy with 1000's of assets with complex names. Not anymore!

Funnel Builder​

The node palette has been updated so that you can better see the category/source of pages when searching and adding them. You can also filter to a specific category to refine your search

Long names are handled better with two lines + truncation and a tooltip of the full name on hover. Canvas nodes have similar new tooltips.

In page groups, the add page drop-down is now a more detailed selector that lets you quickly add multiple pages matching your search:

The page list inside of page groups has been revamped to better show the full names, the page category, and offer source if it's an offer:

This page settings area also has a new sort drop-down which lets you conveniently sort the entire list by name, category, or rotation weight.

We also recently rolled out a new "big nodes" toggle that allows showing longer names on nodes.

General UI Improvements​

We noticed for users with very long asset names, there were multiple places where it got annoying. So have rolled out a number of tweaks:

Asset names in some lists were getting truncated to 100 characters. We have expanded this to 256 chars and set stricter validation on the frontend and backend to clamp asset names to this limit

In many assets, we have changed the name fields to expand to multple lines rather than scroll left to right, so that you can always see the full name. Have done the same for base URLs.

We also updated the duplication flow When duplicating an asset, we now disable tabs and state clearly what data can be changed -- this avoids cloning something then finding some changes were not saved

Notifications now have their width clamped

Some new validation to stop accidentally saving conditions with empty groups. These still functioned on our backend but would always evaluate to "no match".

Performance​

We made significant performance optimisations to the funnel canvas.

Especially if you have quite large funnels, you should find panning and dragging has become a lot smoother.

That's all for now, we will roll out tags this coming week.

 

[Zeno (FunnelFlux)]

Condition Node Updates​

We have rolled out a new UI for condition nodes.

Now it's much easier to manage multiple routes and create/manage the rules.

You can drag to reorder priorities of routes and can filter them. You can also copy the entire route, rule groups, and individual rules.

The route list shows what kind of operator you're using and the number of groups and rules.

Upgrading Existing Conditions​

All new conditions created within the Funnel Builder will use the new User Interface. However old ones can be transformed to use the new format by clicking the upgrade button.

Upgrading needs to change the condition and the funnel data so the upgrade is only persisted when you save the funnel.

Conditions were rather fragile before and prone to bugs. This improves this significantly. However please make sure to re-test any links after upgrading conditions, to make double-sure it's still behaving exactly as you expect.

Note it's not possible to upload **global conditions** because these are used across multiple funnels. The funnel data needs to change to complete the upgrade. It's not possible to trigger updates across all of the related funnels

New Condition Attributes​

We have added UTC offset as a new attribute you can route by. The current timezone attribute uses a large unhelpful list -- the UTC offsets help you match a broader set of users more easily. We plan to deprecate the old timezone attribute later.

We have updated the IP address attribute to allow specifying ranges as well as specifying wildcards to match.

For example, `123.123.X.X` will now match all IPs matching this format. This is only possible for the C and D range. Needing to match greater ranges is unlikely in practice.

Also the IP range option will limit you to similar ranges to prevent destructive rules.

So, IP specific filters are now a lot easier too.

Also, I can confirm for string entry type attributes like ISP, browser version, region etc. -- you can enter a comma separated list of values and it will use all of them separately (like adding separate rules for each individual value).

 

[Zeno (FunnelFlux)]

Tag nodes are now available in beta.

Tag nodes allow you to add and remove labels to users as they move through your funnel.

You can later make decisions in condition nodes based on whether someone has or does not have a tag. This works across separate funnels as well.

In reporting you will be able to see data broken down by tags too.

Tags can be added and removed through nodes in the funnel as well as via Javascript. You can create them from the Create Asset button or on the dedicated Visitor Tags page:

A few use cases to consider:

1. Tag a user before they go down a certain path or to a certain page, then use that tag in a condition to bounce them if they revisit - creating an "only once" path
2. Tag a user based on some action they take on a page. For example time spent on a page or answering certain questions in a quiz
3. Create some bot detection honey pot on a page and tag visitors who trigger it, labeling them as bot-like
4. Add tag nodes after complex condition routes to label them based on important routes they went down - making grouping easier in later reporting
5. As these are in beta, we appreciate your feedback on any issues you might encounter or reporting quirks.

Onward!

 

[Zeno (FunnelFlux)]

We shipped several updates to make organic tracking, referrer protection, cleanup workflows, reporting, and bulk event uploads easier to manage.

Spreadsheet Uploads for Conversions and Custom Events​

Conversion uploads now support spreadsheet-style batch workflows, including custom events.

You can upload rows for conversions and Custom Event 1 through Custom Event 10, with optional revenue, event data, timestamps, PII passthrough fields, and external dedupe IDs.

This makes it easier to import event data data in bulk, especially when you have timestamp overrides or a mixture of events.

Default Funnel Tracking for Pages​

Pages can now have a default funnel, node, and traffic source.

When a visitor lands on a tracked page organically, with no available context, FunnelFlux can detect the page URL and automatically attribute the visit to an appropriate default funnel context.

This makes organic tracking cleaner because you no longer need to embed defaults into specific page code - so this is an alternative to our fluxDefaults code embed.

This, along with UMR domain overrides, are available in page settings > advanced settings tab.

Ultimate Meta Refresh Domain Overrides​

Ultimate Meta Refresh now supports dedicated tracking-domain overrides on offers and offer sources.

This lets you route UMR offer bounces through a specific custom domain instead of the funnel's normal tracking domain.

It is useful when you want to protect primary tracking domains, isolate offer redirection behavior, or use a dedicated domain for referrer masking -- making it so that offer sources never see domains in referrers that are associated with your live tracking links ️

Offer-level overrides take priority over offer-source overrides.

 

[Zeno (FunnelFlux)]

We are excited today to launch webhook nodes in beta to all users.

Webhook nodes allow you to emit webhooks as users move through your funnel:

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 - Email 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.

We have also added webhook support to traffic sources in the conversion tracking section.

You can see our guiding document here and you can read our technical documents here that cover schema.

 

[Zeno (FunnelFlux)]

We have rolled out a useful QOL update with filtering.

Improved Automatic Filtering​

We have added ISP-based filtering to our pipeline that will automatically add a "filtered" flag to visits coming from ISPs that we have deemed as 100% non-human.

This in particular 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​

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.

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.