Beta
Platforms ▾
Engagement platformsCEP
CEPs in the Release Matrix →
Data platformsCDP
CDPs in the Release Matrix →
B2B marketing automationMAP B2B
MAP B2Bs in the Release Matrix →
All platforms15 tracked · 8 CEP · 4 CDP · 3 MAP B2B
Compiled 11 Nov

Type at least 2 characters.

Corrections

Changes made to published records after review: dates, states, promises, classifications, scope and merges. Each entry shows the value before and after, the reason and the evidence. 431 corrections.

What counts as a correction

A correction changes a fact the record had already published, or adds a state that was missed and added after review (for example, a GA documented by the vendor that had not reached the record). New lifecycle states the pipeline reads in vendor sources on its own are not corrections: they appear in the timeline.

Not listed here: technical rebuilds (a platform re-read from scratch, or a product split into two, 143 record addresses moved when Salesforce Marketing Cloud became Engagement and Next), new fields added to the data model, and changes to the under-review flag. Old addresses of merged, moved or removed records still open and point to the current record.

64 entries made before the register existed (8 October 2026) were reconstructed from the record's revision history, back to the first public dataset (29 September 2026). Reports from readers and vendors are checked against public sources; the report text and the reporter's identity are never published.

431 corrections
  1. Lifecycle state HubSpot · Agent Builder for Starter

    Lifecycle state: GA · 29 Sep 2026 → Beta · 29 Sep 2026

    Agent Builder is in public beta ("Introducing Agent Hub and Agent Builder (public beta)", 23 July 2026) and no source states its GA; the September roundup says it "now reaches Starter". Evidence: community.hubspot.com ↗

  2. Lifecycle state Marketo · Merge Leads API ID limit

    Retired state: not recorded → Retired · 31 Jul 2026

    The August 2026 notes confirm the limit is in effect: "As of July 31, 2026, calls that include more than 25 IDs ... result in a 1080 error code" (same treatment as the static list size limit). Evidence: experienceleague.adobe.com ↗

  3. Promised date Marketo · Marketo Engage New UI

    Announced promised date: Sep 2026 → Oct 2026

    The August "Phased rollout throughout August and September" was not yet GA: the later status column promised "General Availability by mid-October" (owner decision). Evidence: experienceleague.adobe.com ↗

  4. Removed HubSpot · Data warehouse sync credit changes

    Record removed: Data warehouse sync credit changes.

    Out of the HubSpot Marketing Hub scope: a change in Data Studio credit consumption (direct data warehouse syncs "no longer consume data studio credits") belongs to Data Hub and is a pricing change, not a Marketing Hub capability. Evidence: community.hubspot.com ↗

  5. Classification Adobe AJO · Dataset TTL guardrail enforcement on existing sandboxes

    Significance: major → minor

    A retention limit extended to existing sandboxes, not a new capability or a removal. Evidence: experienceleague.adobe.com ↗

  6. Text Adobe AJO · Dataset TTL guardrail enforcement on existing sandboxes
    Summary rewritten

    Before: Existing sandboxes/orgs will start enforcing the dataset TTL guardrail (90 days profile store, 13 months data lake) from October 1, 2026.

    After: Journey Optimizer enforces the dataset TTL guardrail (90 days in the profile store, 13 months in the data lake) on existing sandboxes and organizations from October 1, 2026.

    Summary in the present tense for a change in effect since October 1, 2026. Evidence: experienceleague.adobe.com ↗

  7. Lifecycle state Adobe AJO · Dataset TTL guardrail enforcement on existing sandboxes

    Lifecycle state: Deprecation announced · Jul 2026 → GA · 1 Oct 2026

    Not the removal of a feature: the TTL guardrail "will be enforced on existing customer sandboxes and organizations starting October 1, 2026". Recorded as a change in effect from that date (owner decision). Evidence: experienceleague.adobe.com ↗

  8. Classification Iterable · WhatsApp portfolio-wide messaging limits

    Significance: notable → minor

    A third-party policy change reported by Iterable, not a capability released by Iterable. Evidence: support.iterable.com ↗

  9. Classification Iterable · WhatsApp portfolio-wide messaging limits

    Classification: Arbitration, frequency & send-time rules (also Messaging apps) → Messaging apps

    A channel rule set by Meta ("Meta has changed how messaging limits work for WhatsApp"), not a marketer's frequency rule: classified under messaging apps. Evidence: support.iterable.com ↗

  10. Lifecycle state HubSpot · Marketing email creation and review via the ChatGPT connector

    Announced state: not recorded → Announced · 16 Sep 2026

    Announced on 16 September 2026: the "Updated ChatGPT connector runs email campaigns" from inside ChatGPT (HubSpot and OpenAI partnership news). Evidence: hubspot.com ↗

  11. Text HubSpot · ChatGPT connector landing page creation and deal analysis
    Summary rewritten

    Before: The HubSpot connector for ChatGPT is being expanded to run email campaigns, create landing pages and analyze closed-won deals from inside ChatGPT.

    After: The HubSpot connector for ChatGPT is being expanded to create landing pages and analyze closed-won deals from inside ChatGPT.

    The Watch row says the connector "runs email campaigns, creates landing pages and analyses closed-won deals"; email creation is recorded on its own record (GA October 2026), so this one covers landing pages and deal analysis. Evidence: hubspot.com ↗

  12. Text HubSpot · ChatGPT connector landing page creation and deal analysis
    Name rewritten

    Before: ChatGPT connector campaign, landing page and deal analysis

    After: ChatGPT connector landing page creation and deal analysis

    The Watch row says the connector "runs email campaigns, creates landing pages and analyses closed-won deals"; email creation is recorded on its own record (GA October 2026), so this one covers landing pages and deal analysis. Evidence: hubspot.com ↗

  13. Text HubSpot · Redesigned Breeze Assistant prompt experience
    Summary rewritten

    Before: Breeze Assistant prompts support @Mentions of CRM records, saved reusable prompts with placeholders, and categorized prompt suggestions.

    After: Breeze Assistant prompts support @Mentions of CRM records, saved reusable prompts with placeholders, categorized suggestions, and a prompt library of HubSpot-created prompts and prompts shared across the team.

    Merged with the 10 March post on the prompt library: "You can now discover HubSpot-created prompts, create your own, and share them across your team." Evidence: community.hubspot.com ↗

  14. Merged HubSpot · hubspot-marketing-hub.breeze-assistant-custom-prompts

    Record hubspot-marketing-hub.breeze-assistant-custom-prompts merged into Redesigned Breeze Assistant prompt experience.

    Same capability recorded twice: the February 2026 roundup's saved, reusable prompts organized by team are the prompt library of the 10 March post ("discover HubSpot-created prompts, create your own, and share them"); both sources are cited on the kept record. Evidence: community.hubspot.com ↗

  15. Promised date HubSpot · Admin-configured validation enforcement on CRM API writes

    Announced promised state: GA → none

    The changelog says "the /2026-09/ API version shipping on September 8, 2026" and that HubSpot "will enforce" the rules; it does not name a release state. Evidence: developers.hubspot.com ↗

  16. Date Marketo · Generate Content in Email Designer contextual menu

    Announced date: Announced · 14 Aug 2026 → Announced · Aug 2026

    The row is marked "Coming soon": August 14 is when available features "start to be released"; an announcement takes the page month, as the September and October rows do. Evidence: experienceleague.adobe.com ↗

  17. Source SF Account Engagement · Per-business-unit email open and click tracking controls

    GA cite url: https://help.salesforce.com/s/articleView?id=release-notes.rn_mcae_tracking.htm&release=262&type=5&language=en_US → https://help.salesforce.com/s/articleView?id=release-notes.rn_mcae_email_tracking.htm&release=264&type=5&language=en_US

    The state is now dated by the Winter '27 release note "Disable Email Open and Click Tracking", which carries the When line. Evidence: help.salesforce.com ↗

  18. Date SF Account Engagement · Per-business-unit email open and click tracking controls

    GA date: GA · May 2026 → GA · Jul 2026

    The Winter '27 note's When line says "Tracking settings for opens, links, and advanced metrics are available starting in July 2026"; a When note wins over the release date. Evidence: help.salesforce.com ↗

  19. Date Marketo · Survey Pod for Interactive Webinars

    GA date: GA · 30 Jan 2026 → GA · Jan 2026

    Listed under "Non-Standard Release Cycle Features" ("released outside of the standard Marketo Engage release cycle"), with no date; January 30 applies to the standard cycle only. Evidence: experienceleague.adobe.com ↗

  20. Date Marketo · Resources Pod for Interactive Webinars

    GA date: GA · 30 Jan 2026 → GA · Jan 2026

    Listed under "Non-Standard Release Cycle Features" ("released outside of the standard Marketo Engage release cycle"), with no date; January 30 applies to the standard cycle only. Evidence: experienceleague.adobe.com ↗

  21. Date Marketo · Interactive Webinars room interface refresh

    GA date: GA · 30 Jan 2026 → GA · Jan 2026

    Listed under "Non-Standard Release Cycle Features" ("released outside of the standard Marketo Engage release cycle"), with no date; January 30 applies to the standard cycle only. Evidence: experienceleague.adobe.com ↗

  22. Text HubSpot · Planned prioritized daily homepage
    Summary rewritten

    Before: The homepage now surfaces the work needing attention — follow-ups, meetings, tasks and recent activity — rather than a static landing view.

    After: HubSpot will surface a prioritized view of the day at login (overdue follow-ups, deals gone quiet, suggested next actions), as part of a redesign rolling out in stages.

    Summary returned to the announcement: "HubSpot will surface a prioritized view of your day and guide you toward the actions that matter most." Evidence: community.hubspot.com ↗

  23. Lifecycle state HubSpot · Planned prioritized daily homepage

    GA state: GA · 29 Sep 2026 → not recorded

    The 29 September post confirms the new home page only "For those of you who have been using Starter": a tier extension, recorded on its own, not the GA of the homepage announced for all. Evidence: community.hubspot.com ↗

  24. Classification HubSpot · Block IP address in Live Chat

    Classification: Security & certifications (also Conversational & voice) → Conversational & voice

    Classified by what it acts on: "Block an IP from a live chat thread for 14 days and move its existing threads to spam" is a live chat control, not a security certification. Evidence: community.hubspot.com ↗

  25. Removed HubSpot · Conversational context analysis limits add-on

    Record removed: Conversational context analysis limits add-on.

    A packaging change, not a capability: HubSpot "is now metering" conversational records analyzed for AI and high-volume accounts "can purchase an add-on". Recorded as signal hubspot-marketing-hub.signal.conversational-context-limits-addon. Evidence: community.hubspot.com ↗

  26. Removed HubSpot · App object support in association workflow actions

    Record removed: App object support in association workflow actions.

    Out of the HubSpot Marketing Hub scope: the August 2026 roundup gives "Availability: ... Workflow actions for Operations Hub Pro+" for app object association actions. Evidence: community.hubspot.com ↗

  27. Removed HubSpot · AI-generated buyer personas in Make My Persona

    Record removed: AI-generated buyer personas in Make My Persona.

    Out of scope: Make My Persona is "HubSpot's free buyer persona generator", a standalone website tool not included in Marketing Hub. Evidence: community.hubspot.com ↗

  28. Removed HubSpot · Embeddable AI Search Sensor widget for partners

    Record removed: Embeddable AI Search Sensor widget for partners.

    Out of scope: a widget for HubSpot partners ("now available for HubSpot partners") embedding public charts of the free AI Search Sensor benchmark tool, not a Marketing Hub capability. Evidence: community.hubspot.com ↗

  29. Removed Marketo · OpenAI Codex configuration for MCP Server

    Record removed: OpenAI Codex configuration for MCP Server.

    Documentation-only change: the Watch row reports an "OpenAI Codex configuration tab" added to the MCP Server documentation page; no new capability. Evidence: experienceleague.adobe.com ↗

  30. Text Hightouch offered Publicis $800M–$1.2B for LiveRamp's identity assets, RampID and LiveRamp Connect.
    Summary rewritten

    Before: Hightouch offered Publicis $800M–$1.2B in cash and stock for LiveRamp's identity and data onboarding businesses (RampID, LiveRamp Connect) before Publicis' LiveRamp deal closed; its co-CEO confirmed the offer.

    After: Hightouch offered Publicis $800M–$1.2B for LiveRamp's identity assets, RampID and LiveRamp Connect.

    Only what the archived Watch row supports is kept: the deal-closing context, the payment form and the co-CEO confirmation have no archived text. Evidence: businesswire.com ↗

  31. Source Hightouch offered Publicis $800M–$1.2B for LiveRamp's identity assets, RampID and LiveRamp Connect.

    Sources: 2 sources → 3 sources

    The Watch row ("offered Publicis $800M–$1.2B for LiveRamp identity assets (RampID, LiveRamp Connect) — catch-up, announced 16 June") is archived and cited. Evidence: businesswire.com ↗

  32. Source Tealium · Google DV360 Customer Match Data Manager API actions

    GA sources: 1 source → 2 sources

    Cites the later entry merged into this record (tealium.google-dv360-customer-match-add-remove-users-data-manager-api); the earliest state is kept. Evidence: docs.tealium.com ↗

  33. Merged Tealium · tealium.google-dv360-customer-match-add-remove-users-data-manager-api

    Record tealium.google-dv360-customer-match-add-remove-users-data-manager-api merged into Google DV360 Customer Match Data Manager API actions.

    Same capability: the note of 9 September 2026 (Data Manager API actions for adding and removing users, "deprecated the legacy actions") repeats the note of 22 April 2026. Evidence: docs.tealium.com ↗

  34. Text Adobe AEP · Batch profile ingestion job status monitoring
    Summary rewritten

    Before: Users can now track job-level progress percentage and checkpoints for batch Profile ingestion dataflow runs.

    After: Users can track job-level progress percentage and checkpoints for batch Profile ingestion dataflow runs; from May 2026 the monitoring dashboard also shows job initiation and queued time.

    Summary covers the details added by the merged later entry. Evidence: experienceleague.adobe.com ↗

  35. Source Adobe AEP · Batch profile ingestion job status monitoring

    GA sources: 1 source → 2 sources

    Cites the later entry merged into this record (adobe-experience-platform.batch-profile-ingestion-progress-tracking); the earliest state is kept. Evidence: experienceleague.adobe.com ↗

  36. Merged Adobe AEP · adobe-experience-platform.batch-profile-ingestion-progress-tracking

    Record adobe-experience-platform.batch-profile-ingestion-progress-tracking merged into Batch profile ingestion job status monitoring.

    Same capability: the May 2026 "Batch profile ingestion progress" entry tracks batch profile ingestion jobs from the monitoring dashboard, as the January 2026 entry; May adds job initiation and queued time. Evidence: experienceleague.adobe.com ↗

  37. Source Adobe AEP · Attribute summary data in Segment Builder and Audience Builder

    GA sources: 1 source → 2 sources

    Cites the later entry merged into this record (adobe-experience-platform.audience-data-insights-summary); the earliest state is kept. Evidence: experienceleague.adobe.com ↗

  38. Merged Adobe AEP · adobe-experience-platform.audience-data-insights-summary

    Record adobe-experience-platform.audience-data-insights-summary merged into Attribute summary data in Segment Builder and Audience Builder.

    Same capability: the May 2026 entry "You can now view summary data for your people-based and account-based audiences" repeats the March 2026 "Summary data" entry. Evidence: experienceleague.adobe.com ↗

  39. Source Tealium · Connector log streaming

    GA sources: 1 source → 2 sources

    The note of 18 March 2026 dates the capability; the recap of 31 August 2026 stays as the second source. Evidence: docs.tealium.com ↗

  40. Date Tealium · Connector log streaming

    GA date: GA · 31 Aug 2026 → GA · Confirmed by 18 Mar 2026

    The dated note of 18 March 2026 updates "the Google BigQuery connector to add support for sending connector log streaming events"; the recap of 31 August 2026 gives no date. Evidence: docs.tealium.com ↗

  41. Text Treasure AI · Per-user access control for AI Studio
    Summary rewritten

    Before: Account admins can restrict AI Studio access to an approved set of users via the Treasure AI REST API, opt-in per account.

    After: Account admins can restrict AI Studio to an approved set of users through the Treasure AI REST API; the restricted mode is enabled on request by the Customer Success Manager.

    Summary rewritten for the preview state: the mode is enabled on request. Evidence: docs.treasure.ai ↗

  42. Lifecycle state Treasure AI · Per-user access control for AI Studio

    Lifecycle state: GA · 28 Jun 2026 → Preview · 28 Jun 2026

    The entry of 28 June 2026 says "contact your Customer Success Manager to enable restricted (opt-in) mode for your account": access on request. Evidence: docs.treasure.ai ↗

  43. Text Tealium · OpenAI Events connector
    Summary rewritten

    Before: Upcoming connector for server-side delivery of marketing and conversion events to the OpenAI Events API for attribution and optimization.

    After: Server-side connector for events and audiences that delivers marketing and conversion events to the OpenAI Events API for attribution and optimization.

    Summary rewritten for the available connector: no longer upcoming. Evidence: docs.tealium.com ↗

  44. Lifecycle state Tealium · OpenAI Events connector

    GA state: not recorded → GA · Confirmed by 29 Jul 2026

    The dated note of 29 July 2026 "Updated the OpenAI Events connector to improve help text": the connector announced on 28 May was in use by then. Evidence: docs.tealium.com ↗

  45. Source Tealium · New sign-in and profile selector experience

    GA sources: 1 source → 2 sources

    The recap of 30 June 2026 ("A new login experience makes it faster and simpler") is cited on the GA as the same capability. Evidence: docs.tealium.com ↗

  46. Lifecycle state Tealium · New sign-in and profile selector experience

    Announced state: Announced · 30 Jun 2026 → not recorded

    Tealium's recap of 30 June 2026 lists "New Login" without a date of its own; the dated note of 8 July 2026 says "A new sign-in experience is now available". Evidence: docs.tealium.com ↗

  47. Lifecycle state Adobe AEP · Snowflake Batch destination

    GA (regional) state: GA (regional) · 27 Jan 2026 · US → not recorded

    The January 2026 notes update a destination already in limited release, "currently only available to Real-Time CDP customers provisioned in the Experience Platform VA7 region"; February 2026 states GA. Evidence: experienceleague.adobe.com ↗

  48. Text Adobe AEP · V2 table structure for Snowflake Batch destination
    Summary rewritten

    Before: New V2 table structure for Snowflake Batch adds separate audience name and origin columns for new connections; the old structure stays available until it is deprecated at the end of June 2026.

    After: New V2 table structure for Snowflake Batch adds separate audience name and audience origin columns; new destination connections get both the V2 and the original table structures.

    The deprecation of the old structure ("kept until the end of June 2026, after which it will be deprecated") is recorded on its own, as adobe-experience-platform.snowflake-batch-v1-table-structure. Evidence: experienceleague.adobe.com ↗

  49. Removed Tealium · Microsoft Advertising UET tag enhanced conversion em/ph mapping

    Record removed: Microsoft Advertising UET tag enhanced conversion em/ph mapping.

    Out of scope: a bug fix; the note of 30 September 2026 says existing profiles "must update and republish the tag template to receive this fix". Evidence: docs.tealium.com ↗

  50. Removed Tealium · Connector Insights for Google DV360 Customer Match Data Manager API actions

    Record removed: Connector Insights for Google DV360 Customer Match Data Manager API actions.

    Out of scope: a back-end API migration with no new capability; the note of 28 October 2026 updates the connector's "Data Manager API actions to use the Data Manager API for Insights". Evidence: docs.tealium.com ↗

  51. Removed Tealium · Connector Insights for Google Ads Customer Match Data Manager actions

    Record removed: Connector Insights for Google Ads Customer Match Data Manager actions.

    Out of scope: a back-end API migration with no new capability; the note of 28 October 2026 updates the connector's "Insights for Data Manager actions to use the Data Manager API". Evidence: docs.tealium.com ↗

  52. Removed Adobe AEP · NLD2 region IP allowlist update for batch sources

    Record removed: NLD2 region IP allowlist update for batch sources.

    Out of scope: a network allowlist notice, not a capability; the May 2026 notes ask customers to "Update your network allowlist" for batch sources in the NLD2 region. Evidence: experienceleague.adobe.com ↗

  53. Removed Adobe AEP · Write-time profile attribute consolidation for faster exports

    Record removed: Write-time profile attribute consolidation for faster exports.

    Out of scope: a back-end performance change; the July 2026 notes say there is no "change to functionality or merge behavior". Evidence: experienceleague.adobe.com ↗

  54. Removed Adobe AEP · mTLS certificate hierarchy migration

    Record removed: mTLS certificate hierarchy migration.

    Out of scope: an operational certificate advisory, not a capability; the August 2026 notes ask customers to "add the new root and intermediate CA certificates" to their trust store. Evidence: experienceleague.adobe.com ↗

  55. Text SFMC Next · Marketing Cloud Next setup via Salesforce Go
    Summary rewritten

    Before: Salesforce Go provides a single place to enable and configure Marketing Cloud Next features.

    After: Extends Salesforce Go setup: the whole Marketing Cloud configuration, including app install, data streams, prerequisites and Identity Resolution, runs from the Initial Setup page, with filters by channel, Einstein, optimization or analytics.

    Salesforce Go setup already existed in Summer '26 ("Simplify Next-Gen Feature Discovery and Setup"); the Winter '27 note extends it. Evidence: help.salesforce.com ↗

  56. Text SFMC Next · Mobile app metrics dashboards
    Summary rewritten

    Before: Improves dashboards covering mobile app performance and message deliverability.

    After: Unified dashboards for in-app messages and push notifications track mobile app campaign delivery rates, dismissals and CTA clicks, with a filter for iOS or Android.

    Summary limited to the entry "Gain Deeper Insights into Mobile App Metrics"; deliverability is recorded on its own. Evidence: help.salesforce.com ↗

  57. Classification SFMC Next · Mobile app metrics dashboards

    Classification: Reporting & dashboards (also Deliverability & sender infrastructure) → Reporting & dashboards

    Deliverability is the separate entry "Track Deliverability Metrics for SMS, WhatsApp, and Mobile Push", recorded as the Low-Performing Campaign view. Evidence: help.salesforce.com ↗

  58. Text SFMC Next · Preference page design and subscription control
    Summary rewritten

    Before: Adds more design and content control over the customer-facing preference page and its subscriptions.

    After: Preference pages per channel can be linked to specific messages, show a chosen set of subscriptions and use custom button text and styles.

    The note says marketers can "link the right page to the right message, control which subscriptions to show, and update button text and styles". Evidence: help.salesforce.com ↗

  59. Text SFMC Next · Marketing Objects for high-throughput data storage
    Summary rewritten

    Before: Marketing Objects provide high-throughput storage for marketing data used across personalization and campaigns.

    After: Marketing Objects are a high-throughput, low-latency store for marketing data, loaded from external systems by CSV import and readable in emails with Handlebars or AMPscript.

    Summary now includes the CSV import and message use described in the same entry. Evidence: help.salesforce.com ↗

  60. Merged SFMC Next · salesforce-marketing-cloud-next.marketing-objects-csv-import

    Record salesforce-marketing-cloud-next.marketing-objects-csv-import merged into Marketing Objects for high-throughput data storage.

    Part of the same entry, "Store Marketing Data in High-Performance Marketing Objects": "Bring data from external systems into your Marketing Objects by importing CSV files." Evidence: help.salesforce.com ↗

  61. Text SFMC Next · Salesforce Objects and content variables as email data sources
    Summary rewritten

    Before: Marketers can define custom content variables as placeholders in emails and map them to any Salesforce Flow data source, including MuleSoft and HTTP connectors.

    After: Emails can be personalized from two new data sources: live Salesforce Objects such as Cases or Leads, and custom content variables mapped to any Salesforce Flow data source, including MuleSoft and HTTP connectors.

    The entry adds "two new data sources: Salesforce Objects and content variables"; both are now named. Evidence: help.salesforce.com ↗

  62. Merged SFMC Next · salesforce-marketing-cloud-next.live-salesforce-data-personalization-mc-next

    Record salesforce-marketing-cloud-next.live-salesforce-data-personalization-mc-next merged into Salesforce Objects and content variables as email data sources.

    Same Summer '26 entry "Personalize Emails with New Data Sources": "two new data sources: Salesforce Objects and content variables". Evidence: help.salesforce.com ↗

  63. Text SFMC Next · Custom-attribute audience targeting for flash messages
    Summary rewritten

    Before: New flash message type sends high-throughput mobile messages to targeted audiences.

    After: Mobile app users can be subscribed to custom-attribute audiences, such as interest in sports, at device registration, and each flash message can target a chosen audience.

    The new part of the Winter '27 note is audience targeting by custom attributes; flash sending itself is the Spring '26 pilot, now generally available. Evidence: help.salesforce.com ↗

  64. Classification SFMC Next · Custom-attribute audience targeting for flash messages

    Classification: SMS, MMS & RCS → In-app messages

    Flash messages go to mobile app users, not SMS; classified like the flash notifications record. Evidence: help.salesforce.com ↗

  65. Text SFMC Next · Mobile app flash notifications
    Summary rewritten

    Before: In a pilot, marketers can send near real-time flash notifications to mobile app users for time-sensitive messaging via a new flow element.

    After: Marketers can send time-sensitive flash notifications to mobile app users in near real time from a flow element, at up to 5 million messages in 90 seconds.

    Summary rewritten for general availability: the Winter '27 note no longer calls flash sending a pilot. Evidence: help.salesforce.com ↗

  66. Lifecycle state SFMC Next · Mobile app flash notifications

    GA state: not recorded → Sep 2026

    The Winter '27 note describes flash sending to mobile app users ("up to 5 million messages in 90 seconds") with no Pilot marker. Evidence: help.salesforce.com ↗

  67. Merged SFMC Next · salesforce-marketing-cloud-next.email-language-variants

    Record salesforce-marketing-cloud-next.email-language-variants merged into AI-assisted translation for email language variants.

    Same Winter '27 note "Localize Emails Faster with Built-In Language Variants"; Summer '26 only says "go multilingual with content variants", so no May 2026 GA. Evidence: help.salesforce.com ↗

  68. Merged SFMC Next · salesforce-marketing-cloud-next.agentforce-account-nurturing-agent

    Record salesforce-marketing-cloud-next.agentforce-account-nurturing-agent merged into Account Discovery Agent.

    Same agent: the Summer '26 overview's "new Agentforce Account Nurturing Agent" to "identify buying groups" is detailed as "Identify Buying Groups with the Account Discovery Agent". Evidence: help.salesforce.com ↗

  69. Date SFMC Next · Launch Distributed Marketing and Alerts from custom Lightning web components

    Date: GA · week of 28 Sep 2026 · Global → GA · May 2026 · Global

    The Summer '26 notes already say "An admin can now build a custom Lightning Web Component" for it; the Winter '27 entry of September 28 is a republished note. Evidence: help.salesforce.com ↗

  70. Text SFMC Next · Marketing Object sandbox testing
    Summary rewritten

    Before: Test Marketing Object changes in a sandbox and sync the result with Data 360.

    After: Marketing Object schema changes can be tested in a sandbox and deployed to production with change sets; schemas replicate from production when a sandbox is refreshed.

    The Data 360 sync described in the same note is recorded on its own (announced, mid-November 2026); this record covers sandbox testing only. Evidence: help.salesforce.com ↗

  71. Text SFMC Next · Buyer Engagement Agent
    Summary rewritten

    Before: New Agentforce agent nurtures high-volume marketing leads into qualified sales pipeline.

    After: An Agentforce agent runs inbound lead generation and high-volume lead nurturing across marketing channels; its setup builds a Buyer Engagement data graph, deploys the conversation data kit and turns on transcripts.

    Summary now names the setup steps added in October 2026 (data graph, conversation data kit, transcripts), formerly recorded as separate features. Evidence: help.salesforce.com ↗

  72. Date SFMC Next · Buyer Engagement Agent

    Date: GA · week of 30 Aug 2026 · Global → GA · Aug 2026 · Global

    The note's When line says "This feature is available starting August 2026."; the week of August 30 is when the note was added. Evidence: help.salesforce.com ↗

  73. Merged SFMC Next · salesforce-marketing-cloud-next.buyer-engagement-agent-data-graph

    Record salesforce-marketing-cloud-next.buyer-engagement-agent-data-graph merged into Buyer Engagement Agent.

    A setup step, not a capability: the update says "Agent setup now includes steps to create a Buyer Engagement data graph". Evidence: help.salesforce.com ↗

  74. Merged SFMC Next · salesforce-marketing-cloud-next.buyer-engagement-agent-conversation-context

    Record salesforce-marketing-cloud-next.buyer-engagement-agent-conversation-context merged into Buyer Engagement Agent.

    A setup step, not a capability: the update says "Agent setup now includes steps to deploy the conversation data kit and turn on conversation transcripts". Evidence: help.salesforce.com ↗

  75. Source SFMC Next · Automatic archiving of sent emails to the EmailMessage object

    Sources: help.salesforce.com/s/articleView → help.salesforce.com/s/articleView

    "Store Email Copies with Email Archiving" is in the Summer '26 Other Changes section page, not in the snapshot first cited, which carries no section pages. Evidence: help.salesforce.com ↗

  76. Source SFMC Next · Dynamic From and Reply-To addresses

    Sources: help.salesforce.com/s/articleView → help.salesforce.com/s/articleView

    "Personalize Email Headers with Dynamic Addresses" is in the Summer '26 Other Changes section page, not in the snapshot first cited, which carries no section pages. Evidence: help.salesforce.com ↗

  77. Merged SFMC Next · salesforce-marketing-cloud-next.import-data-extension-to-marketing-object

    Record salesforce-marketing-cloud-next.import-data-extension-to-marketing-object merged into Data Extension import into a Marketing Object.

    Same release note: "Import a Data Extension into a Marketing Object" is listed under Marketing Cloud Engagement+ and in the Engagement notes, where it is recorded. Evidence: help.salesforce.com ↗

  78. Text SFMC Engagement · Account security posture dashboard
    Summary rewritten

    Before: A consolidated security dashboard lets admins monitor account health scores and overall security posture.

    After: 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.

    The note says it applies to "editions in Salesforce-hosted environments. This feature isn't available on Hyperforce." Evidence: help.salesforce.com ↗

  79. Date SFMC Engagement · WhatsApp account model update

    Date: Announced · week of 11 Oct 2026 · Global → Announced · week of 12 Oct 2026 · Global

    Salesforce's change log now reads "Prepare for the WhatsApp Account Model Update (Added the week of October 12, 2026)", as on the Marketing Cloud Next record. Evidence: help.salesforce.com ↗

  80. Text SFMC Engagement · Client secret status summary on Installed Packages page
    Summary rewritten

    Before: A summary dashboard on the Installed Packages page now shows the status of each package's API client secrets.

    After: 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.

    Spring '26 already said "see the summary table on the Installed Packages page"; Winter '27 adds revocation status, client ID and days since the last authentication call. Evidence: help.salesforce.com ↗

  81. Text MoEngage · Merlin AI custom agents
    Summary rewritten

    Before: MoEngage announced custom workflow agents with marketer-defined guardrails and full step visibility.

    After: Marketers can build custom Merlin AI agents with their own guardrails and full visibility of each step; Custom Agents are live on all MoEngage data centres.

    Summary rewritten for the general availability stated in the August 2026 release notes. Evidence: moengage.com ↗

  82. Lifecycle state MoEngage · Merlin AI custom agents

    GA state: not recorded → Confirmed by Aug 2026

    The August 2026 release notes say "Custom Agents are live on DC-01 to DC-04 and DC-101": live on all data centres is global GA. Evidence: moengage.com ↗

  83. Text Klaviyo · Klaviyo MCP server: 260+ new tools
    Summary rewritten

    Before: An MCP server exposes 260+ tools so AI agents and developers can read data, build segments, run campaigns and manage catalogs programmatically.

    After: Adds 260+ tools to the existing Klaviyo MCP server, so AI agents and developers can read data, build segments, run campaigns, author flows and manage catalogs from Claude, OpenAI or custom agents.

    The entry, retitled "New Tools for Klaviyo MCP Server", adds "260+ new MCP tools" to a server already in use (MCP template tools on 2026-05-29, Claude connector on 2026-01-22). Evidence: klaviyo.com ↗

  84. Text Klaviyo · Custom Skills for Composer
    Summary rewritten

    Before: Composer supports custom, user-defined Skills that extend its agentic capabilities.

    After: Users can save their own skills in Composer and pull one into a chat by typing @, to reuse workflows that worked.

    Summary rewritten for the availability shown by the vendor's @mention skills entry. Evidence: klaviyo.com ↗

  85. Lifecycle state Klaviyo · Custom Skills for Composer

    Lifecycle state: Announced · 9 Sep 2026 · Global → GA · Confirmed by 2 Sep 2026 · Global

    What's New lists "@mention skills in Composer" (2026-09-02, generalAvailability): "Type @ in the Composer chat to pull in one of your skills." Custom skills were available then. Evidence: klaviyo.com ↗

  86. Removed Klaviyo · Billing in Canadian dollars

    Record removed: Billing in Canadian dollars.

    A billing-currency option, not a capability: "Choose CAD as a new Canadian customer to see pricing, sign contracts, pay, and get invoices". Recorded as signal klaviyo.signal.pay-in-cad. Evidence: klaviyo.com ↗

  87. Removed Klaviyo · Reduced WhatsApp messaging charges

    Record removed: Reduced WhatsApp messaging charges.

    A pricing change, not a capability: "Avoid charges for failed messages, utility templates during open service windows" and Click to WhatsApp Ads messages. Recorded as signal klaviyo.signal.whatsapp-billing-improvements. Evidence: klaviyo.com ↗

  88. Removed Klaviyo · Logging of unsupported MCP server tasks

    Record removed: Logging of unsupported MCP server tasks.

    Not customer-facing: Klaviyo logs tasks its MCP server "can't complete" in Chronosphere "to prioritize tooling improvements"; the entry left What's New after 9 October 2026. Evidence: klaviyo.com ↗

  89. Removed Klaviyo · AI assistant in developer documentation

    Record removed: AI assistant in developer documentation.

    Documentation-only change, out of scope: the entry adds "the new kapa.ai widget on developers.klaviyo.com" for implementation guidance and API help. Evidence: klaviyo.com ↗

  90. Source Adobe AJO · Loyalty for Healthcare Shield and Privacy and Security Shield customers

    GA sources: experienceleague.adobe.com/en/docs/journey-optimizer/using/whats-new/release-not → experienceleague.adobe.com/en/docs/journey-optimizer/using/whats-new/release-not

    The entry "Loyalty available for Healthcare Shield and Privacy and Security Shield customers" is already in the 27 Sep 2026 snapshot. Evidence: experienceleague.adobe.com ↗

  91. Removed Signal

    Record removed: AJO Loyalty is now included for customers on the Healthcare Shield and Privacy and Security Shield packages..

    Covered by the feature Loyalty for Shield customers; the source says Loyalty "is now available to" Shield customers, not "included" in the packages. Evidence: experienceleague.adobe.com ↗

  92. Removed Signal

    Record removed: Adobe Journey Optimizer's AI image generation added a partner model option powered by Google's Gemini 2.5 Flash, alongside Adobe Firefly and custom models..

    Not a partnership: the source lists a "Partner model (powered by Gemini 2.5 Flash)" as a model option inside image generation; no partnership is announced. Evidence: experienceleague.adobe.com ↗

  93. Text Iterable · Salesforce data out (consent sync)
    Name rewritten

    Before: Salesforce activity sync (data out)

    After: Salesforce data out (consent sync)

    The October 20 release of "Salesforce data out" syncs "email opt-in and opt-out updates" to Contact and Lead records. Evidence: support.iterable.com ↗

  94. Text Braze · eCommerce recommended events
    Summary rewritten

    Before: Adds a 'Places Order' conversion event to eCommerce recommended events, mirroring the existing 'Makes Purchase' event.

    After: eCommerce recommended events cover six purchase steps (product_viewed, cart_updated, checkout_started, order_placed, order_cancelled, order_refunded) that Braze validates for platform features; the Places Order conversion event was added in early access.

    The April 30 GA entry says "eCommerce recommended events cover six steps in the purchase journey"; the February early access added "Places Order". Evidence: braze.com ↗

  95. Text Braze · eCommerce recommended events
    Name rewritten

    Before: 'Places Order' eCommerce recommended event

    After: eCommerce recommended events

    The GA entry is the six-event framework "eCommerce recommended events", not the single Places Order event. Evidence: braze.com ↗

  96. Merged Bloomreach · bloomreach-engagement.postgresql-redshift-general-catalogs

    Record bloomreach-engagement.postgresql-redshift-general-catalogs merged into PostgreSQL/Redshift import source for item collections.

    Same connector: release 1.313 already says "Available only for item collection imports in Data hub, and for customer, event, catalog, voucher imports in Marketing"; 1.314 republishes it. Evidence: documentation.bloomreach.com ↗

  97. Source Adobe AJO · Decisioning rules and ranking via Coworker

    GA sources: experienceleague.adobe.com/en/docs/journey-optimizer/using/whats-new/release-not → experienceleague.adobe.com/en/docs/journey-optimizer/using/whats-new/release-not

    The October 22 entry "Decisioning rule generation skill in Coworker" links the same Rules & Ranking skill page; cited here, no new state. Evidence: experienceleague.adobe.com ↗

  98. Text Adobe AJO · Natural-language Decisioning rule generation
    Summary rewritten

    Before: Coworker generates, simulates and optimizes Decisioning eligibility rules and ranking formulas from natural-language prompts, without PQL syntax.

    After: Marketers can describe a Decisioning rule in plain language in the rule builder and let AI generate it; available to a set of organizations with Adobe AI capabilities (Limited Availability).

    Summary restored to the rule-builder feature ("describe the Decisioning rule you want to create in plain language"), still in Limited Availability. Evidence: experienceleague.adobe.com ↗

  99. Lifecycle state Adobe AJO · Natural-language Decisioning rule generation

    GA state: 22 Oct 2026 → not recorded

    The October 22 entry is the "Decisioning rule generation skill in Coworker" (same #rules-ranking page as the Coworker Rules & Ranking skill, GA 16 Sep), not the rule editor feature in Limited Availability. Evidence: experienceleague.adobe.com ↗

  100. Promised date Adobe AJO · Content preview in journey canvas

    Announced promised state: GA → none

    "Target availability date: September 28, 2026" does not say which availability (GA, beta, early access) is promised. Evidence: experienceleague.adobe.com ↗

  101. Lifecycle state Bloomreach · LINE messaging channel

    Lifecycle state: GA (regional) · 8 Jul 2026 · JP, TW, TH → GA · 8 Jul 2026 · Global

    "Reach LINE customers in Japan, Taiwan, and Thailand" names where LINE users are; the channel is not restricted to Bloomreach customers in some regions. Evidence: documentation.bloomreach.com ↗

  102. Text Braze · Android SDK 42
    Summary rewritten

    Before: Android SDK 42.x: BannerDismissSnapshot fields passed to onDismissCallback are now non-null; the callback is skipped with a warning if identifiers can't be resolved.

    After: Android SDK 42 (42.0.0) ships in-app message and Banner fixes; from 42.3.0, BannerDismissSnapshot fields passed to onDismissCallback are non-null and the callback is skipped with a warning if identifiers can't be resolved.

    Summary rewritten for the 42 major, keeping the 42.3.0 breaking change ("BannerDismissSnapshot fields ... are now non-null"). Evidence: braze.com ↗

  103. Text Braze · Android SDK 42
    Name rewritten

    Before: Android SDK 42.x breaking change: non-null Banner dismiss snapshot fields

    After: Android SDK 42

    Recorded as the SDK major (42.0.0, April 30), not the 42.3.0 change alone. Evidence: braze.com ↗

  104. Date Braze · Android SDK 42

    GA date: 25 Jun 2026 → 30 Apr 2026

    One feature per SDK major: the April 30, 2026 release notes list "Android SDK 42.0.0"; 42.3.0 (June 25) is a later minor. Evidence: braze.com ↗

  105. Lifecycle state Adobe AJO · Loyalty Challenges

    Announced state: 20 Apr 2026 → not recorded

    The MarTech Watch row dates the item "Private beta (Jul 28)"; "announced 20 April 2026" refers to the parent application, not Loyalty Challenges. Evidence: experienceleague.adobe.com ↗

  106. Source Braze · SCIM provisioning for Okta and Microsoft Entra ID groups

    Preview sources: braze.com/docs/releases/2026/9_17_26 → braze.com/docs/releases/2026/9_17_26

    The preview state cited only the 27 Sep snapshot ("General availability"); the 1 Oct snapshot of the same notes says "Early access". Evidence: braze.com ↗

  107. Text Adobe AJO · Execution metadata helper function
    Summary rewritten

    Before: The executionMetadata helper function is now open to all customers to append and export contextual data on native actions.

    After: The executionMetadata helper function, previously in Limited Availability, is available to all Journey Optimizer customers to append contextual data to native actions and capture it in a dataset for export.

    The February entry says "Previously released in Limited Availability" without a date: mentioned in the summary, not as a dated state. Evidence: experienceleague.adobe.com ↗

  108. Lifecycle state Adobe AJO · Execution metadata helper function

    Preview state: 27 Jan 2026 → not recorded

    The January 27 entry announces the helper "now available in the personalization editor for Orchestrated campaigns" with no Limited Availability label; the earlier LA is mentioned undated in February. Evidence: experienceleague.adobe.com ↗

  109. Merged Iterable · iterable.mcp-server

    Record iterable.mcp-server merged into MCP Server support for Gemini CLI, Windsurf and Google Antigravity.

    A bundle of MCP Server updates split into its named capabilities (new AI clients, Windows DPAPI encryption, send-safety permissions, experiment tools); the source lists them as new capabilities, not "performance fixes". Evidence: support.iterable.com ↗

  110. Text Iterable · Google Ads audience integration
    Summary rewritten

    Before: Syncs static and dynamic Iterable lists into Google Ads Customer Match for lookalike audiences; GA added a journey tile to export audiences.

    After: Syncs static and dynamic Iterable lists into Google Ads Customer Match to build lookalike audiences across paid and owned channels.

    The journey tile ("exporting audiences to Google Ads from Iterable journeys with the Google Ads journey tile") is recorded as its own feature. Evidence: support.iterable.com ↗

  111. Merged Iterable · iterable.data-sync-edc-sftp-export

    Record iterable.data-sync-edc-sftp-export merged into Data Sync on the EU data center.

    Three releases in one record, split into Data Sync on the EU data center, the SFTP destination and user profile field export: "now available for hosting on Iterable's European data center (EDC)". Evidence: support.iterable.com ↗

  112. Removed Braze · Braze Docs MCP for IDEs

    Record removed: Braze Docs MCP for IDEs.

    Documentation-only: the entry connects IDEs "to the Braze Docs MCP through Context7" to give assistants "access to current Braze documentation"; not a platform capability. Evidence: braze.com ↗

  113. Removed Bloomreach · React Native SDK 4.2.1

    Record removed: React Native SDK 4.2.1.

    A patch release (4.2.1): the entry only says "Build your Android apps on the latest React Native versions"; no named capability and no stated minimum raise, so the SDK rule skips it. Evidence: documentation.bloomreach.com ↗

  114. Date SFMC Next · Adaptive Campaign Audiences for multi-campaign qualification

    Beta date: 1 Sep 2026 → 1 Oct 2026

    Dated to the release month, but the vendor text naming the feature follows the article's "When: Available in late October 2026." and describes it as part of setting up those campaigns. Evidence: help.salesforce.com ↗

  115. Removed Klaviyo · In-app review prompt for app marketplace listings

    Record removed: In-app review prompt for app marketplace listings.

    Out of scope: a banner asking merchants to review Klaviyo's apps on marketplace listings, not a marketing capability; the What's New entry was removed the day after it appeared. Evidence: klaviyo.com ↗

  116. Text Hightouch · Copy audience filters into audience traits
    Summary rewritten

    Before: Filter conditions from an audience, including related and event model conditions, can be copied directly into the trait enrichment builder.

    After: Filter conditions from an audience, including related and event model conditions, can be copied directly into the audience trait builder.

    Hightouch edited its May 2026 changelog entry: the filters are copied into the "audience trait builder", not the trait enrichment builder. Evidence: hightouch.com ↗

  117. Lifecycle state SFMC Next · Custom HTML landing pages and forms

    Lifecycle state: GA · Sep 2026 → Announced · Sep 2026

    The Winter '27 notes listed it, but the change log (week of October 12, 2026) says: "These features aren't quite ready yet, so we removed them for now." Evidence: help.salesforce.com ↗

  118. Promised date SFMC Engagement · Reuse of Engagement images in Marketing Cloud Next via DAM Connect

    Announced promised date: 20 Nov 2026 → 18 Dec 2026

    The release note's 'When' line now says the feature is "planned for availability after December 18, 2026" (was November 20). Evidence: help.salesforce.com ↗

  119. Date Adobe AJO · Self-serve setup for high-throughput email

    GA date: 28 Oct 2026 → 26 Oct 2026

    Adobe revised the entry: Availability date October 26, 2026 (was October 28), and the self-serve setup now covers email and push. Evidence: experienceleague.adobe.com ↗

  120. Date Adobe AJO · Email Designer collaboration tools

    GA date: Sep 2026 → 25 Sep 2026

    Adobe corrected the Availability date of the entry, first published with a 2024 year typo, to "September 25, 2026". Evidence: experienceleague.adobe.com ↗

  121. Lifecycle state SFMC Next · Integrated WhatsApp payment links in India

    Lifecycle state: GA → GA (regional)

    Availability limited to IN is regional: recorded as GA (regional), as the state rules define it; the restricted regions were already on the record. Evidence: help.salesforce.com ↗

  122. Lifecycle state SFMC Next · Short code procurement for SMS in the US and Canada

    Lifecycle state: GA → GA (regional)

    Availability limited to US, CA is regional: recorded as GA (regional), as the state rules define it; the restricted regions were already on the record. Evidence: help.salesforce.com ↗

  123. Lifecycle state SFMC Next · DLT template upload for SMS sending in India

    Lifecycle state: GA → GA (regional)

    Availability limited to IN is regional: recorded as GA (regional), as the state rules define it; the restricted regions were already on the record. Evidence: help.salesforce.com ↗

  124. Lifecycle state SFMC Engagement · WhatsApp payment processing in Brazil

    Lifecycle state: GA → GA (regional)

    Availability limited to BR is regional: recorded as GA (regional), as the state rules define it; the restricted regions were already on the record. Evidence: help.salesforce.com ↗

  125. Lifecycle state SFMC Engagement · In-chat WhatsApp payment options in India

    Lifecycle state: GA → GA (regional)

    Availability limited to IN is regional: recorded as GA (regional), as the state rules define it; the restricted regions were already on the record. Evidence: help.salesforce.com ↗

  126. Lifecycle state SFMC Engagement · Shared US/Canada SMS short and long codes with Marketing Cloud Next

    Lifecycle state: GA → GA (regional)

    Availability limited to US, CA is regional: recorded as GA (regional), as the state rules define it; the restricted regions were already on the record. Evidence: help.salesforce.com ↗

  127. Lifecycle state Klaviyo · State-law text frequency limits

    Lifecycle state: GA → GA (regional)

    Availability limited to US is regional: recorded as GA (regional), as the state rules define it; the restricted regions were already on the record. Evidence: klaviyo.com ↗

  128. Lifecycle state Klaviyo · klaviyo.pay-in-cad

    Lifecycle state: GA → GA (regional)

    Availability limited to CA is regional: recorded as GA (regional), as the state rules define it; the restricted regions were already on the record. Evidence: klaviyo.com ↗

  129. Lifecycle state Adobe AEP · The Trade Desk Third-Party Audiences destination

    Lifecycle state: GA → GA (regional)

    Availability limited to US is regional: recorded as GA (regional), as the state rules define it; the restricted regions were already on the record. Evidence: experienceleague.adobe.com ↗

  130. Lifecycle state Adobe AEP · adobe-experience-platform.sources-nld2-ip-allowlist-update

    Lifecycle state: GA → GA (regional)

    Availability limited to EU is regional: recorded as GA (regional), as the state rules define it; the restricted regions were already on the record. Evidence: experienceleague.adobe.com ↗

  131. Text HubSpot · AI credits spend controls
    Summary rewritten

    Before: First-time AI credit purchasers get a default spend cap of 50% above monthly credits with Pay-as-You-Go overage billing; admins can set account, feature and action limits.

    After: First-time AI credit purchasers get a default spend cap of 50% above monthly credits, with Pay-as-You-Go overage billing from 16 September; admins can set account, feature and action limits.

    Summary keeps 16 September as the start of Pay-as-You-Go overage billing. Evidence: community.hubspot.com ↗

  132. Date HubSpot · AI credits spend controls

    Date: GA · 16 Sep 2026 → GA · Sep 2026

    A September 2026 roundup item: "Pay-as-You-Go for overages from September 16" dates only the overage billing, not the spend caps and limits. Evidence: community.hubspot.com ↗

  133. Date Marketo AI was renamed Coworker for Marketo Engage, with the same agent skills made available to all users.

    Date: Aug 2026 → 14 Aug 2026

    The rename is announced on the August 2026 release notes page of 14 August ("Marketo AI is now Coworker for Marketo Engage"); the page date applies. Evidence: experienceleague.adobe.com ↗

  134. Date Marketo · Coworker for Marketo Engage agent skills

    Date: GA · Aug 2026 → GA · 14 Aug 2026

    The August 2026 release notes page (14 August) announces "Marketo AI is now Coworker for Marketo Engage ... available to all users"; the row has no own date, so the page date applies. Evidence: experienceleague.adobe.com ↗

  135. Date HubSpot · Campaigns as a connected CRM object

    Date: GA · 27 Apr 2026 → GA · Apr 2026

    Dated by the Smart CRM recap of 27 April ("In Q1, we expanded..."). The April 2026 roundup: "Associate custom objects with campaigns: Enterprise customers can now associate...". Evidence: community.hubspot.com ↗

  136. Removed HubSpot · Prospecting Agent for Starter

    Record removed: Prospecting Agent for Starter.

    Out of scope: Prospecting Agent is a Sales Hub agent; the April 2026 roundup says "Live for Sales Hub Starter, Professional, and Enterprise (Prospecting Agent)". Evidence: community.hubspot.com ↗

  137. Removed HubSpot · Health score history change detail

    Record removed: Health score history change detail.

    Out of scope: "Improved Score History for Health Scores" sits under "What's New for Support & Success" in the August 2026 roundup; customer-success health scores are a Service Hub capability. Evidence: community.hubspot.com ↗

  138. Lifecycle state Tealium · Context API

    Lifecycle state: Announced · 9 Jun 2026 → GA · 9 Jun 2026

    The MarTech Watch row can only record an announcement; the vendor's own archived press release states general availability. Tealium's press release of 9 June 2026 says "Tealium Context API solution is now available globally". Evidence: tealium.com ↗

  139. Lifecycle state Braze · BrazeAI Operator agent

    Lifecycle state: Announced · 23 Apr 2026 → GA · 23 Apr 2026

    The MarTech Watch row can only record an announcement; the vendor's own archived press release states general availability. The Braze press release of 23 April 2026 is headed "BrazeAI Operator and BrazeAI Agent Console, now generally available". Evidence: braze.com ↗

  140. Lifecycle state Bloomreach · Loomi Marketing Agent

    Lifecycle state: Announced · week of 8 Jun 2026 → GA · 2 Jun 2026

    The MarTech Watch row can only record an announcement; the vendor's own archived press release states general availability. Bloomreach "today announced the general availability of its Loomi marketing agent" (press release, 2 June 2026). Evidence: bloomreach.com ↗

  141. Lifecycle state Adobe AEP · CX Enterprise Coworker

    Lifecycle state: Announced · 10 Jun 2026 → GA · 10 Jun 2026

    The MarTech Watch row can only record an announcement; the vendor's own archived press release states general availability. Adobe "today announced the general availability of Adobe CX Enterprise Coworker" (media alert, 10 June 2026). Evidence: news.adobe.com ↗

  142. Removed HubSpot · Marketplace credential broker app policy

    Record removed: Marketplace credential broker app policy.

    Out of scope: a HubSpot Marketplace listing policy for third-party apps ("Apps whose primary purpose is selling OAuth or credential storage will be removed"), not a product capability. Evidence: community.hubspot.com ↗

  143. Text SF Account Engagement · Per-business-unit email open and click tracking controls
    Summary rewritten

    Before: Account Engagement adds four per-business-unit settings to enable or disable tracking of email opens, implied opens, link clicks and advanced metrics, supporting EU tracking rules.

    After: Account Engagement adds four per-business-unit settings to enable or disable tracking of email opens, implied opens, link clicks and advanced metrics, supporting EU tracking rules; the advanced metrics setting needs Plus, Advanced, Premium or Growth with the add-on.

    The Advanced Email Analytics setting "is available in ... Plus, Advanced, and Premium editions, as well as Growth Edition with the add-on". Evidence: help.salesforce.com ↗

  144. Merged SF Account Engagement · salesforce-account-engagement.advanced-email-analytics-tracking-control

    Record salesforce-account-engagement.advanced-email-analytics-tracking-control merged into Per-business-unit email open and click tracking controls.

    Same capability recorded twice: the Winter '27 entry "Disable Email Open and Click Tracking" restates the Summer '26 entry; both sources are cited on the kept record. Evidence: help.salesforce.com ↗

  145. Date HubSpot · User object CRM associations and visibility

    Date: GA · 27 Apr 2026 → GA · Aug 2026

    Dated by the Smart CRM recap of 27 April, updated during the year. The August 2026 roundup: "The User object now supports associations, pipelines, and segments". Evidence: community.hubspot.com ↗

  146. Merged HubSpot · hubspot-marketing-hub.user-object-associations-pipelines-segments

    Record hubspot-marketing-hub.user-object-associations-pipelines-segments merged into User object CRM associations and visibility.

    Same capability recorded twice (August 2026 roundup and the Smart CRM recap); both sources are cited on the kept record. Evidence: community.hubspot.com ↗

  147. Date HubSpot · TikTok Ads integration

    Date: GA · Apr 2026 → GA · 3 Apr 2026

    HubSpot's launch post of 3 April 2026 says "Get started by connecting TikTok ads directly to HubSpot"; the April roundup is kept as a second source. Evidence: community.hubspot.com ↗

  148. Text HubSpot · TikTok organic publishing and engagement
    Summary rewritten

    Before: TikTok connects natively to HubSpot's CRM: teams run TikTok ad campaigns, create, schedule and publish organic posts, reply to comments and track performance alongside other social channels.

    After: TikTok connects natively to HubSpot's social tool: teams create, schedule and publish organic TikTok posts, reply to comments and track performance alongside other social channels.

    TikTok organic: "Create, schedule, and publish TikTok posts, reply to comments". The ads part is recorded as TikTok Ads integration. Evidence: community.hubspot.com ↗

  149. Text HubSpot · TikTok organic publishing and engagement
    Name rewritten

    Before: Native TikTok integration

    After: TikTok organic publishing and engagement

    Name restricted to the "TikTok organic" entry of the April 2026 roundup. Evidence: community.hubspot.com ↗

  150. Classification HubSpot · TikTok organic publishing and engagement

    Classification: Organic social publishing (also Paid media audiences) → Organic social publishing

    The April 2026 roundup has separate "TikTok organic" and "TikTok Ads" entries; this record now covers organic only, ads are recorded as TikTok Ads integration. Evidence: community.hubspot.com ↗

  151. Text HubSpot · Data enrichment for EU contacts
    Summary rewritten

    Before: New data sources fill gaps in job title, company and location fields for EU-based contacts, improving enrichment coverage for that region.

    After: New data sources fill gaps in job title, company and location fields, particularly for EU-based contacts, improving data enrichment coverage in HubSpot's Smart CRM.

    Summary no longer implies availability limited to one region. Evidence: community.hubspot.com ↗

  152. Lifecycle state HubSpot · Data enrichment for EU contacts

    Lifecycle state: GA (regional) · 3 Mar 2026 · EU → GA · 3 Mar 2026 · Global

    The new data sources improve coverage "particularly for EU-based businesses"; enrichment "is included with HubSpot's Smart CRM". Availability is not restricted to a region. Evidence: community.hubspot.com ↗

  153. Date SF Account Engagement · Device-validation privacy check on hosted forms

    Date: GA · Jan 2026 → GA · Feb 2026

    Dated to the Spring '26 release. Its section page says "This change is available on a rolling basis in February 2026"; a rollout to all editions is GA. Evidence: help.salesforce.com ↗

  154. Removed SF Account Engagement · "Via" tag on system emails to Google Groups

    Record removed: "Via" tag on system emails to Google Groups.

    Out of the timeline: the Spring '26 release note says "This change began on October 11, 2025", before history starts on 1 January 2026. Evidence: help.salesforce.com ↗

  155. Removed SF Account Engagement · Consent matching with Marketing Cloud Next

    Record removed: Consent matching with Marketing Cloud Next.

    Out of the timeline: the Spring '26 release note says "This change became available in October 2025", before history starts on 1 January 2026. Evidence: help.salesforce.com ↗

  156. Date HubSpot · Marketing Events as a full CRM object

    Date: GA · 27 Apr 2026 → GA · Apr 2026

    Dated by the Smart CRM recap of 27 April ("In Q1, we expanded..."). The April 2026 roundup: "A redesigned Marketing Event record page", "Live for all hubs and tiers". Evidence: community.hubspot.com ↗

  157. Date HubSpot · AEO analysis via the Claude connector

    Date: GA · 15 Sep 2026 → GA · Sep 2026

    Dated by the MCP Spotlight recap of 15 September. The September 2026 roundup says the Claude connector "can now retrieve intent signals, AEO performance"; the recap is kept as a second source. Evidence: community.hubspot.com ↗

  158. Text HubSpot · Salesforce sync v2 for deal objects
    Summary rewritten

    Before: Deal object sync to Salesforce is planned to migrate to the rebuilt v2 engine, bringing the same de-duplication, owner-sync, and error-handling improvements as other migrated objects.

    After: Deal object sync to Salesforce runs on the rebuilt v2 engine in beta, with the same de-duplication, owner-sync and error-handling improvements as other migrated objects.

    Summary no longer describes the deal migration as planned: it is in beta. Evidence: community.hubspot.com ↗

  159. Lifecycle state HubSpot · Salesforce sync v2 for deal objects

    Beta state: not recorded → Confirmed by 8 Jun 2026

    HubSpot's reply of 8 June 2026 on the announcement thread lists objects migrated to v2: "Deals (now in beta)". The announcement stays in the history. Evidence: community.hubspot.com ↗

  160. Text HubSpot · Manual participant status updates for marketing events
    Summary rewritten

    Before: A contact's marketing event registration or participation status can be edited directly from the Marketing Events CRM card, without re-importing data.

    After: In public beta: a contact's marketing event registration or participation status can be edited directly from the Marketing Events CRM card, without re-importing data.

    Summary now states the public beta. Evidence: community.hubspot.com ↗

  161. Lifecycle state HubSpot · Manual participant status updates for marketing events

    Lifecycle state: GA · Feb 2026 → Beta · Feb 2026

    The February 2026 roundup lists it under "Now in Public Beta" ("open to all eligible customers, no waitlist required"), not as generally available. Evidence: community.hubspot.com ↗

  162. Text Tealium · Moments API in CloudStream
    Summary rewritten

    Before: Moments API integrates directly with CloudStream, letting apps retrieve real-time visitor data from cloud-warehouse-based segments.

    After: Moments API (renamed Context API in October 2026) integrates directly with CloudStream, letting apps retrieve real-time visitor data from cloud-warehouse-based segments.

    Summary notes the vendor's rename of Moments API to Context API. Evidence: docs.tealium.com ↗

  163. Source Tealium · Moments API in CloudStream

    GA sources: 1 source → 4 sources

    The later recaps (30 June, 31 August, 30 October 2026) list the same entry; those of 31 August and 30 October mark it "(sign up required*)". The earliest state is kept. Evidence: docs.tealium.com ↗

  164. Merged Tealium · tealium.context-api-cloudstream-integration

    Record tealium.context-api-cloudstream-integration merged into Moments API in CloudStream.

    The recap of 30 October 2026 says "Moments API has been renamed to Context API"; "Context API in CloudStream" repeats the Moments API in CloudStream entry word for word. Evidence: docs.tealium.com ↗

  165. Date Treasure AI · Rule-editor audience building in Personalization Studio

    Date: Oct 2026 → 30 Oct 2026

    The entry "Audiences Built in the Rule Editor" carries its own date, "Posted on: Oct 30, 2026"; it had been dated to the page month. Evidence: docs.treasure.ai ↗

  166. Date Treasure AI · Journey and user attribution in Composable Audience Studio Snowflake query tags

    Date: Sep 2026 → 22 Sep 2026

    The entry "Snowflake Query Tags: Journey and User Attribution" carries its own date, "Posted on: Sep 22, 2026"; it had been dated to the page month. Evidence: docs.treasure.ai ↗

  167. Date Treasure AI · Deep link recording with external metadata for AI Voice

    Date: Sep 2026 → 30 Sep 2026

    The entry "Deep Link Recording with External Metadata" carries its own date, "Posted on: Sep 30, 2026"; it had been dated to the page month. Evidence: docs.treasure.ai ↗

  168. Date Treasure AI · Approval gate for AI Studio tdx commands

    Date: Sep 2026 → 30 Sep 2026

    The entry "Approval Before tdx Commands" carries its own date, "Posted on: Sep 30, 2026"; it had been dated to the page month. Evidence: docs.treasure.ai ↗

  169. Date Treasure AI · Google Search Console connector for AI Studio

    Date: Sep 2026 → 30 Sep 2026

    The entry "Google Search Console for AI Studio" carries its own date, "Posted on: Sep 30, 2026"; it had been dated to the page month. Evidence: docs.treasure.ai ↗

  170. Date Treasure AI · Google Calendar connector for AI Studio

    Date: Sep 2026 → 30 Sep 2026

    The entry "Google Calendar for AI Studio" carries its own date, "Posted on: Sep 30, 2026"; it had been dated to the page month. Evidence: docs.treasure.ai ↗

  171. Date Treasure AI · Google Analytics connector for AI Studio

    Date: Sep 2026 → 30 Sep 2026

    The entry "Google Analytics for AI Studio" carries its own date, "Posted on: Sep 30, 2026"; it had been dated to the page month. Evidence: docs.treasure.ai ↗

  172. Date Treasure AI · Agent Channels SDK Apps for AI Studio

    Date: Oct 2026 → 21 Oct 2026

    The entry "Agent Channels with SDK Apps" carries its own date, "Posted on: Oct 21, 2026"; it had been dated to the page month. Evidence: docs.treasure.ai ↗

  173. Removed Tealium · Custom action functions in CloudStream

    Record removed: Custom action functions in CloudStream.

    Tealium's recap of 31 October 2025 already lists "Custom action functions in CloudStream (sign up required*)": its only state predates the history (1 Jan 2026). Evidence: docs.tealium.com ↗

  174. Removed Tealium · CloudStream zero-copy segmentation and activation

    Record removed: CloudStream zero-copy segmentation and activation.

    The dated note "Server-side > CloudStream (November 24, 2025)" says "CloudStream now available": released before the history starts (1 Jan 2026). Evidence: docs.tealium.com ↗

  175. Removed Tealium · Redesigned AudienceStream attributes experience

    Record removed: Redesigned AudienceStream attributes experience.

    Tealium's recap of 31 October 2025 already lists "New AudienceStream attributes experience" without an early-access marker: released before the history starts (1 Jan 2026). Evidence: docs.tealium.com ↗

  176. Text Tealium · Amazon Redshift cloud data source
    Summary rewritten

    Before: Early-access bulk import of Amazon Redshift data into Tealium attributes, near real-time or on a schedule.

    After: Bulk import of Amazon Redshift data into Tealium attributes, near real-time or on a schedule.

    Summary no longer describes the generally available connector as early access. Evidence: docs.tealium.com ↗

  177. Lifecycle state Tealium · SCIM API for user provisioning

    Preview state: 8 Jan 2026 → not recorded

    Tealium's recap of 31 October 2025 already lists "SCIM API for user provisioning (sign up required*)"; the early access predates the history (1 Jan 2026). The GA stays. Evidence: docs.tealium.com ↗

  178. Lifecycle state Tealium · Amazon Redshift cloud data source

    Preview state: 8 Jan 2026 → not recorded

    Tealium's recap of 31 October 2025 already lists "Amazon Redshift, Google BigQuery, and Databricks data cloud inbound (sign up required*)"; the early access predates the history (1 Jan 2026). The GA stays. Evidence: docs.tealium.com ↗

  179. Lifecycle state Tealium · Databricks cloud data source

    Preview state: 8 Jan 2026 → not recorded

    Tealium's recap of 31 October 2025 already lists "Amazon Redshift, Google BigQuery, and Databricks data cloud inbound (sign up required*)"; the early access predates the history (1 Jan 2026). The GA stays. Evidence: docs.tealium.com ↗

  180. Lifecycle state Tealium · Google BigQuery cloud data source

    Preview state: 8 Jan 2026 → not recorded

    Tealium's recap of 31 October 2025 already lists "Amazon Redshift, Google BigQuery, and Databricks data cloud inbound (sign up required*)"; the early access predates the history (1 Jan 2026). The GA stays. Evidence: docs.tealium.com ↗

  181. Lifecycle state Tealium · Audience fill

    Preview state: 8 Jan 2026 → not recorded

    Tealium's recap of 31 October 2025 already lists "Audience fill (sign up required*)"; the early access predates the history (1 Jan 2026). The GA stays. Evidence: docs.tealium.com ↗

  182. Source Adobe AEP · LAVA source connector

    GA sources: 1 source → 2 sources

    The June 2026 release notes, which first state the GA of the LAVA source, are cited; the August notes stay as confirmation. Evidence: experienceleague.adobe.com ↗

  183. Date Adobe AEP · LAVA source connector

    GA date: 18 Aug 2026 → 16 Jun 2026

    The June 2026 release notes (Release date: June 16, 2026) already list "General availability of the LAVA source"; the August list of promotions to GA repeats it. Evidence: experienceleague.adobe.com ↗

  184. Lifecycle state Tealium · Facebook Conversions connector expanded LDU state support

    Regions: US → Global

    The note adds "Limited Data Use (LDU) ... additional US state codes (CO, CT, FL, TX, and others)" as parameter values; availability of the update is not restricted. Evidence: docs.tealium.com ↗

  185. Lifecycle state Adobe AEP · UID2 identity conversion for The Trade Desk - CRM destination

    Lifecycle state: GA · week of 26 Oct 2026 → GA (regional) · week of 26 Oct 2026

    The release notes say the UID2 namespaces "are available only in the The Trade Desk - CRM (NAMER & APAC) destination", not in the EU one: regional availability. Evidence: experienceleague.adobe.com ↗

  186. Text Treasure AI · Open Catalog Access for Snowflake and Databricks
    Summary rewritten

    Before: Publishes Complete CDP tables as an Iceberg catalog so Snowflake and Databricks can query them in place without copying data.

    After: Publishes Complete CDP tables as an Iceberg catalog so Snowflake and Databricks can query them in place without copying data; not enabled by default, turned on by Treasure on request.

    Summary rewritten for the preview state: access is limited. Evidence: docs.treasure.ai ↗

  187. Lifecycle state Treasure AI · Open Catalog Access for Snowflake and Databricks

    Lifecycle state: GA · 16 Aug 2026 → Preview · 16 Aug 2026

    The entry of 16 August 2026 says the integrations "are generally available" but also "not enabled on accounts by default; contact Technical Support or your Customer Success representative to enable it". Evidence: docs.treasure.ai ↗

  188. Text Treasure AI · Mobile push channel
    Summary rewritten

    Before: Native mobile push becomes a first-class Engage Studio channel via Firebase Cloud Messaging, with rich content and personalization.

    After: Native mobile push via Firebase Cloud Messaging as an Engage Studio channel with rich content and personalization; access through the Treasure account team, described as Beta in June 2026.

    Summary rewritten for the preview state: access is limited. Evidence: docs.treasure.ai ↗

  189. Source Treasure AI · Mobile push channel

    Sources: 1 source → 2 sources

    The June 2026 note, which says "Mobile Push is currently a Beta feature.", is cited as evidence of the channel's limited availability. Evidence: docs.treasure.ai ↗

  190. Lifecycle state Treasure AI · Mobile push channel

    Lifecycle state: GA · Feb 2026 → Preview · Feb 2026

    The February 2026 note says "Talk to your Treasure account team to get started" and the note of 3 June 2026 says "Mobile Push is currently a Beta feature." Evidence: docs.treasure.ai ↗

  191. Text Treasure AI · Mobile push campaign management and editor
    Summary rewritten

    Before: Adds full campaign editor support for FCM mobile push: message type selection, tap behavior, image validation, and delivery error logs.

    After: Campaign editor support for FCM mobile push in Engage Studio: message type, tap behavior, image validation and delivery error logs; enabled on request by the Treasure account team.

    Summary rewritten for the preview state: access is limited. Evidence: docs.treasure.ai ↗

  192. Lifecycle state Treasure AI · Mobile push campaign management and editor

    Lifecycle state: GA · Feb 2026 → Preview · Feb 2026

    The February 2026 note says "contact your Treasure account team to enable Mobile Push (Firebase) configuration": enabled on request, so limited availability. Evidence: docs.treasure.ai ↗

  193. Text Treasure AI · iOS push delivery and dismiss event tracking
    Summary rewritten

    Before: iOS Mobile Push payloads now include fields enabling delivery and dismiss event tracking, complementing existing open and link-open events.

    After: iOS Mobile Push payloads include fields for delivery and dismiss event tracking, complementing open and link-open events; part of the Mobile Push channel, still in Beta.

    Summary rewritten for the preview state: access is limited. Evidence: docs.treasure.ai ↗

  194. Lifecycle state Treasure AI · iOS push delivery and dismiss event tracking

    Lifecycle state: GA · 3 Jun 2026 → Preview · 3 Jun 2026

    The entry of 3 June 2026 says "Mobile Push is currently a Beta feature."; the channel is enabled through the Treasure account team, so limited availability. Evidence: docs.treasure.ai ↗

  195. Lifecycle state Adobe AEP · FreeWheel destination

    Lifecycle state: GA · 24 Mar 2026 → Preview · 24 Mar 2026

    The March 2026 release notes (24 March) end the FreeWheel entry with "Contact your Adobe account team for access.": access on request is limited availability. Evidence: experienceleague.adobe.com ↗

  196. Lifecycle state Tealium · Context API

    Lifecycle state: GA · 9 Jun 2026 → Announced · 9 Jun 2026

    The only archived source is a MarTech Watch row ("Status in the watch: Launched (Jun 9)"); Watch rows record announcements only until a vendor release note dates availability. Evidence: tealium.com ↗

  197. Lifecycle state Adobe AEP · CX Enterprise Coworker

    Lifecycle state: GA · 10 Jun 2026 → Announced · 10 Jun 2026

    The only archived source is a MarTech Watch row ("Status in the watch: GA (Jun 10)"); Watch rows record announcements only until a vendor release note dates availability. Evidence: news.adobe.com ↗

  198. Removed SFMC Next · New WhatsApp message types and conversation enhancements

    Record removed: New WhatsApp message types and conversation enhancements.

    A Spring '26 section page, not a feature: its entries (contact messages, time-sensitive offers, stickers, MM Lite and Brazil payments) are each recorded on their own. Evidence: help.salesforce.com ↗

  199. Removed SFMC Next · Richer personalized emails with shared template control

    Record removed: Richer personalized emails with shared template control.

    A Spring '26 section page, not a feature: its entries (shared templates, template locks, advanced data sources, PDF attachments, Handlebars and the rich text editor) are each recorded on their own. Evidence: help.salesforce.com ↗

  200. Removed SFMC Next · Mobile app engagement messaging and interaction tracking

    Record removed: Mobile app engagement messaging and interaction tracking.

    A Spring '26 section page, not a feature: its entries (in-app messages, flash notifications (pilot) and custom mobile app events) are each recorded on their own. Evidence: help.salesforce.com ↗

  201. Merged SFMC Next · salesforce-marketing-cloud-next.buyer-engagement-agent-sales-pipeline-conversion

    Record salesforce-marketing-cloud-next.buyer-engagement-agent-sales-pipeline-conversion merged into Buyer Engagement Agent.

    Same agent: the full title "Turn Marketing Leads into Qualified Sales Pipeline with the Buyer Engagement Agent" is the note already recorded as the Buyer Engagement Agent. Evidence: help.salesforce.com ↗

  202. Removed SFMC Next · Conversational billing over RCS

    Record removed: Conversational billing over RCS.

    A billing model, not a capability: RCS messages exchanged with a customer within 24 hours "are billed as one conversation" outside the US. Recorded as signal salesforce-marketing-cloud-next.signal.rcs-conversational-billing. Evidence: help.salesforce.com ↗

  203. Date SFMC Next · WhatsApp business-scoped user ID messaging

    Date: GA · Sep 2026 → GA · May 2026

    The same entry, "Reach WhatsApp Users with Usernames Using Business-Scoped User IDs", is in the Summer '26 Other Changes; dated to that release. Evidence: help.salesforce.com ↗

  204. Text SFMC Next · View email as a web page
    Summary rewritten

    Before: Recipients can view a sent marketing email rendered as a standalone web page.

    After: Marketers will be able to add a View As Web Page link to emails so recipients can open a browser version when their email app renders the message badly; planned from November 2026.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  205. Promised date SFMC Next · View email as a web page

    Promised date: none → Nov 2026

    The snapshots of 24 and 28 October 2026 say "The View as Web Page feature is available starting in November 2026." Evidence: help.salesforce.com ↗

  206. Lifecycle state SFMC Next · View email as a web page

    Lifecycle state: GA · Sep 2026 → Announced · Sep 2026

    The snapshots of 24 and 28 October 2026 say "The View as Web Page feature is available starting in November 2026." Evidence: help.salesforce.com ↗

  207. Date SFMC Next · Simplified retail trigger setup with data-cost control

    Date: GA · Sep 2026 → GA · week of 26 Oct 2026

    The change log says "Simplify Trigger Setup and Control Data Costs (Added the week of October 26, 2026)"; earlier snapshots do not contain it. Evidence: help.salesforce.com ↗

  208. Text SFMC Next · Preview personalized content as a recipient
    Summary rewritten

    Before: Preview and test personalized email content as it would render for a chosen recipient.

    After: Preview and test personalized content as list, individual or campaign recipients across email, SMS, WhatsApp, mobile app and RCS, rolled out by channel in phases in October and November 2026.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  209. Date SFMC Next · Preview personalized content as a recipient

    Date: GA · Sep 2026 → GA · Oct 2026

    The When section says the enhancements "become available for different channels in phases throughout October 2026" (later: October and November); a phased rollout to all is GA. Evidence: help.salesforce.com ↗

  210. Date SFMC Next · Marketing Object data sync with Data 360

    Date: Announced · Sep 2026 → Announced · week of 21 Sep 2026

    The entry is "Added the week of September 21, 2026"; the note says "The Data 360 sync feature is available starting mid-November 2026." Evidence: help.salesforce.com ↗

  211. Merged SFMC Next · salesforce-marketing-cloud-next.content-block-scripting-personalization

    Record salesforce-marketing-cloud-next.content-block-scripting-personalization merged into Scripting-based content personalization across channels.

    Duplicate: "Personalize Content in Channels with Scripting Support" is a Winter '27 note only; the Summer '26 notes do not contain it, so its May 2026 GA had no source. Evidence: help.salesforce.com ↗

  212. Source SFMC Next · Centralized web tracking and consent banner setup

    Source: Summer '26 release notes → Winter '27 release notes

    "Centralize Your Web Tracking and Consent Banner Setup" is a Winter '27 note; the Summer '26 notes do not contain it. Evidence: help.salesforce.com ↗

  213. Date SFMC Next · Centralized web tracking and consent banner setup

    Date: GA · May 2026 → GA · Sep 2026

    "Centralize Your Web Tracking and Consent Banner Setup" is a Winter '27 note; the Summer '26 notes do not contain it. Evidence: help.salesforce.com ↗

  214. Date SFMC Next · Independent Sales Data Kit management

    Date: GA · Sep 2026 → GA · Aug 2026

    The Winter '27 note says "available on a rolling basis starting in August 2026"; a rolling rollout is GA. The entry is also in Summer '26 Other Changes. Evidence: help.salesforce.com ↗

  215. Date SFMC Next · Add fields and records to Marketing Objects

    Date: GA · Sep 2026 → GA · Aug 2026

    The Summer '26 and Winter '27 notes both say "This functionality is available starting August 2026." Evidence: help.salesforce.com ↗

  216. Date SFMC Next · Marketing completion actions for follow-up tasks

    Date: GA · Sep 2026 → GA · Aug 2026

    Listed in the Summer '26 Other Changes; the Winter '27 note says "This functionality is available starting August 2026." Evidence: help.salesforce.com ↗

  217. Date SFMC Next · Faster sends to Contact and Lead lists

    Date: GA · May 2026 → GA · Aug 2026

    The Summer '26 note says "This feature is available starting mid-August."; a When note wins over the release date. Evidence: help.salesforce.com ↗

  218. Date SFMC Next · Email image recommenders

    Date: GA · Sep 2026 → GA · Aug 2026

    The Summer '26 entry "Choose the Best Image with Recommenders" says "This functionality is available starting August 2026." Evidence: help.salesforce.com ↗

  219. Date SFMC Next · B2B Analytics for Marketers dashboards

    Date: GA · May 2026 → GA · 10 Aug 2026

    The Summer '26 note says "This feature is available beginning August 10, 2026."; a When note wins over the release date. Evidence: help.salesforce.com ↗

  220. Text SFMC Next · Unified Engagement History dashboard on Opportunity records
    Summary rewritten

    Before: Extends the Unified Engagement History dashboard to Opportunity records so sales reps can see related marketing engagement.

    After: Sales reps will see a Unified Engagement History dashboard on Opportunity records with related contacts' email, form and page-view engagement; Salesforce says it comes later in Summer '26.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  221. Lifecycle state SFMC Next · Unified Engagement History dashboard on Opportunity records

    Lifecycle state: GA · May 2026 → Announced · May 2026

    The Summer '26 note says "This feature becomes available later in Summer '26."; no later source confirms availability. Evidence: help.salesforce.com ↗

  222. Lifecycle state SFMC Next · WhatsApp payment options in Brazil

    Lifecycle state: GA · Jan 2026 → GA (regional) · Jan 2026

    The Spring '26 note says "This message template is currently available only for Brazil."; restricted regions are ga_regional. Evidence: help.salesforce.com ↗

  223. Lifecycle state SFMC Next · Rich MMS messages

    Lifecycle state: GA · May 2026 · Global → GA (regional) · May 2026 · US, CA

    The Summer '26 note says "Sending MMS messages is only supported in the United States and Canada." Evidence: help.salesforce.com ↗

  224. Lifecycle state SFMC Next · Rich Communication Services (RCS) channel support

    Lifecycle state: GA · May 2026 · Global → GA (regional) · May 2026 · US, GB, MX, BR, DE, IN, FR

    The Summer '26 note says "RCS messaging can reach customers in the US, UK, Mexico, Brazil, Germany, India, and France." Evidence: help.salesforce.com ↗

  225. Lifecycle state SFMC Next · RCS messaging for additional countries

    Lifecycle state: GA · Sep 2026 → GA (regional) · Sep 2026

    The note names the countries: "Reach customers with RCS messaging in more countries, including Canada, Colombia, Italy…"; restricted regions are ga_regional. Evidence: help.salesforce.com ↗

  226. Text SFMC Next · Marketing Sites configuration
    Summary rewritten

    Before: New Marketing Sites tab centralizes configuration of landing page site settings.

    After: A Marketing Sites tab for landing page site configuration, listed in the Winter '27 notes and withdrawn by Salesforce in October 2026 because the feature was not ready yet.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  227. Lifecycle state SFMC Next · Marketing Sites configuration

    Lifecycle state: GA · Sep 2026 → Announced · Sep 2026

    The Winter '27 notes listed it, but the change log (week of October 12, 2026) says: "These features aren't quite ready yet, so we removed them for now." Evidence: help.salesforce.com ↗

  228. Text SFMC Next · Landing page personalization with Handlebars and AMPscript
    Summary rewritten

    Before: Landing pages support Handlebars and AMPscript templating for dynamic personalization.

    After: Handlebars and AMPscript personalization for landing pages, listed in the Winter '27 notes and withdrawn by Salesforce in October 2026 because the feature was not ready yet.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  229. Lifecycle state SFMC Next · Landing page personalization with Handlebars and AMPscript

    Lifecycle state: GA · Sep 2026 → Announced · Sep 2026

    The Winter '27 notes listed it, but the change log (week of October 12, 2026) says: "These features aren't quite ready yet, so we removed them for now." Evidence: help.salesforce.com ↗

  230. Text SFMC Next · More data source connections for forms and landing pages
    Summary rewritten

    Before: Connect forms and landing pages to a wider range of data sources to drive visitor experiences.

    After: Connections from forms and landing pages to more data sources, listed in the Winter '27 notes and withdrawn by Salesforce in October 2026 because the feature was not ready yet.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  231. Lifecycle state SFMC Next · More data source connections for forms and landing pages

    Lifecycle state: GA · Sep 2026 → Announced · Sep 2026

    The Winter '27 notes listed it, but the change log (week of October 12, 2026) says: "These features aren't quite ready yet, so we removed them for now." Evidence: help.salesforce.com ↗

  232. Text SFMC Next · High-volume email archiving to own cloud storage
    Summary rewritten

    Before: Archives high-volume outbound marketing emails into a customer-owned cloud storage location.

    After: Archives copies of high-volume sent marketing emails in the customer's own Microsoft Azure cloud storage with Data 360, where they can be queried and retrieved on the customer's schedule.

    The note says copies are stored "directly in your Microsoft Azure cloud storage with Data 360"; Amazon S3 was removed as a supported location. Evidence: help.salesforce.com ↗

  233. Removed SFMC Next · Removal of Amazon S3 as an email-archiving storage destination

    Record removed: Removal of Amazon S3 as an email-archiving storage destination.

    Not a release: "(Updated the week of September 7, 2026) Removed Amazon S3 as a supported storage location" edits the archiving note, which names Microsoft Azure only. Evidence: help.salesforce.com ↗

  234. Merged SFMC Next · salesforce-marketing-cloud-next.cross-channel-utm-link-parameter-tagging

    Record salesforce-marketing-cloud-next.cross-channel-utm-link-parameter-tagging merged into UTM and custom link parameter tracking.

    Same release note recorded three times: change-log title "Automate UTM and Custom Parameter Tagging" and page title "Track Link Engagement with UTM and Custom Link Parameters"; both are cited on the kept record. Evidence: help.salesforce.com ↗

  235. Merged SFMC Next · salesforce-marketing-cloud-next.automate-utm-parameter-tagging

    Record salesforce-marketing-cloud-next.automate-utm-parameter-tagging merged into UTM and custom link parameter tracking.

    Same release note recorded three times: change-log title "Automate UTM and Custom Parameter Tagging" and page title "Track Link Engagement with UTM and Custom Link Parameters"; both are cited on the kept record. Evidence: help.salesforce.com ↗

  236. Text SFMC Next · UTM and custom link parameter tracking
    Summary rewritten

    Before: Reports link-click engagement using UTM and custom parameters on tracked links.

    After: Marketing Cloud Next will tag tracked links in its messaging channels with UTM and custom parameters set per business unit, content record or link, with fallback values; planned for November 2026.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  237. Promised date SFMC Next · UTM and custom link parameter tracking

    Promised date: none → Nov 2026

    Added the week of September 21, 2026 as "Automate UTM and Custom Parameter Tagging"; the release note says "This feature is available in November 2026." Evidence: help.salesforce.com ↗

  238. Lifecycle state SFMC Next · UTM and custom link parameter tracking

    Lifecycle state: GA · Sep 2026 → Announced · week of 21 Sep 2026

    Added the week of September 21, 2026 as "Automate UTM and Custom Parameter Tagging"; the release note says "This feature is available in November 2026." Evidence: help.salesforce.com ↗

  239. Text SFMC Next · Approved attachments for email templates
    Summary rewritten

    Before: Marketing teams can attach approved files, such as required disclosures, to Distributed Marketing email templates for sender use.

    After: Marketing teams will be able to attach approved files, such as required disclosures, to Distributed Marketing email templates for senders to use; planned from November 2026.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  240. Promised date SFMC Next · Approved attachments for email templates

    Promised date: none → Nov 2026

    The change log says "Added a release note to announce the ability to attach required files" (week of October 12), then "Feature available in November 2026." Evidence: help.salesforce.com ↗

  241. Lifecycle state SFMC Next · Approved attachments for email templates

    Lifecycle state: GA · week of 12 Oct 2026 → Announced · week of 12 Oct 2026

    The change log says "Added a release note to announce the ability to attach required files" (week of October 12), then "Feature available in November 2026." Evidence: help.salesforce.com ↗

  242. Text SFMC Next · Compliance, coordination and unified calendar for marketing operations
    Summary rewritten

    Before: Marketing Cloud Next Advanced enforces brand and compliance standards, coordinates work with tasks and approvals, and shows the plan on a unified calendar.

    After: Marketing Planning and Operations will add tactic templates, compliance reviews before execution, tasks and approvals with Slack, and a unified program and campaign calendar; planned from late October 2026.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  243. Promised date SFMC Next · Compliance, coordination and unified calendar for marketing operations

    Promised date: none → Oct 2026

    Added to the notes the week of October 5, 2026, but the note says "This functionality is available starting in late October 2026." It is an announcement with a promised date, not GA. Evidence: help.salesforce.com ↗

  244. Lifecycle state SFMC Next · Compliance, coordination and unified calendar for marketing operations

    Lifecycle state: GA · week of 5 Oct 2026 → Announced · week of 5 Oct 2026

    Added to the notes the week of October 5, 2026, but the note says "This functionality is available starting in late October 2026." It is an announcement with a promised date, not GA. Evidence: help.salesforce.com ↗

  245. Text SFMC Next · Marketing Planning and Operations setup
    Summary rewritten

    Before: Marketing Cloud Next Advanced provides guided discovery and setup steps for the new Marketing Planning and Operations module.

    After: Salesforce Go will offer guided discovery and setup of Marketing Planning and Operations, with feature-usage tracking, from one place in Setup; planned from late October 2026.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  246. Promised date SFMC Next · Marketing Planning and Operations setup

    Promised date: none → Oct 2026

    Added to the notes the week of October 5, 2026, but the note says "This functionality is available starting in late October 2026." It is an announcement with a promised date, not GA. Evidence: help.salesforce.com ↗

  247. Lifecycle state SFMC Next · Marketing Planning and Operations setup

    Lifecycle state: GA · week of 5 Oct 2026 → Announced · week of 5 Oct 2026

    Added to the notes the week of October 5, 2026, but the note says "This functionality is available starting in late October 2026." It is an announcement with a promised date, not GA. Evidence: help.salesforce.com ↗

  248. Text SFMC Next · Goal-driven marketing programs
    Summary rewritten

    Before: Marketing Cloud Next Advanced lets marketers build Marketing Programs that align campaigns to goals, which cascade and roll up across the hierarchy.

    After: Marketing Planning and Operations will let teams build marketing programs at each level of a planning hierarchy, with program goals whose results roll up automatically; planned from late October 2026.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  249. Promised date SFMC Next · Goal-driven marketing programs

    Promised date: none → Oct 2026

    Added to the notes the week of October 5, 2026, but the note says "This functionality is available starting in late October 2026." It is an announcement with a promised date, not GA. Evidence: help.salesforce.com ↗

  250. Lifecycle state SFMC Next · Goal-driven marketing programs

    Lifecycle state: GA · week of 5 Oct 2026 → Announced · week of 5 Oct 2026

    Added to the notes the week of October 5, 2026, but the note says "This functionality is available starting in late October 2026." It is an announcement with a promised date, not GA. Evidence: help.salesforce.com ↗

  251. Text SFMC Next · Linking campaigns to programs and goals
    Summary rewritten

    Before: Marketing Cloud Next Advanced lets marketers connect individual campaigns to the programs and goals they support.

    After: Marketing Planning and Operations will let marketers connect campaigns to the programs and goals they support and roll campaign results up into program goals; planned from late October 2026.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  252. Promised date SFMC Next · Linking campaigns to programs and goals

    Promised date: none → Oct 2026

    Added to the notes the week of October 5, 2026, but the note says "This functionality is available starting in late October 2026." It is an announcement with a promised date, not GA. Evidence: help.salesforce.com ↗

  253. Lifecycle state SFMC Next · Linking campaigns to programs and goals

    Lifecycle state: GA · week of 5 Oct 2026 → Announced · week of 5 Oct 2026

    Added to the notes the week of October 5, 2026, but the note says "This functionality is available starting in late October 2026." It is an announcement with a promised date, not GA. Evidence: help.salesforce.com ↗

  254. Text SFMC Next · Agentforce strategy-to-execution planning
    Summary rewritten

    Before: Agentforce turns a marketer's strategy into an executable marketing plan built on programs and campaigns.

    After: The Marketing Planning and Operations agent in Agentforce will turn marketing strategy into connected programs and goals that cascade through planning hierarchies; planned from late October 2026.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  255. Promised date SFMC Next · Agentforce strategy-to-execution planning

    Promised date: none → Oct 2026

    Added to the notes the week of October 5, 2026, but the note says "This functionality is available starting in late October 2026." It is an announcement with a promised date, not GA. Evidence: help.salesforce.com ↗

  256. Lifecycle state SFMC Next · Agentforce strategy-to-execution planning

    Lifecycle state: GA · week of 5 Oct 2026 → Announced · week of 5 Oct 2026

    Added to the notes the week of October 5, 2026, but the note says "This functionality is available starting in late October 2026." It is an announcement with a promised date, not GA. Evidence: help.salesforce.com ↗

  257. Text SFMC Next · Marketing Goals Agent for self-optimizing campaigns
    Summary rewritten

    Before: New Agentforce agent sets goals and continuously self-optimizes marketing campaigns toward them.

    After: The Agentforce Marketing Goals Agent will run self-optimizing agentic campaigns, choosing campaign, channel, content and timing per customer toward a set goal; Salesforce gives late October 2026.

    Summary rewritten to describe the corrected state. Evidence: help.salesforce.com ↗

  258. Promised date SFMC Next · Marketing Goals Agent for self-optimizing campaigns

    Promised date: none → Oct 2026

    Recorded as GA at the Winter '27 release date, but the note's When section says "Available in late October 2026."; no source confirms availability. Evidence: help.salesforce.com ↗

  259. Lifecycle state SFMC Next · Marketing Goals Agent for self-optimizing campaigns

    Lifecycle state: GA · Sep 2026 → Announced · Sep 2026

    Recorded as GA at the Winter '27 release date, but the note's When section says "Available in late October 2026."; no source confirms availability. Evidence: help.salesforce.com ↗

  260. Date 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.

    Date: week of 11 Oct 2026 → week of 12 Oct 2026

    The vendor's changelog first said "Added the week of October 11, 2026", then "Added the week of October 12, 2026"; the latest statement is kept. Evidence: help.salesforce.com ↗

  261. Text 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.
    Summary rewritten

    Before: Salesforce announced upcoming changes to WhatsApp service and utility message pricing affecting Marketing Cloud Engagement customers.

    After: 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.

    The sub-page says Meta charges per message for service and utility messages from October 1, 2026, and Salesforce updates its pricing on November 1, 2026. Evidence: help.salesforce.com ↗

  262. Merged 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.

    A duplicate entry of this signal was merged into it.

    Same "Prepare for WhatsApp Service and Utility Message Pricing Changes" entry recorded as four signals; only the changelog week changed (October 11 to 12). Evidence: help.salesforce.com ↗

  263. Merged 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.

    A duplicate entry of this signal was merged into it.

    Same "Prepare for WhatsApp Service and Utility Message Pricing Changes" entry recorded as four signals; only the changelog week changed (October 11 to 12). Evidence: help.salesforce.com ↗

  264. Merged 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.

    A duplicate entry of this signal was merged into it.

    Same "Prepare for WhatsApp Service and Utility Message Pricing Changes" entry recorded as four signals; only the changelog week changed (October 11 to 12). Evidence: help.salesforce.com ↗

  265. Text SFMC Engagement · WhatsApp messaging by Business-Scoped User ID (Engagement)
    Summary rewritten

    Before: Engagement can message WhatsApp users by username via Business-Scoped User IDs, reaching those who hide phone numbers.

    After: 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.

    Summary rewritten for the single available state. Evidence: help.salesforce.com ↗

  266. Lifecycle state SFMC Engagement · WhatsApp messaging by Business-Scoped User ID (Engagement)

    Lifecycle: Announced · May 2026; GA · Sep 2026 → GA · Jun 2026

    The Summer '26 notes list it as shipped: "When: Starting June 2026, Marketing Cloud Engagement handles BSUID user-initiated messages without disruption." Winter '27 repeats it. Evidence: help.salesforce.com ↗

  267. Text SFMC Engagement · Guidance to prepare for client secret rotation
    Summary rewritten

    Before: Advises admins to prepare to rotate API client secrets for installed packages ahead of upcoming changes.

    After: 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.

    Summary states the dates given by the vendor. Evidence: help.salesforce.com ↗

  268. Promised date SFMC Engagement · Guidance to prepare for client secret rotation

    Promised date: none → 23 Mar 2026

    The Spring '26 note says "Beginning March 23, 2026, all client secrets for API integrations have a 180-day expiration period". Evidence: help.salesforce.com ↗

  269. Date SFMC Engagement · Step-up MFA reauthentication for security tasks

    Date: Sep 2026 → 30 Jul 2026

    The Winter '27 note says "Step-up authentication was enforced beginning on July 30, 2026". Evidence: help.salesforce.com ↗

  270. Date SFMC Engagement · Phishing-resistant MFA via platform authentication

    Date: Sep 2026 → 30 Jul 2026

    The Winter '27 note says "Support for platform-based authentication methods became available on July 30, 2026". Evidence: help.salesforce.com ↗

  271. Date SFMC Engagement · Login allowlist using recommended IP ranges

    Date: Sep 2026 → 30 Jul 2026

    The Winter '27 note says "This change became available on July 30, 2026"; the When note wins over the release date. Evidence: help.salesforce.com ↗

  272. Date SFMC Engagement · Duplicate Marketing Cloud Engagement users into Marketing Cloud Next

    Date: Jan 2026 → 27 Feb 2026

    The Spring '26 note says "This feature is available on a rolling basis beginning February 27, 2026"; a rollout to everyone is general availability. Evidence: help.salesforce.com ↗

  273. Text SFMC Engagement · Skip template pre-approval for WhatsApp Direct Send utility messages
    Summary rewritten

    Before: WhatsApp utility messages sent via Direct Send can skip template pre-approval, with checks against category mismatches.

    After: 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.

    Summary no longer presents a planned feature as available. Evidence: help.salesforce.com ↗

  274. Merged SFMC Engagement · salesforce-marketing-cloud-engagement.direct-send-template-category-mismatch-detection

    Record salesforce-marketing-cloud-engagement.direct-send-template-category-mismatch-detection merged into Skip template pre-approval for WhatsApp Direct Send utility messages.

    The Messaging overview sentence on catching "Direct Send template category mismatches" introduces the Skip Template Pre-Approval entry, whose page is rn_mce_category_mismatches. Evidence: help.salesforce.com ↗

  275. Lifecycle state SFMC Engagement · Skip template pre-approval for WhatsApp Direct Send utility messages

    Lifecycle state: GA · Sep 2026 → Announced · Sep 2026

    The Winter '27 sub-page says "This feature is planned for availability after November 2026"; no promised date is given. Evidence: help.salesforce.com ↗

  276. Text SFMC Engagement · MFA requirement for single sign-on accounts
    Summary rewritten

    Before: Single sign-on accounts must now be updated to use multi-factor authentication.

    After: 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.

    Summary no longer presents a future requirement as in force. Evidence: help.salesforce.com ↗

  277. Lifecycle state SFMC Engagement · MFA requirement for single sign-on accounts

    Lifecycle state: GA · Sep 2026 → Announced · Sep 2026

    The Winter '27 note says "This requirement isn't enforced in the current release. In a future release, all accounts that use single sign-on must meet this requirement." Evidence: help.salesforce.com ↗

  278. Date MoEngage · Merlin AI custom agents

    Date: 3 Jun 2026 → week of 8 Jun 2026

    The cited MarTech Watch row of week 2026-W24 gives no date ("Status in the watch: Launched"); 3 June is not in the archived source, so the state is dated to that week. Evidence: prnewswire.com ↗

  279. Date MoEngage · Open MCP server for custom agents

    Date: 3 Jun 2026 → week of 8 Jun 2026

    The cited MarTech Watch row of week 2026-W24 gives no date ("Status in the watch: Launched"); 3 June is not in the archived source, so the state is dated to that week. Evidence: prnewswire.com ↗

  280. Lifecycle state MoEngage · Workspace classification

    Lifecycle state: GA · Global → GA (regional) · DC-03

    The June 2026 release notes say "This feature is enabled for all customers on the Enterprise plan on DC-03": one data centre only. Evidence: moengage.com ↗

  281. Lifecycle state MoEngage · Flows Assist iterative editing

    Regions: Global → DC-03

    The June 2026 release notes say "This feature is available for clients who already have the Flows Assist MVP enabled on DC-03". Evidence: moengage.com ↗

  282. Text MoEngage · Daily-refresh computed traits
    Summary rewritten

    Before: Computed Traits can now refresh at a daily frequency, enabled on request.

    After: Computed Traits can refresh at a daily frequency for accounts that ask MoEngage to enable it.

    Summary rewritten for the limited availability (on request). Evidence: moengage.com ↗

  283. Lifecycle state MoEngage · Daily-refresh computed traits

    Lifecycle state: GA · Jul 2026 → Preview · Jul 2026

    The July 2026 release notes say "Computed Traits are now available at a daily refresh frequency. This can be enabled on request": access on request is limited availability. Evidence: moengage.com ↗

  284. Date precision Klaviyo became available for procurement on AWS Marketplace via AWS EDP committed spend.

    Date precision: exact day → week

    The MarTech Watch row of week 2026-W21 gives no date ("Status in the watch: Launched"); the signal is dated to the Monday of that week. Evidence: klaviyo.com ↗

  285. Merged Klaviyo · klaviyo.headless

    Record klaviyo.headless merged into Klaviyo MCP server: 260+ new tools.

    The MarTech Watch row describes Klaviyo Headless as "260+ MCP tools and capabilities callable from Claude, ChatGPT or any AI system": the MCP server, GA since 11 August. Evidence: klaviyo.com ↗

  286. Merged Klaviyo · klaviyo.customer-agent-product-recommendations

    Record klaviyo.customer-agent-product-recommendations merged into Customer Agent product recommendations for WooCommerce and Magento.

    Same What's New entry recorded twice: identical text ("Use Customer Agent on WooCommerce and Magento 2 to recommend in-stock products"), retitled and redated by the vendor to 2026-10-23. Evidence: klaviyo.com ↗

  287. Text Klaviyo · Scheduled tasks in Composer
    Summary rewritten

    Before: Composer can run marketing tasks on a schedule rather than only on demand.

    After: Composer can turn a task that went well into a scheduled task that reruns automatically on fresh data.

    Summary rewritten for the general availability stated by the vendor. Evidence: klaviyo.com ↗

  288. Lifecycle state Klaviyo · Scheduled tasks in Composer

    Lifecycle state: Announced · 9 Sep 2026 → GA · 4 Sep 2026

    Klaviyo's What's New lists "Scheduled Tasks in Composer" with "Date: 2026-09-04" and "Release type: generalAvailability"; the later MarTech Watch announcement of 9 September adds no state. Evidence: klaviyo.com ↗

  289. Merged Adobe AJO · adobe-journey-optimizer.journey-stop-action-activity

    Record adobe-journey-optimizer.journey-stop-action-activity merged into Inbound activity deactivation journey activity.

    Same capability recorded twice: "Stop action" is the released Inbound Activity Deactivation journey activity (identical text); both sources are cited on the kept record. Evidence: experienceleague.adobe.com ↗

  290. Text Adobe AJO · Inbound activity deactivation journey activity
    Summary rewritten

    Before: A new journey activity will let a canvas remove a profile from up to five inbound activities or experiences.

    After: A Stop action activity in the journey canvas removes a profile from up to five inbound activities or experiences, decoupling inbound disqualification from journey exit.

    Summary rewritten for the GA state. Evidence: experienceleague.adobe.com ↗

  291. Lifecycle state Adobe AJO · Inbound activity deactivation journey activity

    GA state: not recorded → 12 Oct 2026

    On 13 October the Coming soon entry left the block renamed "Stop action", word for word the same text, with "Availability date: October 12, 2026". Evidence: experienceleague.adobe.com ↗

  292. Merged Adobe AJO · adobe-journey-optimizer.email-designer-dynamic-media-template-component

    Record adobe-journey-optimizer.email-designer-dynamic-media-template-component merged into PSD import into Email Designer Dynamic Media.

    Same capability recorded twice: the September Coming soon entry on PSD import was renamed "Dynamic Media Template component" with the same text and Limited Availability; both sources are cited on the kept record. Evidence: experienceleague.adobe.com ↗

  293. Text Braze · Locale translation for Content Blocks
    Summary rewritten

    Before: Content Blocks can target users in different workspace locales with translated content, mirroring existing banner localization.

    After: Content Blocks target users in different workspace locales with translated content; generally available with multi-language translations.

    Summary rewritten for the GA state. Evidence: braze.com ↗

  294. Lifecycle state Braze · Locale translation for Content Blocks

    GA state: not recorded → 2 Apr 2026

    The 2 April 2026 "Multi-language translations" release, marked General availability, covers translations "within a single push, email, Banner, in-app message, or Content Block". Evidence: braze.com ↗

  295. Text Braze · Locale translation for banners
    Summary rewritten

    Before: A single banner can target users across multiple workspace locales with translated content.

    After: A single banner targets users across multiple workspace locales with translated content; generally available with multi-language translations.

    Summary rewritten for the GA state. Evidence: braze.com ↗

  296. Lifecycle state Braze · Locale translation for banners

    GA state: not recorded → 2 Apr 2026

    The 2 April 2026 "Multi-language translations" release, marked General availability, covers translations "within a single push, email, Banner, in-app message, or Content Block". Evidence: braze.com ↗

  297. Date Bloomreach · Native SDK log callbacks in the React Native SDK

    GA date: Confirmed by 19 Oct 2026 → 8 Oct 2026

    Release 1.320 dates the React Native SDK 4.2.0 entry, which lists this change, "October 08, 2026"; the fetch date of 19 October is not a vendor date. Evidence: documentation.bloomreach.com ↗

  298. Date Bloomreach · UIScene lifecycle support in the React Native SDK (iOS)

    GA date: Confirmed by 19 Oct 2026 → 8 Oct 2026

    Release 1.320 dates the React Native SDK 4.2.0 entry, which lists this change, "October 08, 2026"; the fetch date of 19 October is not a vendor date. Evidence: documentation.bloomreach.com ↗

  299. Source Bloomreach · Dynamic file-name matching for Data hub imports

    GA sources: documentation.bloomreach.com/engagement/changelog/1320 → documentation.bloomreach.com/engagement/changelog/1321

    Release 1.321 replaces the withdrawn 1.320 section "Import files with changing names into Data hub" as the source. Evidence: documentation.bloomreach.com ↗

  300. Date Bloomreach · Dynamic file-name matching for Data hub imports

    GA date: 14 Oct 2026 → 28 Oct 2026

    The section appeared in release 1.320 only on 14 October and was removed the next day; release 1.321 ("Release date: 28.10. - 2.11.2026") publishes it. Evidence: documentation.bloomreach.com ↗

  301. Date precision Adobe AJO · Restart button for orchestrated campaigns

    GA date precision: 27 Jan 2026 → Jan 2026

    In the January '26 orchestrated campaigns list, "Restart button" has no date of its own: "Availability date: January 27, 2026" belongs to "User-generated metadata support". Dated to the month. Evidence: experienceleague.adobe.com ↗

  302. Date precision Adobe AJO · Rate control for orchestrated campaigns

    GA date precision: 27 Jan 2026 → Jan 2026

    In the January '26 orchestrated campaigns list, "Rate control support" has no date of its own: "Availability date: January 27, 2026" belongs to "User-generated metadata support". Dated to the month. Evidence: experienceleague.adobe.com ↗

  303. Date precision Adobe AJO · Predefined retargeting filters for orchestrated campaigns

    GA date precision: 27 Jan 2026 → Jan 2026

    In the January '26 orchestrated campaigns list, "Predefined retargeting filters" has no date of its own: "Availability date: January 27, 2026" belongs to "User-generated metadata support". Dated to the month. Evidence: experienceleague.adobe.com ↗

  304. Date precision Adobe AJO · Send confirmation step for orchestrated campaigns

    GA date precision: 27 Jan 2026 → Jan 2026

    In the January '26 orchestrated campaigns list, "Message confirmation before send" has no date of its own: "Availability date: January 27, 2026" belongs to "User-generated metadata support". Dated to the month. Evidence: experienceleague.adobe.com ↗

  305. Date precision Adobe AJO · Select and copy distribution values in orchestrated campaigns

    GA date precision: 27 Jan 2026 → Jan 2026

    In the January '26 orchestrated campaigns list, "Select attributes and copy distribution values" has no date of its own: "Availability date: January 27, 2026" belongs to "User-generated metadata support". Dated to the month. Evidence: experienceleague.adobe.com ↗

  306. Date precision Adobe AJO · Predefined parameterized filters for orchestrated campaigns

    GA date precision: 27 Jan 2026 → Jan 2026

    In the January '26 orchestrated campaigns list, "Predefined filters with parameters" has no date of its own: "Availability date: January 27, 2026" belongs to "User-generated metadata support". Dated to the month. Evidence: experienceleague.adobe.com ↗

  307. Date precision Adobe AJO · Data usage label inheritance for orchestrated campaign audiences

    GA date precision: 27 Jan 2026 → Jan 2026

    In the January '26 orchestrated campaigns list, "Data usage label inheritance for audiences" has no date of its own: "Availability date: January 27, 2026" belongs to "User-generated metadata support". Dated to the month. Evidence: experienceleague.adobe.com ↗

  308. Date precision Adobe AJO · Revert live orchestrated campaigns to draft

    GA date precision: 27 Jan 2026 → Jan 2026

    In the January '26 orchestrated campaigns list, "Revert live campaigns to draft status" has no date of its own: "Availability date: January 27, 2026" belongs to "User-generated metadata support". Dated to the month. Evidence: experienceleague.adobe.com ↗

  309. Date Adobe AJO · Reduced step events for wait and event activities

    Announced date: 1 Oct 2026 → 1 Sep 2026

    On 27 September the bullet "Reduced step events for wait and event activities" is in the Coming soon block of September '26 > Journeys; it moved to October on 7 October. Evidence: experienceleague.adobe.com ↗

  310. Text Adobe AJO · Estimated click metrics for email reporting
    Summary rewritten

    Before: Journeys, Campaigns, and Channel Live reports now include Estimated CTR and Estimated CTOR metrics.

    After: Journeys, Campaigns and Channel reports include Estimated CTR and Estimated CTOR metrics for email, computed from estimated clicks.

    The June entry names Journeys, Campaigns and Channel reports; Channel Live reports are named only by the July entry. Evidence: experienceleague.adobe.com ↗

  311. Date Adobe AJO · Estimated click metrics for email reporting

    GA date: 29 Jul 2026 → 25 Jun 2026

    June '26 > Reporting of the 2026 archive: estimated metrics "now available across Journeys, Campaigns, and Channel reports", availability date June 25, 2026. Evidence: experienceleague.adobe.com ↗

  312. Date Adobe AJO · Dataset TTL guardrail enforcement on existing sandboxes

    Deprecation announced date: 1 Sep 2026 → 1 Jul 2026

    The TTL guardrail bullet is already in the July '26 > Administration section of the 2026 archive (no date of its own); September repeats it under "The following reminder applies". Evidence: experienceleague.adobe.com ↗

  313. Text Adobe AJO · Journey execution timeline analysis via Coworker
    Summary rewritten

    Before: Coworker analyzes Read Audience journey execution timing: duration, P95/P99 and export-to-first-profile latency, and flags the slowest versions and runs.

    After: Coworker returns the end-to-end timeline of a Read Audience journey batch: how long it took, when audience export, execution and delivery started and ended, and profile-level P95 and P99 times.

    Summary rewritten to match the vendor's current entry of 26 October 2026. Evidence: experienceleague.adobe.com ↗

  314. Date Adobe AJO · Journey execution timeline analysis via Coworker

    GA date: 1 Oct 2026 → 26 Oct 2026

    The entry dated October 1 appeared only on 22 October; from 27 October it is rewritten as "Journey Execution Timeline skill" with "Availability date: October 26, 2026". Evidence: experienceleague.adobe.com ↗

  315. Date Adobe AJO · Batch audience deprecation in Audience Qualification and Exit Criteria

    Deprecation announced date: 1 Jul 2026 → 1 Jun 2026

    The [Deprecation] bullet "Batch audiences no longer supported in Audience Qualification node and Exit Criteria" is already in the June '26 > Journeys section of the 2026 archive. Evidence: experienceleague.adobe.com ↗

  316. Text Braze · Messaging Observability dashboard
    Summary rewritten

    Before: A dashboard giving a high-level breakdown of message sending outcomes to spot trends and diagnose why campaign or Canvas messages weren't sent as expected.

    After: In early access, a dashboard breaks down message sending outcomes so teams can spot trends and diagnose why campaign or Canvas messages were not sent as expected; access is requested through the customer success manager.

    Summary rewritten for the early-access state. Evidence: braze.com ↗

  317. Lifecycle state Braze · Messaging Observability dashboard

    GA state: 23 Jul 2026 → not recorded

    The 23 July 2026 entry is labelled "General availability" but says "Contact your customer success manager for access to the feature": access on request, so it stays in early access. Evidence: braze.com ↗

  318. Classification Braze · JP-01 regional data center

    Significance: major → minor

    A new data center extends where the platform is available; availability extensions are minor features. Evidence: braze.com ↗

  319. Lifecycle state Braze · JP-01 regional data center

    Lifecycle state: GA · 5 Mar 2026 → GA (regional) · 5 Mar 2026

    "Braze has launched a new data center: JP-01": a single new data center is availability in one region, recorded as regional GA. Evidence: braze.com ↗

  320. Text Braze · BrazeAI Operator agent
    Summary rewritten

    Before: BrazeAI Operator, Braze's in-platform AI agent, became generally available together with BrazeAI Agent Console.

    After: BrazeAI Operator, Braze's in-platform AI agent, was announced together with BrazeAI Agent Console; the MarTech Watch reports both as generally available.

    Summary rewritten for an announcement taken from the MarTech Watch. Evidence: braze.com ↗

  321. Lifecycle state Braze · BrazeAI Operator agent

    Lifecycle state: GA · 23 Apr 2026 → Announced · 23 Apr 2026

    The only cited source is a MarTech Watch row ("(catch-up, 23 Apr) BrazeAI Operator, Agent Console ... to GA"); Watch rows record announcements only. Evidence: braze.com ↗

  322. Text Bloomreach · Loomi Marketing Agent
    Summary rewritten

    Before: AI agent that builds marketing campaigns end-to-end from a natural-language prompt, selecting audience, content and channels.

    After: Loomi Marketing Agent builds marketing campaigns end-to-end from a natural-language prompt, choosing audience, content and channels; the MarTech Watch reports it as generally available.

    Summary rewritten for an announcement taken from the MarTech Watch. Evidence: bloomreach.com ↗

  323. Lifecycle state Bloomreach · Loomi Marketing Agent

    Lifecycle state: GA · 2 Jun 2026 → Announced · week of 8 Jun 2026

    The only cited source is a MarTech Watch row ("Status in the watch: GA", week 2026-W24, no date); Watch rows record announcements only, dated to the Watch week. Evidence: bloomreach.com ↗

  324. Text Adobe AJO · Guided onboarding migration workspace
    Summary rewritten

    Before: A dedicated onboarding workspace to migrate existing email content and journeys from other platforms moves toward GA.

    After: A dedicated workspace helps organizations moving from another marketing platform bring existing email content and journeys into Journey Optimizer instead of rebuilding them; in limited availability.

    Summary rewritten for the limited-availability state. Evidence: experienceleague.adobe.com ↗

  325. Lifecycle state Adobe AJO · Guided onboarding migration workspace

    Lifecycle state: Announced · Sep 2026 → Preview · 30 Jul 2026

    The 2026 archive (July '26 > Content management, "Guided Adoption Capabilities") says it is "only available for a set of organizations (Limited Availability)", availability date July 30, 2026. Evidence: experienceleague.adobe.com ↗

  326. Date Adobe AJO · Decisioning support in custom outbound channels

    GA date: 5 Oct 2026 → 2 Oct 2026

    2026-10-05 was the fetch date. "Use Journey Optimizer Decisioning in the custom channel payload" is listed in the Custom outbound channel GA block, which from 6 October reads "Availability date: October 2, 2026". Evidence: experienceleague.adobe.com ↗

  327. Date Adobe AJO · Custom channels in API-triggered campaigns

    GA date: 5 Oct 2026 → 2 Oct 2026

    2026-10-05 was the fetch date. "Select custom channels in the channel list for API-triggered campaigns" is listed in the Custom outbound channel GA block, which from 6 October reads "Availability date: October 2, 2026". Evidence: experienceleague.adobe.com ↗

  328. Date Adobe AJO · Business rules for custom outbound channels

    GA date: 5 Oct 2026 → 2 Oct 2026

    2026-10-05 was the fetch date. "Apply business rules to custom channels" is listed in the Custom outbound channel GA block, which from 6 October reads "Availability date: October 2, 2026". Evidence: experienceleague.adobe.com ↗

  329. Date Adobe AJO · Custom outbound channel

    GA date: 5 Oct 2026 → 2 Oct 2026

    2026-10-05 was the day the entry was fetched; from 6 October the "Custom outbound channel (General Availability)" block reads "Availability date: October 2, 2026". Evidence: experienceleague.adobe.com ↗

  330. Lifecycle state Adobe AJO · Custom outbound channel

    Lifecycle state: Announced · Sep 2026 → Preview · 31 Jul 2026

    The 2026 archive (July '26 > Channels) says "Custom outbound channels are currently available as Limited Availability", availability date July 31, 2026; the September Coming soon row cannot follow it as an announcement. Evidence: experienceleague.adobe.com ↗

  331. Merged SF Account Engagement · salesforce-account-engagement.data-360-companion-org-connection

    Record salesforce-account-engagement.data-360-companion-org-connection merged into Data 360 business unit connection.

    Same capability recorded twice: the Spring '26 section page repeats the entry already recorded from the Account Engagement release notes page. Evidence: help.salesforce.com ↗

  332. Removed SFMC Engagement · Real-time offer management

    Record removed: Real-time offer management.

    Real-Time Offer Management is a separate Salesforce product with its own Summer '26 release notes, not part of Marketing Cloud Engagement. Evidence: help.salesforce.com ↗

  333. Lifecycle state SFMC Next · Dynamic From and Reply-To addresses

    Lifecycle state: Announced · 15 Jun 2026 → GA · May 2026

    The Summer '26 release notes (Other Changes in Marketing Cloud Next) describe it as shipped in that release. Evidence: help.salesforce.com ↗

  334. Classification SFMC Next · Dynamic From and Reply-To addresses

    Platform: Marketing Cloud Engagement → Marketing Cloud Next

    The cited Summer '26 news story does not name this feature. Salesforce's Summer '26 release notes describe it under Marketing Cloud Next. Evidence: help.salesforce.com ↗

  335. Lifecycle state SFMC Next · Automatic archiving of sent emails to the EmailMessage object

    Lifecycle state: Announced · 15 Jun 2026 → GA · May 2026

    The Summer '26 release notes (Other Changes in Marketing Cloud Next) describe it as shipped in that release. Evidence: help.salesforce.com ↗

  336. Classification SFMC Next · Automatic archiving of sent emails to the EmailMessage object

    Platform: Marketing Cloud Engagement → Marketing Cloud Next

    The cited Summer '26 news story does not name this feature. Salesforce's Summer '26 release notes describe it under Marketing Cloud Next. Evidence: help.salesforce.com ↗

  337. Text Tealium · Tealium Prism mobile SDK platform
    Summary rewritten

    Before: Tealium Prism will be a next-generation mobile SDK platform for Android and iOS giving developers native control over event processing, configuration, consent and data handling without a WebView.

    After: Tealium Prism, a next-generation mobile SDK platform for Android and iOS, gives developers native control over event processing, remote configuration, consent and integrations without a WebView; documented as early access.

    Summary no longer describes the platform as future. Evidence: docs.tealium.com ↗

  338. Lifecycle state Tealium · Tealium Prism mobile SDK platform

    Lifecycle state: Announced · 16 Oct 2026 → Preview · 16 Oct 2026

    The release notes of 16 October 2026 announce Tealium Prism and its documentation (installation, quick start) is published in Tealium's Early Access section, so it is usable with limited access rather than only announced. Evidence: docs.tealium.com ↗

  339. Text Bloomreach · External segments from outside data sources
    Summary rewritten

    Before: Imports customer segments defined outside the project, such as in a data warehouse, and lets you use them as audiences in campaigns and scenarios without rebuilding segment logic.

    After: Imports customer segments defined outside the project, such as in a data warehouse, and lets you use them as audiences in campaigns and scenarios without rebuilding segment logic. Released between 14 and 19 October 2026; the recorded date is the start of that window.

    Release 1.320 gives "Release date: 14.10. - 19.10.2026"; the summary now states the rollout window. Evidence: documentation.bloomreach.com ↗

  340. Date precision Marketo AI was renamed Coworker for Marketo Engage, with the same agent skills made available to all users.

    Date precision: 14 Aug 2026 → Aug 2026

    The August 2026 release notes give 14 August as the start of the release cycle, with phased rollout over the following weeks; the Coworker announcement carries no date of its own, so it is dated to the month. Evidence: experienceleague.adobe.com ↗

  341. Date precision Marketo · Coworker for Marketo Engage agent skills

    Date precision: 14 Aug 2026 → Aug 2026

    The August 2026 release notes give 14 August as the start of the release cycle, with phased rollout over the following weeks; the Coworker announcement carries no date of its own, so it is dated to the month. Evidence: experienceleague.adobe.com ↗

  342. Date MoEngage · Open MCP server for custom agents

    Date: week of 8 Jun 2026 → 3 Jun 2026

    Dated to the MarTech Watch week; MoEngage's release is dated 3 June 2026. Evidence: prnewswire.com ↗

  343. Date MoEngage · Merlin AI custom agents

    Date: week of 8 Jun 2026 → 3 Jun 2026

    Dated to the MarTech Watch week; MoEngage's release is dated 3 June 2026. Evidence: prnewswire.com ↗

  344. Text Braze · BrazeAI Operator agent
    Summary rewritten

    Before: Press release referenced BrazeAI Operator reaching general availability, recorded here as announced only.

    After: BrazeAI Operator, Braze's in-platform AI agent, became generally available together with BrazeAI Agent Console.

    Summary rewritten to match the state now taken from the vendor's release. Evidence: braze.com ↗

  345. Lifecycle state Tealium · Context API

    Lifecycle state: Announced · 9 Jun 2026 → GA · 9 Jun 2026

    Recorded as an announcement from the MarTech Watch. The vendor's own page states general availability: Tealium's release of 9 June 2026 says "Tealium Context API solution is now available globally". Evidence: tealium.com ↗

  346. Lifecycle state Braze · BrazeAI Operator agent

    Lifecycle state: Announced · 23 Apr 2026 → GA · 23 Apr 2026

    Recorded as an announcement from the MarTech Watch. The vendor's own page states general availability: the release of 23 April 2026 is headed "BrazeAI Operator and BrazeAI Agent Console, now generally available". Evidence: braze.com ↗

  347. Lifecycle state Bloomreach · Loomi Marketing Agent

    Lifecycle state: Announced · week of 8 Jun 2026 → GA · 2 Jun 2026

    Recorded as an announcement from the MarTech Watch. The vendor's own page states general availability: Bloomreach "today announced the general availability of its Loomi marketing agent" (2 June 2026). Evidence: bloomreach.com ↗

  348. Lifecycle state Adobe AEP · CX Enterprise Coworker

    Lifecycle state: Announced · 10 Jun 2026 → GA · 10 Jun 2026

    Recorded as an announcement from the MarTech Watch. The vendor's own page states general availability: Adobe "today announced the general availability of Adobe CX Enterprise Coworker" (10 June 2026). Evidence: news.adobe.com ↗

  349. Date Tealium · AI-generated notes for audiences

    GA date: 27 Feb 2026 → 30 Jan 2026

    The GA date came from the "Product highlights" recap of 27 February; the dated release note "Administration (January 30, 2026)" says the AI Note Generation function was "updated to support audience note generation". Evidence: docs.tealium.com ↗

  350. Date Tealium · Function transformations for cloud data sources

    GA date: 30 Apr 2026 → 15 Apr 2026

    The GA date came from the "Product highlights" recap of 30 April; the dated release note "Server-side > Functions (April 15, 2026)" says "Data transformations can now be applied to events coming from cloud data sources". Evidence: docs.tealium.com ↗

  351. Lifecycle state Braze · Content Optimizer step updates (September 2026)

    GA state: not recorded → 15 Oct 2026

    Recorded in beta while the Content Optimizer step was in beta. Braze made the step generally available on 15 October 2026, and its documentation now describes preheader, sender name and image components and the per-step component limits as part of the step, with no beta label. The beta stays in the history. Evidence: braze.com ↗

  352. Lifecycle state Braze · Content Optimizer step updates (August 2026)

    GA state: not recorded → 15 Oct 2026

    Recorded in beta while the Content Optimizer step was in beta. Braze made the step generally available on 15 October 2026, and its documentation now describes the Learning, Optimizing and Action Recommended step statuses and the pre-launch checks (the Currents event types of the same update are not described on that page) as part of the step, with no beta label. The beta stays in the history. Evidence: braze.com ↗

  353. Lifecycle state Braze · Edit a launched Content Optimizer step

    GA state: not recorded → 15 Oct 2026

    Recorded in beta while the Content Optimizer step was in beta. Braze made the step generally available on 15 October 2026, and its documentation now describes adding, deactivating and reactivating variants on a launched step as part of the step, with no beta label. The beta stays in the history. Evidence: braze.com ↗

  354. Lifecycle state Klaviyo · SQL querying in the Klaviyo Data Platform

    Lifecycle state: Announced · 9 Sep 2026 → Preview · 9 Sep 2026

    Recorded as an announcement from the MarTech Watch, which only records announcements. Klaviyo's own post of 9 September 2026 says "SQL is available in Composer today, in Preview", so the state is preview from that date. Evidence: klaviyo.com ↗

  355. Date Tealium · Insights Dashboard threshold alerts

    GA date: 30 Jun 2026 → 24 Jun 2026

    The GA date came from the "Product highlights" recap of 30 June; the dated release note "Server-side > Insights (June 24, 2026)" says "Threshold alerts are now available in Tealium Insights". Evidence: docs.tealium.com ↗

  356. Date Tealium · AI SQL writer for cloud data sources

    GA date: 31 Aug 2026 → 19 Aug 2026

    The GA date came from the July/August "Product highlights" digest of 31 August; the dated release note "Server-side > Data sources (August 19, 2026)" says "Added the SQL writer". Evidence: docs.tealium.com ↗

  357. Classification Treasure AI · Open Catalog Access for BigQuery

    Classification: Warehouse-native / zero-copy → Destinations & connectors

    Warehouse-native / zero-copy covers a platform that reads or computes on data that stays in the customer's warehouse. Open Catalog Access works the other way: tables managed in Complete CDP, which "remains the system of record", are published as an Iceberg catalog that Snowflake, Databricks or BigQuery query. Sharing the platform's own data with an external warehouse is classified as Destinations & connectors. Reverses the confirmation of 8 October. Evidence: docs.treasure.ai ↗

  358. Classification Treasure AI · Open Catalog Access for Snowflake and Databricks

    Classification: Warehouse-native / zero-copy → Destinations & connectors

    Warehouse-native / zero-copy covers a platform that reads or computes on data that stays in the customer's warehouse. Open Catalog Access works the other way: tables managed in Complete CDP, which "remains the system of record", are published as an Iceberg catalog that Snowflake, Databricks or BigQuery query. Sharing the platform's own data with an external warehouse is classified as Destinations & connectors. Reverses the confirmation of 8 October. Evidence: docs.treasure.ai ↗

  359. Lifecycle state Braze · Content Optimizer for SMS, MMS and RCS

    GA state: not recorded → 15 Oct 2026

    The Braze release of 15 October 2026 makes Content Optimizer generally available as a step that tests variants "for email, push notifications, SMS, MMS, and RCS", so the SMS, MMS and RCS extension recorded in beta on 28 May is GA from the same date. The beta stays in the history. Evidence: braze.com ↗

  360. Lifecycle state Adobe AJO · LINE channel for orchestrated campaigns

    Lifecycle state: Announced · Sep 2026 → Preview · 12 Aug 2026

    The 2026 release notes archive records "LINE channel support (Limited Availability)" with availability date 12 August 2026; the September "coming soon" entry announced the GA that followed on 2 October, so the first state is preview on 12 August, not an announcement. Evidence: experienceleague.adobe.com ↗

  361. Date precision Adobe AJO · Journey-level holdout groups

    Preview date precision: month → exact day

    Reverses corr-2026-10-09-001: the September '26 release notes give "Availability date: September 1, 2026" for this entry, both in the text captured on 27 September and on the current page. Evidence: experienceleague.adobe.com ↗

  362. Text Tealium · Stitching merge rules
    Summary rewritten

    Before: Early-access per-attribute rules that decide which value wins when two visitor profiles are stitched together.

    After: Per-attribute rules that decide which value wins when two visitor profiles are stitched together.

    Summary still described the January early-access phase after GA. Evidence: docs.tealium.com ↗

  363. Date Tealium · Stitching merge rules

    GA date: 31 Aug 2026 → 12 Aug 2026

    The GA date came from the July/August "Product highlights" digest of 31 August; the dated release note "Stitching merge rules now available" is from 12 August 2026. Evidence: docs.tealium.com ↗

  364. Lifecycle state Tealium · Tealium Configuration MCP

    Lifecycle state: GA → Preview

    The release note of 26 August 2026 says only "Added", but Tealium's documentation states that the Configuration MCP "is only available to select customers" and is enabled through support, so the state is preview, not GA. Evidence: docs.tealium.com ↗

  365. Lifecycle state Tealium · Audience dashboard

    Lifecycle state: GA → Preview

    Tealium lists the audience dashboard under Early Access ("sign up required" in the July/August highlights) and its documentation says it "is in Early Access and is only available to select customers", so the state is preview, not GA. Evidence: docs.tealium.com ↗

  366. Lifecycle state Braze · SCIM provisioning for Okta and Microsoft Entra ID groups

    Lifecycle state: GA → Preview

    Braze now labels this entry of the 17 September 2026 release "Early access" (it read "General availability" when first recorded on 27 September), so the state is preview, not GA. Evidence: braze.com ↗

  367. Date precision Adobe AJO · Journey-level holdout groups

    Preview date precision: exact day → month

    Accuracy audit: the release notes give no availability date for this entry, so it is dated to the release month. Evidence: experienceleague.adobe.com ↗

  368. Classification Klaviyo · Customer Hub revenue attribution in the data warehouse

    Classification: Attribution (also Warehouse-native / zero-copy) → Attribution

    Warehouse-native / zero-copy applies only when data stays in the customer's warehouse; writing data into a warehouse is data movement. Evidence: klaviyo.com ↗ · Reconstructed from the record's revision history.

  369. Classification Hightouch · Snowflake Iceberg destination

    Classification: Destinations & connectors (also Warehouse-native / zero-copy) → Destinations & connectors

    Warehouse-native / zero-copy applies only when data stays in the customer's warehouse; writing data into a warehouse is data movement. Evidence: hightouch.com ↗ · Reconstructed from the record's revision history.

  370. Removed HubSpot · GPT Image 2.0 for AI image generation

    Record removed: GPT Image 2.0 for AI image generation.

    Out of the HubSpot Marketing Hub scope: source availability 'Available for Content Hub Starter or above' (owner decision 2026-10-07: Data Hub / Content Hub-only items are excluded). Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  371. Removed HubSpot · Data Studio column summaries, gap filling and rollups

    Record removed: Data Studio column summaries, gap filling and rollups.

    Out of the HubSpot Marketing Hub scope: source availability 'Available for Data Hub Professional+' (owner decision 2026-10-07: Data Hub / Content Hub-only items are excluded). Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  372. Removed HubSpot · Bulk accept/reject formatting issues

    Record removed: Bulk accept/reject formatting issues.

    Out of the HubSpot Marketing Hub scope: source availability 'Available for Data Hub Starter, Professional, and Enterprise' (owner decision 2026-10-07: Data Hub / Content Hub-only items are excluded). Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  373. Removed HubSpot · Breeze-generated custom code workflow actions

    Record removed: Breeze-generated custom code workflow actions.

    Out of the HubSpot Marketing Hub scope: source availability 'Available for Data Hub Professional or Enterprise' (owner decision 2026-10-07: Data Hub / Content Hub-only items are excluded). Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  374. Date precision MoEngage · Merlin AI custom agents

    Announced date precision: exact day → week

    Site review of 2026-10-07: date and precision re-read at the cited source. Evidence: prnewswire.com ↗ · Reconstructed from the record's revision history.

  375. Date precision MoEngage · Open MCP server for custom agents

    Announced date precision: exact day → week

    Site review of 2026-10-07: date and precision re-read at the cited source. Evidence: prnewswire.com ↗ · Reconstructed from the record's revision history.

  376. Date Klaviyo · Multiple email addresses per profile

    Announced date: 11 May 2026 → 24 Mar 2026

    Site review of 2026-10-07: date and precision re-read at the cited source. Evidence: klaviyo.com ↗ · Reconstructed from the record's revision history.

  377. Removed HubSpot · Ticket links open Help Desk

    Record removed: Ticket links open Help Desk.

    Out of the HubSpot Marketing Hub scope: source availability 'Help Desk: Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  378. Lifecycle state HubSpot · Redesigned Smart CRM index

    Beta state: not recorded → Confirmed by 11 Aug 2026

    Site review of 2026-10-07: state confirmed by the cited source. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  379. Removed HubSpot · Live captioning and Live Call Assist with Breeze

    Record removed: Live captioning and Live Call Assist with Breeze.

    Out of the HubSpot Marketing Hub scope: source availability 'Available for Service Hub Professional+ (Help Desk ticket thread, calls)'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  380. Removed HubSpot · AI-assisted knowledge base category translation

    Record removed: AI-assisted knowledge base category translation.

    Out of the HubSpot Marketing Hub scope: source availability 'KB Translation for Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  381. Removed HubSpot · Help Desk ticket reopening rules

    Record removed: Help Desk ticket reopening rules.

    Out of the HubSpot Marketing Hub scope: source availability 'Help Desk: Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  382. Removed HubSpot · Help Desk thread filters

    Record removed: Help Desk thread filters.

    Out of the HubSpot Marketing Hub scope: source availability 'Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  383. Removed HubSpot · Help Desk thread attachment tiles

    Record removed: Help Desk thread attachment tiles.

    Out of the HubSpot Marketing Hub scope: source availability 'Live for Service Hub Professional+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  384. Removed HubSpot · Help Desk system message redesign

    Record removed: Help Desk system message redesign.

    Out of the HubSpot Marketing Hub scope: source availability 'Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  385. Removed HubSpot · Help Desk spam search

    Record removed: Help Desk spam search.

    Out of the HubSpot Marketing Hub scope: source availability 'Live for Service Hub Professional+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  386. Removed HubSpot · Help Desk routing via workflow

    Record removed: Help Desk routing via workflow.

    Out of the HubSpot Marketing Hub scope: source availability 'Live for Service Hub Professional+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  387. Removed HubSpot · Route Help Desk tickets by rep skill

    Record removed: Route Help Desk tickets by rep skill.

    Out of the HubSpot Marketing Hub scope: source availability 'Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  388. Removed HubSpot · Out-of-office labels in Help Desk mentions

    Record removed: Out-of-office labels in Help Desk mentions.

    Out of the HubSpot Marketing Hub scope: source availability 'Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  389. Removed HubSpot · Help Desk omnichannel waitlist

    Record removed: Help Desk omnichannel waitlist.

    Out of the HubSpot Marketing Hub scope: source availability 'Help Desk: Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  390. Removed HubSpot · Customer Experience and Quality Assurance scores

    Record removed: Customer Experience and Quality Assurance scores.

    Out of the HubSpot Marketing Hub scope: source availability 'Help Desk: Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  391. Removed HubSpot · Custom ticket automation messages

    Record removed: Custom ticket automation messages.

    Out of the HubSpot Marketing Hub scope: source availability 'Live for Service Hub Professional+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  392. Removed HubSpot · Bulk unmark spam in Help Desk

    Record removed: Bulk unmark spam in Help Desk.

    Out of the HubSpot Marketing Hub scope: source availability 'Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  393. Removed HubSpot · Help Desk board redesign and composer

    Record removed: Help Desk board redesign and composer.

    Out of the HubSpot Marketing Hub scope: source availability 'Help Desk: Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  394. Removed HubSpot · Customer Agent team scorecard

    Record removed: Customer Agent team scorecard.

    Out of the HubSpot Marketing Hub scope: source availability 'Team Scorecard for Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  395. Removed HubSpot · Customer Agent folder in Help Desk

    Record removed: Customer Agent folder in Help Desk.

    Out of the HubSpot Marketing Hub scope: source availability 'Help Desk folder: Service Hub Pro+'. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  396. Date precision Bloomreach · Loomi Marketing Agent

    Announced date precision: exact day → week

    Site review of 2026-10-07: date and precision re-read at the cited source. Evidence: bloomreach.com ↗ · Reconstructed from the record's revision history.

  397. Promised date Marketo · Marketo Engage New UI

    Announced promised date: 30 Sep 2026 → 1 Sep 2026

    Site review of 2026-10-07: date and precision re-read at the cited source. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  398. Date precision Adobe AJO · Decisioning support in custom outbound channels

    GA date precision: month → exact day

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  399. Date Adobe AJO · Decisioning support in custom outbound channels

    GA date: 1 Sep 2026 → 5 Oct 2026

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  400. Lifecycle state Adobe AJO · Decisioning support in custom outbound channels

    Announced state: not recorded → Sep 2026

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  401. Date precision Adobe AJO · Custom channels in API-triggered campaigns

    GA date precision: month → exact day

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  402. Date Adobe AJO · Custom channels in API-triggered campaigns

    GA date: 1 Sep 2026 → 5 Oct 2026

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  403. Lifecycle state Adobe AJO · Custom channels in API-triggered campaigns

    Announced state: not recorded → Sep 2026

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  404. Date precision Adobe AJO · Custom outbound channel

    GA date precision: month → exact day

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  405. Date Adobe AJO · Custom outbound channel

    GA date: 1 Sep 2026 → 5 Oct 2026

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  406. Lifecycle state Adobe AJO · Custom outbound channel

    Announced state: not recorded → Sep 2026

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  407. Date precision Adobe AJO · Business rules for custom outbound channels

    GA date precision: month → exact day

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  408. Date Adobe AJO · Business rules for custom outbound channels

    GA date: 1 Sep 2026 → 5 Oct 2026

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  409. Lifecycle state Adobe AJO · Business rules for custom outbound channels

    Announced state: not recorded → Sep 2026

    Pipeline fix: a state transition seen on a later day had been dropped; the announced state is restored and the GA date set to the day it was published. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  410. Text Hightouch offered Publicis $800M–$1.2B for LiveRamp's identity assets, RampID and LiveRamp Connect.
    Summary rewritten

    Before: Hightouch reportedly offered Publicis $800M–$1.2B for LiveRamp's identity assets, including RampID and LiveRamp Connect.

    After: Hightouch offered Publicis $800M–$1.2B in cash and stock for LiveRamp's identity and data onboarding businesses (RampID, LiveRamp Connect) before Publicis' LiveRamp deal closed; its co-CEO confirmed the offer.

    Signal re-sourced: the cited release did not support it; the announcement and the co-CEO's confirmation do. Evidence: axios.com ↗ · Reconstructed from the record's revision history.

  411. Merged HubSpot · hubspot-marketing-hub.tiktok-organic-publishing

    Record hubspot-marketing-hub.tiktok-organic-publishing merged into TikTok organic publishing and engagement.

    Same capability recorded twice; both sources are cited on the kept record. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  412. Text HubSpot · TikTok organic publishing and engagement
    Summary rewritten

    Before: TikTok connects natively to HubSpot's CRM, letting teams run TikTok ad campaigns, publish organic content and manage engagement from inside HubSpot.

    After: TikTok connects natively to HubSpot's CRM: teams run TikTok ad campaigns, create, schedule and publish organic posts, reply to comments and track performance alongside other social channels.

    Owner review of the first MAP B2B extraction. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  413. Classification HubSpot · TikTok organic publishing and engagement

    Classification: Integrations & marketplace (also Paid media audiences) → Organic social publishing (also Paid media audiences)

    Owner review of the first MAP B2B extraction and taxonomy v1.6: classified by what the feature does. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  414. Classification HubSpot · Reddit posting and analytics

    Classification: Integrations & marketplace (also Reporting & dashboards) → Organic social publishing (also Reporting & dashboards)

    Owner review of the first MAP B2B extraction and taxonomy v1.6: classified by what the feature does. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  415. Text HubSpot · Conversation volume estimates for Customer Agent
    Summary rewritten

    Before: When configuring Customer Agent on email or chat, HubSpot estimates how many conversations the agent will handle based on history or similar channels.

    After: When configuring Customer Agent on email or chat, HubSpot estimates the conversation volume the agent is likely to handle, based on history or similar channels.

    Owner review of the first MAP B2B extraction. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  416. Classification HubSpot · In-workflow content actions from AEO recommendations

    Classification: Content generation (also Reporting & dashboards) → AI answer engine visibility (also Content generation)

    Owner review of the first MAP B2B extraction and taxonomy v1.6: classified by what the feature does. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  417. Classification HubSpot · AI answer engine visibility tracking (AEO)

    Classification: Reporting & dashboards (also Predictive models) → AI answer engine visibility (also Predictive models)

    Owner review of the first MAP B2B extraction and taxonomy v1.6: classified by what the feature does. Evidence: community.hubspot.com ↗ · Reconstructed from the record's revision history.

  418. Classification Marketo · Manage Brands for Email Designer

    Classification: Content generation → Assets & creative library (also Content generation)

    Owner review of the first MAP B2B extraction and taxonomy v1.6: classified by what the feature does. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  419. Classification Marketo · Brand Score Checker for Email Designer

    Classification: Predictive models → Editors & templates (also Predictive models)

    Owner review of the first MAP B2B extraction and taxonomy v1.6: classified by what the feature does. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  420. Classification Marketo · API name validation for custom activity attributes

    Classification: Data quality & contracts → APIs & extensibility

    Owner review of the first MAP B2B extraction and taxonomy v1.6: classified by what the feature does. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  421. Date precision Braze · Cloud Data Ingestion: Azure Blob Storage source

    Announced date precision: week → exact day

    Rule: never two states of a feature on the same day; a promised availability date is kept as the promise, not as the state date. Evidence: braze.com ↗ · Reconstructed from the record's revision history.

  422. Date Braze · Cloud Data Ingestion: Azure Blob Storage source

    Announced date: 31 Aug 2026 → 20 Aug 2026

    Rule: never two states of a feature on the same day; a promised availability date is kept as the promise, not as the state date. Evidence: braze.com ↗ · Reconstructed from the record's revision history.

  423. Text Adobe AJO · Orchestrated campaigns API
    Summary rewritten

    Before: New API specifications will let you programmatically create, manage, and trigger orchestrated campaigns.

    After: APIs for orchestrated campaigns let external systems retrieve campaigns and monitor their executions programmatically.

    Summary rewritten to describe the current state instead of the earlier promise. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  424. Text Adobe AJO · Orchestrated campaign data monitoring dashboard
    Summary rewritten

    Before: A new Campaign Orchestration tab will track ingestion status and freshness of relational store data feeding batch audiences.

    After: A Campaign Orchestration tab in the Experience Platform Monitoring dashboard tracks ingestion status and freshness of the relational data feeding orchestrated campaign audiences.

    Summary rewritten to describe the current state instead of the earlier promise. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  425. Text Adobe AJO · Supplemental ID in journey simulation
    Summary rewritten

    Before: Journey Simulation will support Supplemental ID for testing read-audience and event-triggered journey scenarios.

    After: Journey Simulation supports Supplemental ID, so read-audience and event-triggered journey scenarios can be tested with it.

    Summary rewritten to describe the current state instead of the earlier promise. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  426. Date precision Adobe AJO · Content preview in journey canvas

    Announced date precision: exact day → month

    Rule: never two states of a feature on the same day; a promised availability date is kept as the promise, not as the state date. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  427. Date Adobe AJO · Content preview in journey canvas

    Announced date: 28 Sep 2026 → 1 Sep 2026

    Rule: never two states of a feature on the same day; a promised availability date is kept as the promise, not as the state date. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  428. Text Adobe AJO · Content preview in journey canvas
    Summary rewritten

    Before: The journey canvas will show a content thumbnail per channel activity, with a fullscreen modal to inspect treatments and variants.

    After: The journey canvas shows a content thumbnail for each channel activity, with a fullscreen modal to inspect and switch between treatments and variants.

    Summary rewritten to describe the current state instead of the earlier promise. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  429. Date precision Adobe AJO · Dataset TTL guardrail enforcement on existing sandboxes

    Deprecation announced date precision: exact day → month

    Rule: never two states of a feature on the same day; a promised availability date is kept as the promise, not as the state date. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  430. Date Adobe AJO · Dataset TTL guardrail enforcement on existing sandboxes

    Deprecation announced date: 1 Oct 2026 → 1 Sep 2026

    Rule: never two states of a feature on the same day; a promised availability date is kept as the promise, not as the state date. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  431. Date Adobe AJO · Primary identity requirement for Audience Composition audiences

    Deprecation announced date: 1 Oct 2026 → 1 Sep 2026

    Rule: never two states of a feature on the same day; a promised availability date is kept as the promise, not as the state date. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

Report an issue

Tell us what is wrong in this record. Reports are checked against public sources, with the same rules as every entry. How corrections work

Sent through Web3Forms. Nothing you send is published. How reports are handled.