New Conditions Editor

We have rolled out a significant improvement to the UI and UX of 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.

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

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

We consolidated our category APIs to a single canonical endpoint rather than a category path under every asset.

The new V2 conditions specify a route ID alongside route names as well as a priority key, which sets the ordering that they're processed by the edge.

For route ID we suggest using our ID generator and creating IDs like . However you can also give them semantic names. They are limited to 64 characters.

Funnel data now refers to these route IDs explicitly for which connections map where.

We have updated our API docs accordingly.

Please review them if you are creating funnels via API. Note the old format will still work but we would highly recommend moving to V2 conditions, as they are less brittle and easier to manage.