Guides

Version V1_6

Released: <2026-07-13> · 3 views changed · 3 breaking changes (primary-key changes)

V1_6 introduces ENGAGEMENT_ID — a single, consistent identifier for an engagement that is shared across the engagement views — plus channel/template/send identifiers on the campaign views. New columns are additive, but the primary key changes on all three views (see each section).

⚠️

Breaking: the primary key changed on VW_TARGETED_AND_EXCLUDED_CUSTOMERS, VW_ENGAGED_CUSTOMERS, and VW_ENGAGEMENT_ACTIVITY. Review any joins, upserts, or dedup logic keyed on the V1_5 keys before migrating.

📌

Availability. The V1.6 columns and key changes are rolling out to Campaign Execution 2.0 clients automatically over the coming months; data begins at each client's rollout date. To get access sooner, contact your Customer Success Manager.

VW_TARGETED_AND_EXCLUDED_CUSTOMERS_V1_6

Added

  • PLAN_DETAIL_CHANNEL_ID (NUMBER) — channel used within a plan detail.
  • ENGAGEMENT_ID (NUMBER) — shared engagement join key; 0 for control-group rows.
  • TEMPLATE_ID (NUMBER) — engagement/communication template used.

Primary key changed: EXECUTION_DATE, CUSTOMER_ID, PLAN_ID → CUSTOMER_ID, ENGAGEMENT_ID.

VW_ENGAGED_CUSTOMERS_V1_6

Added

  • PLAN_DETAIL_CHANNEL_ID (NUMBER) — channel used within a plan detail.
  • SEND_ID (TEXT) — per-send identifier; 0 for control-group rows.

Primary key changed: ID, TEMPLATE_NAME → CUSTOMER_ID, SEND_ID.

VW_ENGAGEMENT_ACTIVITY_V1_6

Added

  • ENGAGEMENT_ID (NUMBER) — shared engagement join key. (PLAN_DETAIL_CHANNEL_ID already present since V1_5.)

Primary key changed: CUSTOMER_ID, SEND_ID → CUSTOMER_ID + ENGAGEMENT_ID (scheduled campaigns) / CUSTOMER_ID + SEND_ID (triggered campaigns).

Entity Relation Diagram

Updated: all entity suffixes _V1_5 → _V1_6; new columns and revised key flags on the three engagement entities.

All other views

Version suffix bump only (_V1_5 → _V1_6), no schema change.

Migration

New columns are additive, but the primary key changed on the three views above — update any joins, upserts, or dedup logic accordingly. To adopt V1_6, change the view suffix in your queries (_V1_5 → _V1_6). Earlier-generation views remain queryable; do not join views from different generations in a single query.

Updated 18 days ago

Did this page help you?