Today, Dynamics 365 Customer Insights – Journeys does not natively persist or expose a customer’s business-specific Trigger ID (for example, an external Email Trigger ID) in email interaction and analytics tables such as Sent, Opened, and Clicked. While Trigger IDs can be used at runtime within journeys for branching and personalization, they are not available for post-send reporting, auditability, or analytics.

This limitation creates a significant gap for customers who rely on external systems to initiate journeys and need deterministic answers to specific business questions

Proposed enhancement: Introduce a native capability in Customer Insights – Journeys to persist and expose a custom Trigger ID (or other business correlation key) alongside journey runs and email interaction records. This Trigger ID should be:

• Automatically stored when a journey is initiated by a custom trigger.
• Available as a first-class dimension in analytics and reporting (Sends, Opens, Clicks).
• Queryable via Dataverse, APIs, and built-in analytics without custom joins.
• Optional but configurable, so customers can choose which business identifier to persist.