I have a segment based journey that sends messages to a segment based on customer profiles from CI-D. I want to set a custom business measure, where I count instances of a field being updated in a dataverse table after the recipient participated in the journey. Is this possible to achvieve? Or is it only possible to do when sending to leads or contacts?. The list of triggers that are available when I select are only common triggers like email deliverd, opened, .... And when I create a new trigger based on dataverse I get the error message that this trigger can not be used with a ci-d profile.
Is there a workaround for this anyone can point to? Or is it possible to use custom triggers?
Yes, it is possible to track a custom business measure—such as a field update in a Dataverse table—after a customer with a CI-D profile has participated in a journey, but there are limitations and workarounds involved due to how CI-D profiles and triggers interact in Real-time Marketing (RTM) in Dynamics 365.
✅ Problem Summary
You're using Customer Insights - Data (CI-D) customer profiles as your journey audience in Real-time Marketing. You want to set a custom journey goal that is triggered when a field in a Dataverse table is updated after a journey interaction. However:
The Dataverse trigger is not compatible with CI-D profiles.
Only default triggers (email delivered, opened, etc.) are available when using CI-D.
✅ Confirmed Limitation
Currently, custom Dataverse-based triggers cannot be directly used with journeys targeting CI-D profiles. Microsoft’s Real-time Marketing platform does not allow combining CI-D profiles with Dataverse event triggers out of the box.
✅ Workaround Solution
You can work around this limitation by using a combination of the following techniques:
Option 1: Use a Power Automate Flow + Custom Trigger Mapping
Create a custom trigger in Real-time Marketing (based on a custom event definition).
Go to Customer Insights - Journeys → Triggers.
Define a custom event that includes relevant data like contactId or a unique identifier for your CI-D profile.
In Power Automate, create a flow that:
Monitors the Dataverse table for the field update (using the When a row is modified trigger).
Looks up the related CI-D profile (based on a mapping logic, like email, contact ID, or a custom key).
Calls the Real-time Marketing custom trigger via the Outbound API:
Use the Trigger a journey HTTP API.
Payload should match the custom trigger schema you've defined.
In your journey:
Add the custom trigger as a goal condition or step.
This will allow you to simulate a custom goal based on any external update, including from Dataverse, even when targeting CI-D profiles.
Option 2: Sync Data to Unified Contacts and Use Leads/Contacts Instead
If maintaining full compatibility with built-in triggers is critical, you may consider:
Syncing your CI-D customer profile data into Dataverse contact or lead tables.
Running journeys on contacts or leads instead of CI-D profiles.
Then use native Dataverse triggers or custom goals based on field updates.
⚠️ However, this reduces the flexibility of using Customer Insights as your main segmentation engine.
✅ Conclusion
While custom triggers can't directly run with CI-D profiles, using Power Automate to push a custom event into Real-time Marketing when a Dataverse field is updated is a reliable workaround. Let me know if you need help with the Power Automate setup or the custom trigger schema.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.