Sales teams rely on Salesforce CRM to tell them whether a Contact or Lead is reachable. If someone’s email has permanently bounced in SFMC, the CRM record should reflect that — so sales reps are not wasting calls following up on “did you get my email” with someone whose inbox has been dead for months.

The integration is straightforward in concept but has a nuance that catches most teams out when they first build it. Simply querying the _Bounce Data View for hard bounces and syncing everything you find is not the correct approach. The result will be a lot of noise, false flags, and contacts marked as unreachable in CRM who are actually perfectly fine.

How SFMC Actually Handles Bounces

Before building the sync, understanding the subscriber status model matters. SFMC does not treat all hard bounces equally, and the path a subscriber takes depends on whether the bounce came from a trusted ISP.

The correct signal to sync to CRM is not a bounce event in _Bounce. It is a subscriber reaching Held status in _Subscribers. That is the moment SFMC itself has decided the address is permanently undeliverable and stopped all future sends. That is what your CRM should know about.

The Full Architecture

The SQL Query

This is the exact query for the daily Automation Studio step. It joins _Bounce with _Subscribers to confirm Held status, applies a 24-hour incremental filter, and brings in the email address and bounce category for context in the staging DE:

/* Pulls confirmed hard bounces — only where SFMC has also moved
   the subscriber to Held status. This is the CRM-worthy signal.
   Run daily. Action: Overwrite on Hard_Bounce_Staging_DE. */

SELECT DISTINCT
    b.SubscriberKey,
    b.EmailAddress,
    b.BounceCategory,
    b.SMTPCode,
    LEFT(b.SMTPBounceReason, 500) AS BounceReason,
    b.EventDate                 AS BounceDate

FROM   _Bounce         b
JOIN   _Subscribers    s  ON  b.SubscriberKey = s.SubscriberKey

WHERE
    b.BounceCategory = 'Hard bounce'
    AND s.Status     = 'Held'
    AND b.EventDate >= DATEADD(day, -1, GETDATE())
    AND b.EventDate <  GETDATE()

Setting Up the Salesforce CRM Fields

Before configuring the Journey, create two custom fields on both the Contact and Lead objects in Salesforce CRM. These are simple to set up via Setup in the CRM:

• Hard_Bounce__c — Checkbox field. Ticked when the Journey Object Activity runs. Sales reps can filter their views on this field immediately.
• Hard_Bounce_Date__c — Date/DateTime field. Set to the BounceDate value from the staging DE. Gives visibility into when the address became undeliverable.

In the Journey Builder Object Activity, configure it as Find and Update. Match on SubscriberKey to ContactID and LeadID respectively. Map Hard_Bounce__c to true and Hard_Bounce_Date__c to the BounceDate field from the journey DE. Set the Journey to Re-entry Always so that if the same contact bounces again at a later date, the BounceDate in CRM is updated to the most recent event.

CRM Fields to Add to Your Page Layouts

Once the fields exist and data starts populating, add them to the Contact and Lead page layouts in Salesforce so sales reps can see email reachability at a glance. A simple section called “Email Deliverability” with the two fields is enough. You can also add a CRM report or list view filtered on Hard_Bounce__c = TRUE so the sales team has a single place to review and action these records periodically.

Frequently Asked Questions