SFDC Special Fields - Email Bounced Date and Reason

Brian_Law_MKTO
Marketo Employee
Marketo Employee

During an integration with SFDC there are some fields from SFDC which will automatically appear in Marketo which aren't part of the SFDC object visibility rules. (Check out this article for a list of fields). Two of the fields (Email Bounced Date and Email Bounced Reason) which will sync into Marketo are used in SFDC to track whether the email address is valid. These two fields are not connected or integrated with the Marketo Email Invalid and Email Invalid Cause fields. You can use smart campaigns and tokens to set these two fields. Remember to set up data management campaigns to reset the fields if the email address changes.

SFDC Field

Description

Available in Marketo as a Filter in a Smart List

Marketo Token

Email Bounced Date

Date record bounced in SFDC

Yes

{{lead.Email Bounced Date}}

Email Bounced Reason

Reason record bounced in SFDC

Yes

{{lead.Email Bounced Reason}}

Marketo Field

Description

Available in Marketo as a Filter in a Smart List

Marketo Token

Email Invalid

Marketo recognizes the email address is invalid

Yes

N/A

Email Invalid Cause

Cause of the email being invalid

Yes

{{lead.Email Invalid Cause}}

Here are some additional resources for learning about the Marketo integration with SFDC.

4056
1
1 Comment
grantboothcs2
Level 1

Do not do what this article is suggesting. If you want to bring information about Marketo bounces into SFDC, you should create new fields in Salesforce to store that information.

These are standard fields in Salesforce, intended to show why a Salesforce email bounced. Weirdly enough, you can set the values for an existing lead or contact in Salesforce via an integration like Marketo's, but if you try to insert a new lead with these values set, it will throw an error.
Screenshot 2024-03-19 at 4.32.59 PM.png
I also recommend relabeling the fields as "SFDC Email Bounced Reason" and "SFDC Email Bounced Date" to avoid confusion. And hopefully Marketo relabels these too as part of its standard integration.