Considerations for Storing Sales Engagement Data in Data 360

Store Sales Engagement data in Data 360 to retain a longer-term history of email activity and engagement data for reporting and cross-cloud use cases. For example, create reports on historical email opens or personalize marketing and sales campaigns based on engagement with sales emails.

Required Editions

Available in: Lightning Experience
Available with Sales Engagement, which is included with Sales in Performance, Einstein 1, and Unlimited Editions, and available for an extra cost in Professional and Enterprise Editions. Sales Engagement is also available for an extra cost in Service and Lightning Platform.

Before you set up the Data 360 connection, review these considerations.

  • Storing and processing Sales Engagement data in Data 360 consumes Data 360 credits. Review Data 360 billable usage types to understand how ingestion, storage, and processing affect credit consumption.
  • The Data 360 integration doesn't provide real-time synchronization. It can take some time for the engagement data to be ingested and become available.
  • For workflows that require immediate action, such as cadence automations triggered by an email open or link click, Sales Engagement continues to support the applicable near-real-time product experiences.
  • Sales Engagement stores recent engagement data to support activity timelines, cadence steps, automations, and engagement metrics. Data 360 stores the full history of raw engagement data from the time that you turn on the integration.
  • Sales Engagement doesn't automatically sync every related Salesforce object to Data 360. Raw engagement data includes information about related Salesforce records, such as leads, contacts, cadences, and email messages.
  • Changes to Sales Engagement data are reflected in related Salesforce records. For example:
    • When a lead converts to a contact, historical engagement data is associated with the contact.
    • When leads or contacts merge, we move engagement data associated with the duplicate record to the primary record.
    • When you delete customer data in response to privacy requests, separately delete the associated engagement data from Data 360.