Targeted and Excluded Customers

Overview

This view provides an organized representation of customers who were either targeted or excluded from scheduled campaigns. It includes details about the campaigns, customers, and reasons for exclusion if one occurred.

Each row represents a customer (CUSTOMER_ID) eligibility for a campaign (PLAN_DETAIL_ID) on an execution day (EXECUTION_DATE).

Data is updated daily on an incremental method, adding the previous day's campaign prioritization results.

This table includes customers that are targeted only by scheduled campaigns. For triggered campaigns, visit Engaged Customers. Read more about terminology in the Data Share Glossary.

📣
Latest version available: BI.VW_TARGETED_AND_EXCLUDED_CUSTOMERS_V1_6. Use the tabs below to view the version you're integrating against.

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

👍
What changed in V1_6: three new columns — PLAN_DETAIL_CHANNEL_ID, ENGAGEMENT_ID, and TEMPLATE_ID. ENGAGEMENT_ID is a single, consistent identifier for an engagement, shared across the engagement views; it is 0 for control-group rows. All other V1_5 columns are unchanged.

📌
Availability: The V1.6 columns and the primary-key change on this view are being rolled out to Campaign Execution 2.0 clients automatically 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 EXECUTION_DATE, CUSTOMER_ID, PLAN_ID → now CUSTOMER_ID, ENGAGEMENT_ID. Update any joins or dedup logic that relied on the V1_5 key.

🔑 Primary Key

Primary Key: CUSTOMER_ID, ENGAGEMENT_ID
Watermark column: LAST_UPDATED_TIME

Table Description

Field Name	Description	Data Type	Format
`EXECUTION_DATE`	Date when the campaign was executed	DATE	YYYY-MM-DD
`CUSTOMER_ID`	Optimove internal unique identifier for the customer	NUMBER(38,0)
`CLIENT_CUSTOMER_ID`	Unique identifier of customer as provided by the customer	TEXT(200)
`LIFECYCLE_STAGE_ID`	ID of lifecycle stage of customer when the campaign was executed	NUMBER(38,0)
`LIFECYCLE_STAGE_NAME`	Lifecycle stage of customer when the campaign was executed	TEXT(200)
`PLAN_ID`	Unique identifier for the campaign plan	NUMBER(38,0)
`PLAN_DETAIL_ID`	Unique identifier for the specific detail within the campaign plan	NUMBER(38,0)
`ACTION_SERIAL`	Unique serial of the campaign action. Added in V1_5; links this view to `VW_ENGAGEMENT_ACTIVITY`	NUMBER(38,0)
`CAMPAIGN_ACTION_ID`	ID of the action within a campaign or 1 for control group	NUMBER(38,0)
`CAMPAIGN_ACTION_NAME`	Name of the campaign action or DN for control group	TEXT(16777216)
`TAKEN_FROM_PLAN_ID`	Plan ID from which the campaign action was taken. If `NULL`, this is the plan the customer was targeted with	NUMBER(38,0)
`EXCLUSION_REASON_ID`	Unique identifier for the reason a customer was excluded from the campaign	NUMBER(38,0)
`EXCLUSION_REASON`	The exclusion reason	TEXT(50)
`EXCLUSION_REASON_DESC`	A detailed description of why the customer was excluded	TEXT(100)
`PLAN_DETAIL_CHANNEL_ID`	Unique identifier for the channel used within a plan detail (a communication on a single channel of a campaign). Added in V1_6.	NUMBER(38,0)
`ENGAGEMENT_ID`	Unique identifier of an engagement record, consistent across the engagement views. `0` for control-group rows. Added in V1_6 — part of the primary key.	NUMBER(38,0)
`TEMPLATE_ID`	Identifier for the engagement/communication template used. Added in V1_6.	NUMBER(38,0)
`LAST_UPDATED_TIME`	The timestamp of the last update to this record	TIMESTAMP_TZ	YYYY-MM-DD HH:MM

-- FOR V1.5
SELECT *
FROM [SHARED_DB].[BI].[VW_TARGETED_AND_EXCLUDED_CUSTOMERS_V1_5]

👍
What changed in V1_5: a new ACTION_SERIAL column between PLAN_DETAIL_ID and CAMPAIGN_ACTION_ID — the unique serial of the campaign action and the join key into VW_ENGAGEMENT_ACTIVITY.

🔑 Primary Key

Primary Key: EXECUTION_DATE, CUSTOMER_ID, PLAN_ID
Watermark column: LAST_UPDATED_TIME

Table Description

Field Name	Description	Data Type	Format
`EXECUTION_DATE`	Date when the campaign was executed	DATE	YYYY-MM-DD
`CUSTOMER_ID`	Optimove internal unique identifier for the customer	NUMBER(38,0)
`CLIENT_CUSTOMER_ID`	Unique identifier of customer as provided by the customer	TEXT(200)
`LIFECYCLE_STAGE_ID`	ID of lifecycle stage of customer when the campaign was executed	NUMBER(38,0)
`LIFECYCLE_STAGE_NAME`	Lifecycle stage of customer when the campaign was executed	TEXT(200)
`PLAN_ID`	Unique identifier for the campaign plan	NUMBER(38,0)
`PLAN_DETAIL_ID`	Unique identifier for the specific detail within the campaign plan	NUMBER(38,0)
`ACTION_SERIAL`	Unique serial of the campaign action. Added in V1_5; links this view to `VW_ENGAGEMENT_ACTIVITY`	NUMBER(38,0)
`CAMPAIGN_ACTION_ID`	ID of the action within a campaign or 1 for control group	NUMBER(38,0)
`CAMPAIGN_ACTION_NAME`	Name of the campaign action or DN for control group	TEXT(16777216)
`TAKEN_FROM_PLAN_ID`	Plan ID from which the campaign action was taken. If `NULL`, this is the plan the customer was targeted with	NUMBER(38,0)
`EXCLUSION_REASON_ID`	Unique identifier for the reason a customer was excluded from the campaign	NUMBER(38,0)
`EXCLUSION_REASON`	The exclusion reason	TEXT(50)
`EXCLUSION_REASON_DESC`	A detailed description of why the customer was excluded	TEXT(100)
`LAST_UPDATED_TIME`	The timestamp of the last update to this record	TIMESTAMP_TZ	YYYY-MM-DD HH:MM

