Triggered - Engaged Customers

Targeting History under real time campaigns

Views are out-of-the-box data queries on top of the base structure of the data, providing easy access to common use cases and additional data useful to exploit the data lake fully. Using views, Data Share evolves while providing you with data contracts that are kept stable, enabling reliable integrations with your internal platforms.

Overview

This view provides a snapshot of targeting history by triggered campaigns for customers. Use it to query, monitor, and analyze which triggered campaigns your customers are targeted by, and to identify the most engaging campaigns and templates.

It is the parallel view to Targeted and Excluded Customers, representing triggered campaigns executed alongside scheduled campaigns. Read more about terminology in the Data Share Glossary.

📣

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

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

What changed in V1_6: two new columns — PLAN_DETAIL_CHANNEL_ID and SEND_ID. SEND_ID is the per-send identifier ('DN' for control-group rows) and is now part of the primary key. The primary key changed (see below). 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 ID, TEMPLATE_NAME → now CUSTOMER_ID, SEND_ID. Update any joins or dedup logic that relied on the V1_5 key.

🔑 Primary Key

  • Primary Key: CUSTOMER_ID, SEND_ID

Table Description

Column NameDescriptionData TypeFormat
IDUnique identifier for engagement recordNUMBER(38,0)
CUSTOMER_IDUnique identifier for the customerNUMBER(38,0)
CLIENT_CUSTOMER_IDUnique identifier of customer as provided by the clientTEXT(510)
ENGAGED_DATETimestamp of campaign triggeringTIMESTAMP_NTZYYYY-MM-DD
ACTION_SERIALID of a campaign occurrence on a specific day (Optimove internal)NUMBER(38,0)
CAMPAIGN_ACTION_IDID of the action within a campaign or 1 for control groupNUMBER(38,0)
CAMPAIGN_ACTION_NAMEName of the campaign action or DN for control groupTEXT(16777216)
CAMPAIGN_DETAIL_IDUnique identifier for the campaign detailNUMBER(38,0)
IS_VISITORFlag indicating if the customer is a visitorNUMBER(38,0)
OPTIMOVE_IDUnique identifier assigned by OptimoveNUMBER(38,0)
TEMPLATE_IDIdentifier for the engagement templateNUMBER(38,0)
TEMPLATE_NAMEName of the template associated with this sub-actionTEXT(16777216)
PLAN_DETAIL_CHANNEL_IDUnique identifier for the channel used within a plan detail. Added in V1_6.NUMBER(38,0)
SEND_IDUnique identifier for the send action. 'DN' for control-group rows. Added in V1_6 — part of the primary key.TEXT


Did this page help you?