Release Notes: July 10

Loyalty

Self-Scheduled Dashboards

Users can now schedule any Analytics dashboard for automatic delivery — no admin required. Send the entire dashboard or a specific one, on a daily, weekly, monthly, or custom cadence, with control over delivery days, time, and time zone. Delivery is no longer limited to email — dashboards can also be routed to SFTP, a webhook, or an Amazon S3 bucket.

Messaging

Evo Messaging: Send Test

Users can now dispatch cross-channel test campaigns to dedicated lists of accounts, with resulting metrics automatically excluded from live reporting.

Evo Messaging: Split Testing

Users can now run up to 10 variants in a single campaign, featuring automatic winner selection and full pause/resume controls.

Loyalty

Updated Page Designs

Refreshed the look and feel of several key screens — Account Lookup, Campaign Message Templates, Coupon Manager, Email Builder Center, Report Center, and Social Login Configuration — for a more consistent, modern experience.

New Omni Analytics Link in Recent Pages

The recent pages analytics link now points to the new Omni URL instead of the legacy one. This update also cleans up duplicate old-URL entries, removes outdated "Omni" wording from titles and strings, and ensures the analytics page is properly tracked in a user's recent pages when selected.

Fixed Expired Password Links in Welcome Emails

New Evo users were sometimes receiving welcome emails with password-setup links that had already expired by the time they clicked them. The link is now generated only at the moment the user clicks it, so it will always be valid.

Batching for Large Campaign Account Updates

Campaign execution now updates account records in batches of up to 1,000 rows at a time. This improves reliability and performance for very large campaigns that previously risked timeouts during the account update step.

More Resilient Evo Webhook Delivery

Evo webhook delivery is now more resilient across server instances, with duplicate deliveries filtered out and cleaner handling of timeouts and claim releases. The wait timeout was also increased so webhooks are less likely to be dropped or processed twice.