-- FOR V1.3
SELECT *
FROM [SHARED_DB].[BI].[VW_TARGETED_AND_EXCLUDED_CUSTOMERS_V1_3]

🔑 Primary Key

Primary Key: EXECUTION_DATE, CUSTOMER_ID, PLAN_ID
Watermark column: LAST_UPDATED_TIME

Table Description

Field Name	Description	Data Type	Format
`EXECUTION_DATE`	Date when the campaign was executed	DATE	YYYY-MM-DD
`CUSTOMER_ID`	Optimove internal unique identifier for the customer	NUMBER(38,0)
`CLIENT_CUSTOMER_ID`	Unique identifier of customer as provided by the customer	TEXT(200)
`LIFECYCLE_STAGE_ID`	ID of lifecycle stage of customer when the campaign was executed	NUMBER(38,0)
`LIFECYCLE_STAGE_NAME`	Lifecycle stage of customer when the campaign was executed	TEXT(200)
`PLAN_ID`	Unique identifier for the campaign plan	NUMBER(38,0)
`PLAN_DETAIL_ID`	Unique identifier for the specific detail within the campaign plan	NUMBER(38,0)
`CAMPAIGN_ACTION_ID`	ID of the action within a campaign or 1 for control group	NUMBER(38,0)
`CAMPAIGN_ACTION_NAME`	Name of the campaign action or DN for control group	TEXT(16777216)
`TAKEN_FROM_PLAN_ID`	Plan ID from which the campaign action was taken. If `NULL`, this is the plan the customer was targeted with	NUMBER(38,0)
`EXCLUSION_REASON_ID`	Unique identifier for the reason a customer was excluded from the campaign	NUMBER(38,0)
`EXCLUSION_REASON`	The exclusion reason	TEXT(50)
`EXCLUSION_REASON_DESC`	A detailed description of why the customer was excluded	TEXT(100)
`LAST_UPDATED_TIME`	The timestamp of the last update to this record	TIMESTAMP_TZ	YYYY-MM-DD HH:MM

Targeted and Excluded Customers

Overview

Latest version available: `BI.VW_TARGETED_AND_EXCLUDED_CUSTOMERS_V1_6`. Use the tabs below to view the version you're integrating against.

What changed in V1_6: three new columns — `PLAN_DETAIL_CHANNEL_ID`, `ENGAGEMENT_ID`, and `TEMPLATE_ID`. `ENGAGEMENT_ID` is a single, consistent identifier for an engagement, shared across the engagement views; it is `0` for control-group rows. All other V1_5 columns are unchanged.

Breaking — primary key changed in V1_6: was `EXECUTION_DATE, CUSTOMER_ID, PLAN_ID` → now `CUSTOMER_ID, ENGAGEMENT_ID`. Update any joins or dedup logic that relied on the V1_5 key.

🔑 Primary Key

Table Description

What changed in V1_5: a new `ACTION_SERIAL` column between `PLAN_DETAIL_ID` and `CAMPAIGN_ACTION_ID` — the unique serial of the campaign action and the join key into `VW_ENGAGEMENT_ACTIVITY`.

🔑 Primary Key

Table Description

🔑 Primary Key

Table Description

Overview

Latest version available: BI.VW_TARGETED_AND_EXCLUDED_CUSTOMERS_V1_6. Use the tabs below to view the version you're integrating against.

What changed in V1_6: three new columns — PLAN_DETAIL_CHANNEL_ID, ENGAGEMENT_ID, and TEMPLATE_ID. ENGAGEMENT_ID is a single, consistent identifier for an engagement, shared across the engagement views; it is 0 for control-group rows. All other V1_5 columns are unchanged.

Breaking — primary key changed in V1_6: was EXECUTION_DATE, CUSTOMER_ID, PLAN_ID → now CUSTOMER_ID, ENGAGEMENT_ID. Update any joins or dedup logic that relied on the V1_5 key.

🔑 Primary Key

Table Description

What changed in V1_5: a new ACTION_SERIAL column between PLAN_DETAIL_ID and CAMPAIGN_ACTION_ID — the unique serial of the campaign action and the join key into VW_ENGAGEMENT_ACTIVITY.

🔑 Primary Key

Table Description

🔑 Primary Key

Table Description

Latest version available: `BI.VW_TARGETED_AND_EXCLUDED_CUSTOMERS_V1_6`. Use the tabs below to view the version you're integrating against.

What changed in V1_6: three new columns — `PLAN_DETAIL_CHANNEL_ID`, `ENGAGEMENT_ID`, and `TEMPLATE_ID`. `ENGAGEMENT_ID` is a single, consistent identifier for an engagement, shared across the engagement views; it is `0` for control-group rows. All other V1_5 columns are unchanged.

Breaking — primary key changed in V1_6: was `EXECUTION_DATE, CUSTOMER_ID, PLAN_ID` → now `CUSTOMER_ID, ENGAGEMENT_ID`. Update any joins or dedup logic that relied on the V1_5 key.

What changed in V1_5: a new `ACTION_SERIAL` column between `PLAN_DETAIL_ID` and `CAMPAIGN_ACTION_ID` — the unique serial of the campaign action and the join key into `VW_ENGAGEMENT_ACTIVITY`.