Engagement Activity

This dataset describes how customers engage with campaigns that were sent to them.

Overview

The Engagement Activity view provides detailed data on customer engagements with campaigns they were targeted with, updated daily alongside other datasets. It tracks interactions at the channel level, represented by PLAN_DETAIL_CHANNEL_ID, allowing for granular insight into how customers engage with each communication channel within a campaign.

Each row represents an engagement of a customer with a certain campaign, capturing key performance metrics such as message opens, clicks, and unsubscribes, along with timestamps for each interaction.

This data is essential for analyzing campaign and content effectiveness and customer behavior across different channels.

📣
Latest version available: BI.VW_ENGAGEMENT_ACTIVITY_V1_6. Use the tabs below to view the version you're integrating against. All timestamps are in UTC.

-- FOR V1.6
SELECT *
FROM [SHARED_DB].BI.VW_ENGAGEMENT_ACTIVITY_V1_6

👍
What changed in V1_6: new column ENGAGEMENT_ID — a single, consistent identifier for an engagement, shared across the engagement views. CAMPAIGN_TYPE is also exposed. The primary key changed (see below). All other V1_5 columns are unchanged.

📌
Availability: The V1.6 columns and the primary key change for this view are being rolled out automatically to Campaign Execution 2.0 clients over the coming months. Data begins at your rollout date — earlier history isn't backfilled. Need access sooner? Contact your Customer Success Manager and we'll enable it on request.

⚠️
Breaking — primary key changed in V1_6: was CUSTOMER_ID, SEND_ID → now CUSTOMER_ID + ENGAGEMENT_ID for scheduled campaigns and CUSTOMER_ID + SEND_ID for triggered campaigns. CAMPAIGN_TYPE (SCHEDULED vs REAL_TIME) indicates which applies.

🔑 Primary Key

Primary Key: CUSTOMER_ID + ENGAGEMENT_ID (scheduled · CAMPAIGN_TYPE = 'SCHEDULED') · CUSTOMER_ID + SEND_ID (triggered · CAMPAIGN_TYPE = 'REAL_TIME')
Watermark Column: UPDATED_AT (reliable as of V1_5)

Data retention

Initially loaded with the last 365 days of engagement data; from V1_5 onward (delta mode) data accumulates indefinitely after the initial load.

Table Description

Field Name	Description	Data Type	Format
`CUSTOMER_ID`	Unique identifier for the customer	String
`CLIENT_CUSTOMER_ID`	Unique identifier for the client's customer	String
`CAMPAIGN_TYPE`	Campaign type — `SCHEDULED` or `REAL_TIME` (triggered). Determines which primary key applies.	String
`SEND_ID`	Unique identifier for the send action	String
`ENGAGEMENT_ID`	Unique identifier of an engagement record, consistent across the engagement views. Added in V1_6 — part of the primary key for scheduled campaigns.	Integer
`ACTION_SERIAL`	Sequence number for the action	Integer
`PLAN_DETAIL_ID`	Campaign action ID	String
`PLAN_DETAIL_CHANNEL_ID`	Unique identifier for the channel used in the plan detail	String
`CHANNEL_ID`	Unique identifier for the communication channel	String
`CHANNEL_NAME`	Name of the communication channel	String
`IS_DELIVERED`	Timestamp of campaign delivery, in UTC	DateTime	yyyy-mm-dd HH:MM:SS
`IS_OPENED`	Timestamp of the first time a customer opened a message, in UTC	DateTime	yyyy-mm-dd HH:MM:SS
`IS_CLICKED`	Timestamp of the first time a customer clicked a message, in UTC	DateTime	yyyy-mm-dd HH:MM:SS
`IS_UNSUBSCRIBED`	Timestamp of the first time a customer unsubscribed, in UTC	DateTime	yyyy-mm-dd HH:MM:SS
`IS_DROPPED`	Timestamp of the first time a customer's message was dropped, in UTC	DateTime	yyyy-mm-dd HH:MM:SS
`IS_SPAM_REPORT`	Timestamp of the first time a customer reported as spam, in UTC	DateTime	yyyy-mm-dd HH:MM:SS
`IS_BOUNCED`	Timestamp of the first time a customer's message bounced, in UTC	DateTime	yyyy-mm-dd HH:MM:SS
`UPDATED_AT`	Timestamp when the record was last updated	DateTime	yyyy-mm-dd HH:MM:SS

Channels

This view captures engagement across campaign channels — Email, SMS, and Push — identified by CHANNEL_ID / CHANNEL_NAME and measured per channel sub-action (PLAN_DETAIL_CHANNEL_ID). Metric availability depends on what each channel reports: Email provides the full delivery / open / click set, while some channels (e.g. Push) report a subset.

Use cases

Analyze customers' engagement by their demographic details.
Analyze templates and channels that created the most engagement.
Cross with VW_TRANSACTIONS to analyze the relationship between engagement and purchases.

Engagement Activity

Engagement Activity

Overview

Latest version available: `BI.VW_ENGAGEMENT_ACTIVITY_V1_6`. Use the tabs below to view the version you're integrating against. All timestamps are in UTC.

What changed in V1_6: new column `ENGAGEMENT_ID` — a single, consistent identifier for an engagement, shared across the engagement views. `CAMPAIGN_TYPE` is also exposed. The primary key changed (see below). All other V1_5 columns are unchanged.

Breaking — primary key changed in V1_6: was `CUSTOMER_ID, SEND_ID` → now `CUSTOMER_ID` + `ENGAGEMENT_ID` for scheduled campaigns and `CUSTOMER_ID` + `SEND_ID` for triggered campaigns. `CAMPAIGN_TYPE` (`SCHEDULED` vs `REAL_TIME`) indicates which applies.

🔑 Primary Key

Data retention

Table Description

Channels

Use cases

Engagement Activity

Overview

Latest version available: BI.VW_ENGAGEMENT_ACTIVITY_V1_6. Use the tabs below to view the version you're integrating against. All timestamps are in UTC.

What changed in V1_6: new column ENGAGEMENT_ID — a single, consistent identifier for an engagement, shared across the engagement views. CAMPAIGN_TYPE is also exposed. The primary key changed (see below). All other V1_5 columns are unchanged.

Breaking — primary key changed in V1_6: was CUSTOMER_ID, SEND_ID → now CUSTOMER_ID + ENGAGEMENT_ID for scheduled campaigns and CUSTOMER_ID + SEND_ID for triggered campaigns. CAMPAIGN_TYPE (SCHEDULED vs REAL_TIME) indicates which applies.

🔑 Primary Key

Data retention

Table Description

Channels

Use cases

Latest version available: `BI.VW_ENGAGEMENT_ACTIVITY_V1_6`. Use the tabs below to view the version you're integrating against. All timestamps are in UTC.

What changed in V1_6: new column `ENGAGEMENT_ID` — a single, consistent identifier for an engagement, shared across the engagement views. `CAMPAIGN_TYPE` is also exposed. The primary key changed (see below). All other V1_5 columns are unchanged.

Breaking — primary key changed in V1_6: was `CUSTOMER_ID, SEND_ID` → now `CUSTOMER_ID` + `ENGAGEMENT_ID` for scheduled campaigns and `CUSTOMER_ID` + `SEND_ID` for triggered campaigns. `CAMPAIGN_TYPE` (`SCHEDULED` vs `REAL_TIME`) indicates which applies.