We have rolled out two new feature changes -- to rotators, and conditions.
Rotator Stickiness Settings
We've had a few requests in the past for "smart" rotation where you can make sure the same user always gets rotated to the same page -- or the opposite, where a user is always routed to a new destination if they visit the same rotator multiple times.
This affinity and anti-affinity logic is now available in rotator node settings:
Note this data is at the session level, so is limited by the session persistence. A user coming back after seven days will no longer have session data (even if we recover the session ID from cookies). So this functionality is aimed at repeat visitors within a short timeframe, e.g. in a 24 hour window.
Condition Node Updates
- Tracking field and referrer properties can now use the IS EMPTYandIS NOT EMPTYoperators
- This will allow you to more easily redirect users based on URL parameters being present or not, or having no value. Likewise with direct visits that have no referrer value
Domain API Updates
- Domains can now be managed via API directly, rather than only via the frontend.
- For users who need programmatic domain control this is likely very helpful news!
- Now, our backend domain API handles all the management of adding to our assets, Cloudflare, and updating billing. It will be relatively high latency when adding domains since it has to do all these processes behind the scenes (e.g. 5-10 seconds).
- We have updated our API docs here to reflect all our recent API changes
Billing systems improvements
- The billing page now shows better breakdowns of charges and estimates upcoming billing
- You can now trial addons for 14 days. As we roll out new addons this will become more important, allowing you to test functionality
- Cancelled and paused subscriptions should now show a reactivate button to resume normal billing
- Fixed an issue where overage were counting from 1 M instead of the included 2 M.
Upcoming Migrations
Just mentioning this now, and will mention again soon, but we are in the middle of migrating our entire assets database system and rolling out a new backend service for this.
Likewise, reporting V2, and soon will be migrating to a new auth system. These all enable us to move faster with development, improve performance, and remove some annoying historic issues.
We expect no downtime or issues, but like with all things, migrations can be complex and small bugs can appear, so we'll announce in advance and appreciate your patience with any things that pop up.