Each Recipient Interaction record includes a consistent set of data to support reporting and automations.
Activity metrics are counts and timestamps of engagement events (opens, clicks, bounces, failures, spam, opt outs), which you can roll up in Reports and use to trigger follow up actions:
|
Label |
Description |
|---|---|
| Bounced Count | How many times the element send bounced. |
| Bounced Date | The date/time of the last bounce. |
| Clicked Count | How many times the template in the element was ‘clicked’ |
| Clicked Date | Date/time of the last time a template in an element was ‘clicked’. |
| Failed Count | How many times delivery of the element to the recipient failed. |
| Failed Date | The date of the last failed delivery attempt. |
| Opened Count | How many times the template in the sent element was opened by the recipient. |
| Opened Date | The date/time of the last recipient. |
| Opt Out Count | If greater than 0, the recipient opted out. If more than 1, the recipient oped out, opted in, and opted out again. |
| Opt Out Date | The date of the last opt-out. |
| Send Date | The date the element was sent to the recipient. |
| Spam Reported Count | How many times the element was marked as spam. |
| Spam Reported Date | The date/time of the last time the element was marked as spam. |
| Status |
The formula field updates the overall activity of the recipient on the element. The status will be updated to the most recent activity, except for ‘open’. The status of ‘click’ will be maintained if the recipient continues to open the element, but not click. This is a delivered formula field. If you wish to have the activity summarized according to your business needs, a new formula field can be created, and this delivered status can be hidden from the record. |
Context fields tell you which campaign/track/element the opens, clicks, bounces, etc. belong to, so you can group and filter reporting by those properties:
|
Label |
Description |
|---|---|
| Campaign Name | The sending campaign. |
| Element | The ID of the element that was sent to the recipient. |
| Element Name | The name of the element that was sent to the recipient. |
| Element Type | The type of element that was sent to the recipient. In May 2026, these will all be ‘Email’. |
| Track Name | The Track to which the sending element belongs. |
| Track Type | Drip track or fixed date track. |
Recipient fields let you tie opens, clicks, bounces, etc., back to the right person or relationship in your CRM so you can segment, report, and trigger follow‑ups accurately:
|
Label |
Description |
|---|---|
| Contact | The Contact recipient, if sending to Contacts. |
| Lead | The Lead recipient, if sending to Leads. |
| Recipient Email | The email address the element was sent to. |
If you wish to record recipient interactions for parents, you can do so. There are a few steps your Administrator will need to complete to enable the upsync of parent data.
Parent interactions will be recorded and associated with the Relationship object.
This example shows how a single Recipient Interaction unfolds for a single recipient.
After the first record is created, all subsequent qualifying activities for the same recipient and email element update that same record.
A separate child record of the EBM record is created for every unique link the recipient clicks, capturing link level details for later reporting on link performance.
Note on interaction counts: Email providers such as Microsoft (Office) 365, Gmail, and Apple use their own security technology to review emails for harmful content and links. This automated security activity can sometimes show up in reporting as an open or a click, and in some cases may even click every link in the message (including the unsubscribe link), which is a strong sign it is a spam filter, not a real person. This behavior has mostly resulted in inflated numbers of logged opens and clicks during testing of this feature. As these automated security interactions become easier to identify, the product will be updated to filter them out, so Reports better reflect actual recipient behavior.
When building campaigns, you can turn Recipient Interaction on or off for each track in the track’s Email Settings. This setting is time stamped against the Track Active and Campaign Active dates, so you can see which sends had interaction tracking enabled.
For any track where Recipient Interaction is enabled, every send will create or update interaction records for all supported recipients. Each email open, click, bounce, failure, spam report, or opt out is written to the Recipient Interaction record together with the date and time of that activity.
Recipient Interaction data appears in your Salesforce org within a few hours of the activity, and your CRM is refreshed multiple times throughout the day.
Note: if you enable recipient interactions on an existing track after installing the May package, a few days of historical activity may sync to the org. For example, if you install the package on 5/15 and then enable RI on a track that was created and activated in January, interaction records may be created for sends dating back to 5/11.
Use the Recipient Interactions report types to build Reports on engagement activity. For example: