53 features and 54 dated states recorded · 11% of dates precise to the day · 1 monitored vendor source. Counts reflect how finely the vendor documents, not how much it ships. They include 16 features under review; the tiles and lifecycle summaries exclude them.
Current lifecycle records
The latest recorded state per feature, entries under review excluded. These are the records counted in the tiles above.
Will let marketers browse and insert Marketing Cloud Engagement images directly in Marketing Cloud Next Content Builder via DAM Connect, without manual downloads; planned for availability after December 18, 2026.
As Meta separates WhatsApp phone numbers from provider-specific templates and billing, Marketing Cloud Engagement lets a single WhatsApp number be used across Salesforce and another provider simultaneously without disrupting journeys, templates or API integrations.
Now GA (15 Oct 2026). Current summary: As Meta separates WhatsApp phone numbers from provider-specific templates and billing, Marketing Cloud Engagement lets a single WhatsApp number be used across Salesforce and another provider simultaneously without disrupting journeys, templates or API integrations.
Copies a data extension's columns, data types, primary keys and records from Marketing Cloud Engagement into a Marketing Object in one step, as a one-time copy with no ongoing sync.
A Security Dashboard gives admins one view of the account's security settings: an overall health score, factors by category, priority improvements and a PDF export. Not available on Hyperforce.
Salesforce announced that, in a future release, accounts using single sign-on will have to use MFA systems that send AMR and ACC claims; the requirement is not yet enforced.
Planned: WhatsApp Direct Send will let Engagement send utility messages without waiting for template pre-approval and catch template category mismatches before they trigger account restrictions; availability after November 2026.
The Installed Packages summary, which already listed client secret expiry dates, now also shows revocation and expiration status, client ID and days since the last authentication call.
Engagement can import contacts by WhatsApp Business-Scoped User ID, message users who hide their phone number behind a username, and track engagement across both identifiers.
Older TLS cipher suites are no longer supported for browser or API connections to Marketing Cloud Engagement as of the Summer '26 release; customers must use a modern TLS implementation such as TLS 1.3 with SHA-256/SHA-384 cipher suites.
The Summary widget shows why emails weren't sent, breaking out counts for duplicates, suppression list matches and missing addresses to help spot data issues.
Marketing Cloud Einstein features, including engagement scoring, were retired for customers in Australia, Japan and Canada Hyperforce regions; EU/US processing or Marketing Cloud Next can keep data in-region.
Admins can quickly create Marketing Cloud Next users by duplicating existing Engagement users, who are auto-assigned the permissions needed to start using Next.
Unified Messaging customers can enable Meta's MM Lite optimizations for outbound WhatsApp marketing template messages, improving delivery rates and ad-spend return.
Will let orgs with an older Engagement data model unify legacy data for compatibility with Marketing Cloud Next features like Marketing Performance reports.
Salesforce announced that from March 23, 2026 API client secrets expire 180 days after they are generated, and that secrets generated before that date expire on September 30, 2026.
Package Manager deployments now keep original external key values, including Journey Builder entry-source event keys, easing deployment of objects called by external APIs.
Dated changes (feature states) per primary capability area and month, minor updates and records under review included. They show what the vendor documented, which depends on how finely it writes release notes: not investment, and not how complete the platform is.
Links open this platform's whole-record timeline, including minor updates and all states. Capability timelines also include secondary classifications, so their totals can be higher than the primary-only counts above. Use All platforms in Timeline filters to explore the wider record.
week of 12 Oct 2026: Meta now charges per message for WhatsApp service and utility messages sent within the Customer Service Window (previously free); Salesforce updates its own pricing to reflect this, effective November 1, 2026, while Meta's charges take effect October 1, 2026. ↗Open signal →