The Activity tab on a contact record shows a chronological log of every action and event associated with that contact. The log is ordered from most recent to oldest, giving you a complete picture of the contact’s engagement journey.
Filtering by activity type
Click the Filters button to filter the activity log by specific activity categories.
The following activity types are available as filters:
| Activity type | Description |
|---|
| Emails | Email sends, opens, clicks, bounces, unsubscribes, and other email lifecycle events. |
| Form submissions | Form submissions tracked in Conversion. |
| Page visits | Website page visits tracked by the Conversion pixel. |
| Workflows | Workflow entries, exits, and related automation events. |
| Custom events | Custom events tracked for the contact via the Events API. |
| Field changes | Updates to fields on the contact record, including the old and new values. |
| Campaigns | Campaign entries, exits, campaign status changes, and campaign member field changes for the contact. |
| Audiences | Audience entries and exits for the contact. |
Activity type reference
The activity log captures a detailed history of engagement events. Each event belongs to a top-level type, and most types have specific subtypes that classify the event further.
Page visits
Page visit events display when the contact has visited your website. They are categorized into traffic channels based on the tracked data.
Page visit events classify the traffic source that brought a contact to a page on your site. When multiple page visits share a session*, they are grouped into a session group in the timeline.
*A session is a continuous period of activity by a single user on a website, beginning when they first arrive and ending when they close the browser tab.
- The form name (or form ID).
- The page URL where the form was submitted.
- The individual field values of the submission.
Emails
These track lifecycle events for emails sent to a contact via Conversion’s email infrastructure. Each event is tied to a specific sent email.
| Subtype | Description | UI display |
|---|
| Send | The email was successfully sent to the contact. | ”Sent [Email Name]“ |
| Open | The contact opened the email. Tracks occurrence count (e.g., “3 times”). | ”Opened [Email Name]“ |
| Click | The contact clicked a link within the email. Includes the specific link URL that was clicked. | ”Clicked a link in [Email Name]“ |
| Bounce | The email hard-bounced (permanent delivery failure, e.g., invalid address). | ”[Email Name] bounced” |
| Soft bounce | The email soft-bounced (temporary delivery failure, e.g., full mailbox). | — |
| Complaint | The contact marked the email as spam. | ”Marked [Email Name] as spam” |
| Delivery | The email was successfully delivered to the recipient’s mail server. | — |
| Reject | The email was rejected before sending (e.g., content policy violation). | — |
| Rendering failure | The email template failed to render. | — |
| Delivery delay | The email delivery was delayed. | — |
| Unsubscribe | The contact unsubscribed from a specific email topic or list. | ”Unsubscribed” |
| Unsubscribe all | The contact unsubscribed from all email communications. | — |
| Topic unsubscribe | The contact unsubscribed from a specific email topic. | — |
| Subscription | The contact subscribed (or re-subscribed) to email communications. | — |
| Unknown | An unknown or unclassified email event occurred. | — |
Subtypes marked with ”—” in the UI display column are tracked in the system but are not explicitly rendered on the activity timeline.
Workflows
These track a contact’s journey through an automation workflow.
| Subtype | Description | UI display |
|---|
| Enter automation | The contact entered (was enrolled into) a workflow. | ”Entered [Workflow Name]“ |
| Exit automation | The contact exited (completed or was removed from) a workflow. | ”Exited [Workflow Name]“ |
| Enter node | The contact entered a specific node or step within a workflow. | — |
| Exit node | The contact exited a specific node or step within a workflow. | — |
| Error | An error occurred while processing the contact within a workflow. | — |
The enter node, exit node, and error subtypes are tracked in the system but are currently displayed the same as “exited” on the activity timeline.
Custom events
Custom events are tracked via the Events API and appear in the activity log with the event name and a timestamp. There are no subtypes — each entry represents a single occurrence of the named event.
If the event was sent with a data payload, the metadata is displayed in JSON format directly on the activity entry. For example, an event named feature_activated with data {"feature_name": "dashboard", "plan": "pro"} would show both the event name and the full data object in the log.
Field changes
Field change events are recorded whenever a field on the contact record is updated. Each entry captures the field that changed along with both the previous and new values, giving you a complete audit trail of how a contact’s data has evolved over time.
Each field change event includes:
- The field name that was updated.
- The old value prior to the change.
- The new value after the change.
Field changes apply to both default and custom fields on the contact record.
Campaigns
Campaign events track a contact’s full lifecycle within a campaign: when they enter, when they leave, when their status changes, and whenever a field on their campaign member record is updated.
| Subtype | Description | UI display |
|---|
| Enter campaign | The contact was added to a campaign. | ”Was added to campaign [Campaign Name]“ |
| Exit campaign | The contact was removed from or completed a campaign. | ”Was removed from campaign [Campaign Name]“ |
| Status change | The contact’s status within a campaign changed (e.g., from step two to step three). | ”Moved to [New Status] from [Old Status] in campaign [Campaign Name]“ |
| Member field change | A field on the contact’s campaign member record was updated. Shows the new value, or “cleared” when the field is emptied. | ”[Field Name] set to “[New Value]” in campaign [Campaign Name]” or “[Field Name] cleared in campaign [Campaign Name]” |
Audiences
Audience events track when a contact enters or leaves an audience. Audience membership is dynamic, so these events are generated automatically as a contact’s data changes and they begin (or stop) matching an audience definition.
| Subtype | Description | UI display |
|---|
| Enter audience | The contact began matching an audience and was added to it. | ”Entered [Audience Name]“ |
| Exit audience | The contact stopped matching an audience and was removed from it. | ”Exited [Audience Name]” |
