Customer Insights Journeys triggers: choosing between interaction and Dataverse records
Diesen Beitrag auf Deutsch lesen
Customer Insights Journeys offers interaction and record-change triggers. Dataverse records add application-owned history that can be queried and reported on.
TL;DR
Customer Insights Journeys supports triggers for website or app interactions and for Dataverse record creation or updates. The interaction trigger uses a generated integration snippet but did not expose a directly queryable Dataverse history table in this investigation. A Dataverse-based trigger requires integration to create records, enabling application-owned history and reporting.
Original by Temmy Raharjo, on Temmy Raharjo's Blog. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Choose the interaction trigger for simple application-invoked journeys, or create Dataverse records when the application needs queryable interaction history.
- Admins/CoE: Validate the selected table type, relationships and automation capabilities before relying on the Dataverse trigger design.
- Security/Compliance: Treat the Dataverse record as evidence of what the integration recorded, not proof that a journey started or an email was delivered.
- Leadership/Business: Align reporting expectations with the data source, using Dataverse for recorded interactions and Customer Insights journey insights for outcomes.
Frequently asked questions
How does the Customer Insights Journeys website or app interaction trigger work?
The application invokes the published trigger using its generated integration snippet and supplied customer data, such as Contact or Lead attributes.
Why use a Dataverse record-change trigger for Customer Insights Journeys?
It lets an integration create or update a customer-related Dataverse row, producing an application-owned interaction history that can be queried and reported on.
Does a Dataverse interaction record prove that a Customer Insights journey email was delivered?
No. The record shows what the integration recorded; Customer Insights journey insights are needed for journey entry and email delivery outcomes.