# October 2026 Release Note

These are the Treasure AI features and improvements released in October, 2026.

## Engage Studio

### New Feature: Landing Pages

*Posted on: Oct 01, 2026*

- Engage Studio now supports Landing Pages, letting you publish completed static website packages from ZIP files to Active custom subdomains as branded public campaign destinations.
- Marketers prepare the page files outside Engage Studio, while web administrators configure and activate the custom subdomains.
- Landing Pages can also host a branded unsubscribe confirmation page on an Active custom subdomain, but the page does not process the unsubscribe request itself.
- Learn more by visiting the [Landing Pages](/products/marketing-cloud/engage-studio/landing-pages) page.


Engage Studio Landing Pages list showing a published Unsubscribe Page
### Enhancement to Mobile Push: Time-Sensitive Delivery

*Posted on: Oct 02, 2026*

- The **Time-sensitive delivery** switch lets you ask Firebase Cloud Messaging (FCM) to use high priority for Android notifications in one-off and always-on Mobile Push campaigns.
- Designed for time-sensitive alerts, the setting asks FCM to attempt delivery as soon as possible, including when an Android device is in Doze mode, but it does not guarantee immediate delivery because FCM, network, and device conditions can affect timing.
- The switch is off by default, is included in test sends, and leaves iOS delivery unchanged.
- Learn more by visiting the [Mobile Push Campaign](/products/marketing-cloud/engage-studio/channels/mobile-push) page.


Engage Studio's Mobile Push editor showing the Time-sensitive delivery switch turned off
## Integration Hub

### Enhancement to OneTrust Import Connector: V4 Collection Point Filtering and Rolling Incremental Loads

*Posted on: Oct 01, 2026*

- The OneTrust Import Connector's Data Subject Profile (API V4) data type now supports Collection Point filtering and rolling incremental loads, bringing V1-style per-Collection Point ingestion to V4.
- Set `collection_point_guid` to retrieve data for one Collection Point; if you omit it, the connector keeps the existing behavior of retrieving data across all Collection Points.
- With `incremental: true`, `end_time` is optional. The connector fixes an upper bound for each run and advances the next run's start time to that bound only after all pages are retrieved and written successfully, even when the run returns no records.
- This enhancement is designed for data engineers moving OneTrust Data Subject Profile jobs from API V1 to API V4 who need to keep website consent data separate and avoid repeatedly requesting the same empty time range.
- Learn more by visiting the [OneTrust Import Integration](/int/onetrust-import-integration) page.