Customer tags are most useful when they're accurate and up to date. We've made significant improvements to auto-tagging, giving you much more control over when and why a tag gets applied.
You can now set flexible time periods for tag triggers - either fixed date ranges (for example, "purchased between 1 January and 31 March") or rolling windows ("purchased within the last 45 days"). This means your segments can reflect genuine recent behaviour rather than all-time history, which matters when you're targeting a campaign at people who've been active this season.
The filtering options are more granular too. Tags can now be triggered by purchases linked to a specific organisation, a specific ticket type, or events carrying a specific event tag. Combined with existing rules based on number of events attended, tickets purchased, or total spend, this gives you a much more precise toolkit for building meaningful customer segments automatically.
One note worth flagging: if a tag was applied because a customer reached a rule threshold, and that order is later deleted, the tag isn't automatically removed. Manual review is needed in that case.
Basket rules that react in real time
This is where the tagging improvements connect directly to your sales flow. Two new actions are now available within basket rules, and both work while the customer is still actively shopping.
The first is interim customer tags. If a customer adds a membership to their basket, the system can apply a temporary tag to them immediately - before they've completed the purchase. Other basket rules can then recognise that tag and apply member-only discounts to the rest of their basket in the same session. If the customer abandons the basket without completing the purchase, the interim tag is removed automatically. The result is that membership benefits apply in real time during checkout rather than only kicking in after a completed purchase.
The second is automatic ticket type switching. If a customer meets certain criteria - entering a promo code, or reaching a specific number of tickets or unique events in their basket - the system can automatically switch their selected ticket type to a discounted or promotional one. This removes the need for customers to know which ticket type to select, and removes the need for your team to handle it manually.
Two new supporting settings sit alongside these: a toggle to create customer records earlier in the registration flow, and an option to prompt login before the basket stage for membership purchases, so the system knows who the customer is before the rules need to run.
Product dependencies
Some products should only be available once certain conditions are met. The product module now supports forced product dependencies - the ability to require that one product is in the basket before another can be added.
This is useful in a range of scenarios: a facility fee that must accompany a specific ticket type, a mandatory programme for certain events, or an add-on that only makes sense alongside a particular purchase. Customers are prompted to add the required product before the dependent one becomes available, and if they try to remove the required product, the dependent items are also removed.
A new column in the product module lets your team quickly see which products have dependencies attached, making it easier to manage and review these configurations as your product catalogue grows.
Mobile wallet ticket improvements
The final update in this batch is about what the ticket looks like at the end of the journey. Mobile wallet tickets now support more customisation options, giving venues greater control over how tickets appear in Apple Wallet and Google Pay.
You can now use an event group image on the wallet ticket rather than just the event date title - a more visual, branded presentation that better reflects the event itself. Barcode format is now flexible too: QR codes and Code 128 barcodes are both supported, depending on your scanning hardware. Layout options have been expanded for numbered and unnumbered events, so seat information (or the absence of it) displays cleanly across different event types.
For venues operating across multiple organisations, finance exports can now be filtered by seller organisation or owner organisation, which helps with tracking mobile sales in more complex setups.
