Skip to main content
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 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.

​
Form submissions

Represents a contact submitting a form on your site. There are no further subtypes. The engagement data includes:
  • 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.
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.
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. Each campaign event includes the campaign name and the timestamp of the change. Status changes additionally include the previous status and the new status, and member field changes include the field name and the new value (or indicate that the field was cleared) — giving you full visibility into how a contact’s campaign membership data evolves over time.

​
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. Each audience event includes the audience name and the timestamp of the entry or exit.

​
Contact created

A synthetic event injected by the UI at the bottom of every contact’s activity timeline to show when the contact record was first created. This is not an API engagement type. It is generated by the frontend to provide historical context.