Capture and tracking customer consent preferences to support your data privacy and compliance strategy. With Field Audit Trail, you can retain and audit changes to customer consent preferences across five consent management objects: Authorization Form Consent, Communication Subscription Consent, Contact Point Consent, Contact Point Type Consent, and Party Consent.

Where: This change applies to Lightning Experience, Salesforce Classic, and the mobile app in Enterprise, Performance, and Unlimited editions.

Who: This change is available to customers who purchased Privacy Center and either Field Audit Trail or Salesforce Shield add-on subscriptions.

How: To retain fields that have field history tracking enabled, add consent management data to your retention policy with Metadata API. Then use REST API, SOAP API, and Tooling API to work with your archived data.

Track and Audit Consent Management Data (salesforce.com)

Retain field history for a range of consent management objects.

• Track and Audit Consent Management Data
  Capture and tracking customer consent preferences to support your data privacy and compliance strategy. With Field Audit Trail, you can retain and audit changes to customer consent preferences across five consent management objects: Authorization Form Consent, Communication Subscription Consent, Contact Point Consent, Contact Point Type Consent, and Party Consent.

Field Audit Trail (salesforce.com)

Use the API Total Usage event type to monitor details of requests made from all versions of the Platform SOAP API, Platform REST API, and Bulk API. Previously, this event type monitored usage through API version 49.0.

Where: This change applies to Enterprise, Performance, Unlimited, and Developer editions. This event type is available in the API but not in the Event Monitoring Analytics app.

Who: The API Total Usage event type is free with 24-hour data retention for all customers. Customers who purchased Salesforce Shield or Salesforce Event Monitoring add-on subscriptions enjoy a longer data retention period.

Track API Usage for All API Versions (salesforce.com)

Say goodbye to recreating Event Monitoring Analytics apps with each new release. You can now upgrade and reconfigure Event Monitoring Analytics apps configured to add only new event log file data to existing datasets. Save time and reduce the likelihood of reaching row count limits.

Where: This change applies to Lightning Experience in Enterprise, Performance, Unlimited, and Developer editions.

Who: This change is available to customers who purchased Salesforce Shield or Salesforce Event Monitoring add-on subscriptions.

Streamline Dataset Updates for the Event Monitoring Analytics App (Beta) (salesforce.com)

You can now use the Event Monitoring Analytics app to visualize event data about knowledge article usage. Build or enhance dashboards that show key information such as who’s viewing knowledge articles, which article version they open, and when they view it. Use the new USER_ID_DERIVED field on the Knowledge Article View event type to better understand specific users’ interactions with your knowledge content.

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions where Event Monitoring is enabled.

Who: This change is available to customers who purchased Salesforce Shield or Salesforce Event Monitoring add-on subscriptions.

View Knowledge Article Event Data in Event Monitoring Analytics Apps (salesforce.com)

With Real-Time Event Monitoring, you can now monitor for insecure flows that can expose user credentials to security risks. Use LoginEvent and LoginEventStream to track OAuth user-agent and username-password flows.

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions where Event Monitoring is enabled.

Who: This change is available to customers who purchased Salesforce Shield or Salesforce Event Monitoring add-on subscriptions.

Track Insecure Login Flows (salesforce.com)

To help you update references to your previous My Domain URLs, the Hostname Redirects event type includes more information on where requests to those URLs come from. Use the new Origin and Referrer fields to identify references to your previous URLs. If your URLs changed with enhanced domains, use this information to update those references before some redirections stop in Winter ’25.

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions. The Hostname Redirects event is available in the API but not in the Event Monitoring Analytics app. This event is free for all customers with a 24-hour data retention period.

Track the Source of My Domain Redirections (salesforce.com)

Hone you app’s efficiency and performance by tracking your Lightning page performance. Use new EPT deviation fields on the Lightning URI Event and Lightning URI Event Stream real-time events to see if your page load times have changed and why. And when page load times take more than 60 seconds, the EffectivePageTime field value no longer is set to 0 on real-time events or the Lightning Page View event type.

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions where Event Monitoring is enabled.

Who: This change is available to customers who purchased Salesforce Shield or Salesforce Event Monitoring add-on subscriptions.

How: Use four new fields to see what caused changes in your Lightning page performance.

• EffectivePageTimeDeviationErrorType: Indicates the origin of an error.
• EffectivePageTimeDeviationReason: The reason for deviation in page loading time.
• HasEffectivePageTimeDeviation: If a deviation in page load time occurred.
• UserAgent: The type of client used to make the request. For example, the browser, application, or API.

Dig into Details About Page Load Times (salesforce.com)

With this update, event log files are generated and delivered only to orgs that opt in to receive event log files. Previously, all orgs received event log files automatically. This update automatically disables event log file generation for Developer and Trial editions and for orgs that don’t have the Event Monitoring add-on subscription by default. If you have Salesforce Shield or Salesforce Event Monitoring add-on subscriptions, you’re opted in to receiving event log files by default. This update was first available it Spring ’23 and is enforced in Summer ’23.

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer Editions.

When: This update was first available in Spring ’23 and is enforced in Summer ’23. To get the major release upgrade date for your instance, go to Trust Status, search for your instance, and click the maintenance tab.

How: To review this update, from Setup, in the Quick Find box, enter Event Monitoring, and then select Event Monitoring Settings. Turn on or off Generate event log files.

Opt in for Event Log File Generation (Release Update) (salesforce.com)

Files are a treasure trove of sensitive and important information. Use FileEvent and FileEventStore, now generally available, to track file previews, uploads, and downloads from the UI and API. And because file events support transaction security policies, you can take steps to proactively control how users interact with specific files.

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions where Event Monitoring is enabled.

Who: This change is available to customers who purchased Salesforce Shield or Salesforce Event Monitoring add-on subscriptions.

Track File Usage in Near Real-Time with FileEvent (Generally Available) (salesforce.com)