1.304 Contextual personalization, bot detection for SMS click events, Safari push update & Mobile SDK

Expand AI-powered contextual personalization across all scenario channels. Remove legacy Safari 15 push support—Safari 16+ continues with Web Push API, and enhance iOS SDK stability for mobile apps.
Version released between 09.03. - 19.03.2026.

Contextual personalization improvements

Contextual personalization now works across all scenario channels and is easier to set up:

• All scenario channels supported: Use contextual personalization across email, mobile push, browser push, SMS, RCS, WhatsApp, App Inbox, and in-app personalization.
• Easier setup with Loomi AI defaults: The new Optimized by Loomi AI option automatically selects the most relevant contextual features for your project, replacing manual feature configuration.
• Optimize for any business goal: Define any tracked event as your optimization goal — such as purchase_item or subscription_complete — instead of relying on opens and clicks alone.

Deliver the right message to each customer by personalizing across your entire omnichannel strategy with AI-powered contextual intelligence.

Improved bot detection for SMS click events

We've added a new user agent to our bot detection list for SMS click events, based on our analysis of behavior patterns, IP addresses, and testing:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36

SMS click events from this user agent are now marked with bot = true.

This only applies to projects using Bloomreach's link shortener, as link tracking requires it.

Impact

For some projects, this user agent has accounted for over 90% of SMS click events, significantly inflating click metrics. Depending on your current setup:

• If you already filter out bot = true SMS clicks in your reporting, you may see a drop in reported click rates after this change.
• If you don't yet filter out bot = true clicks, we recommend doing so. Your historical SMS click data may include non-human activity.

Removal of legacy Safari push notifications (Safari 15 and earlier)

Bloomreach Engagement no longer supports push notifications for Safari versions 15 and earlier on macOS. These older Safari versions relied on Apple's proprietary push notification system (the "pushPackage" API), which Apple deprecated and removed starting with macOS Ventura and Safari 16 in 2022.

Who is affected?

Only website visitors using Safari 15 or earlier on macOS. Our data shows no successfully delivered Safari push notifications through this legacy system in recent months.

What isn't affected?

• Push notifications on Safari 16 and later (macOS Ventura and newer) — these use the industry-standard Web Push API and continue to work as expected
• Push notifications on Chrome, Firefox, Edge, and all other modern browsers
• Mobile push notifications (iOS, Android)

Do I need to do anything?

No action is required. If you previously configured legacy Safari push notifications using an Apple Developer certificate and Website Push ID, that configuration is no longer active. Safari users on macOS Ventura or later already receive push notifications through the standard Web Push API automatically.

Mobile SDK updates

iOS SDK

Enhanced stability and developer experience with our latest iOS SDK 3.10.0:

• Example app updates: Updates Example App's and their extensions bundle IDs.
• App Links support: Updates Example App to handle App Links with the new domain.
• Device ID management: Clears device ID when calling stopIntegration() or clearLocalCustomerData().
• Documentation improvements: Updates page titles with "iOS SDK" reference for improved searchability and navigation.
• Token tracking: Fixes tokenTrackFrequency method invocation.
• In-app message behavior: Fixes in-app message dismissal when user taps outside the dialog.