Dynamics 365 Customer Insights: Use Journeys Behavior for Segments and Measures—Batch Limits

Bridging that divide previously meant building and maintaining custom data plumbing—specifically, waiting on specialized data flows to export behavioral interaction records from Microsoft Dataverse into Microsoft Fabric, and then ingesting them back into Customer Insights - Data.

Under Microsoft's AI at Work roadmap item 576827 (tracked in the 2026 release wave 1 plan and Microsoft Message Center notice MC1411121), Microsoft has eliminated that intermediate data-flow requirement. Behavioral interaction data captured by Customer Insights - Journeys is now automatically available directly inside Customer Insights - Data for building segments and calculated measures. Following a preview rollout in May 2026, the capability reached general availability in July 2026 for Worldwide (Standard Multi-Tenant) web environments and is enabled automatically for administrators, makers, and marketers.

Here is a complete breakdown of how the native integration works, what interaction signals are exposed, how to configure behavioral segments and measures, and the crucial architectural limitations—especially around batch processing—that IT and marketing ops teams need to understand before retiring their existing workflows.

Eliminating the Dataverse-to-Fabric Detour​

The core value proposition of this update is architectural simplification and better audience precision. In any sizable CRM deployment, a single human customer often exists as multiple contact or lead records tied to different email addresses, phone numbers, or loyalty accounts. If a marketer only segments inside the execution engine based on a single email address, they are targeting an inbox rather than a person.

By bringing campaign response signals directly into Customer Insights - Data without custom Dataverse-to-Fabric pipelines, organizations can evaluate campaign behavior against unified customer profiles. According to Microsoft's roadmap and release documentation, this unlocks several practical workflows:

• Identity-Resolved Engagement Tracking: Because Customer Insights - Data unifies records across multiple contact points, teams can see how a single customer interacts with the brand across separate email addresses or channels, rather than treating each address as a disconnected prospect.
• Composite Scoring and High-Intent Targeting: Makers can combine Journeys interaction data with external data sources and predictive AI outputs. For example, a team can build a segment of unified profiles that hold a high predicted lifetime value score and have actively engaged with recent campaigns by opening emails or clicking product links.
• Escalated Retargeting: Microsoft illustrates a common retail scenario where a monthly campaign offering a 5 percent discount yields a high email open rate but a low coupon click-through rate. Rather than blasting the entire list again, a marketer can isolate the specific segment of customers who opened the message without selecting the coupon and retarget them with a 10 percent offer—though teams should treat such retail scenarios as illustrative targeting strategies rather than guaranteed conversion outcomes.
• Cross-Channel Export for Non-Responders: When customers consistently ignore email or push campaigns, marketers can group those non-responsive unified profiles into a dedicated segment and use Customer Insights - Data export connectors to retarget them on external advertising and social platforms such as Google and Meta.

Section Summary: Native ingestion of Journeys behavioral data into Customer Insights - Data removes the need for custom Dataverse-to-Fabric export flows, allowing teams to combine multi-channel campaign signals with unified customer profiles and predictive scoring.

Prerequisites and Supported Interaction Signals​

Before marketers go looking for the new behavioral options in their workspace, administrators must ensure two strict prerequisites documented by Microsoft Learn are satisfied:

1. Same-Environment Deployment: Both Customer Insights - Journeys and Customer Insights - Data must be deployed within the exact same environment.
2. Profile Unification: The contact or lead records from Customer Insights - Journeys must be included in your data unification rules so they resolve into unified customer profiles.

Once unified, interaction records are stored in system tables visible under the System section on the Tables page in Customer Insights - Data (note that the interface only displays tables that currently contain data).

Microsoft Learn documentation confirms that the integration captures four primary categories of behavioral events across channels:

Each interaction table exposes granular metadata fields that can be used as filter conditions, including Journey, Email, Email address, Email client, Timestamp, Profile ID, and Profile type.

Section Summary: The integration requires both Dynamics 365 apps to reside in the same environment with unified contact or lead records, exposing 21 distinct interaction types across email, SMS, push notifications, forms, and events.

Step-by-Step: Building Behavioral Segments and Measures​

Because this feature is enabled automatically for admins, makers, and marketers, eligible environments will see a Behavioral tab inside both the segment builder and the measure builder.

How to Filter a Segment by Campaign Behavior​

To build a target audience based on how unified profiles responded—or failed to respond—to earlier campaigns, Microsoft Learn outlines the following procedure:

1. Navigate to Insights > Segments and select New > Build your own.
2. Click Edit details to assign a clear name to your segment.
3. In the Add to Rule 1 side panel, select the Behavioral tab.
4. Expand the desired interaction category (such as Email Opened) to browse its fields, or use the search bar at the top of the panel.
   • Pro Tip for Admins: The search box queries the underlying technical field names rather than localized display labels. If a search comes up empty, type a portion of the technical schema name or click Show display names at the bottom of the panel to toggle views.
5. Select a field (or drag it onto Rule 1). For example, to target recipients who opened a specific campaign message, expand Email Opened and select the Email field, which places EmailOpened: CustomerInsightsJourneysInteractions.Email is equal to onto the canvas.
6. Configure the operator, select the specific campaign email from the value dropdown, and optionally apply a rolling time window (such as within the last 7 or 30 days).
7. Add any additional demographic, transactional, or predictive rules, then click Save and Run.

How to Aggregate Interactions in a Customer Measure​

If you want to score engagement frequency—such as identifying subscribers who have opened more than five emails in the past 60 days—you can build a calculated measure first:

1. Go to Insights > Measures and select New > Build your own.
2. Select Add dimension or begin adding conditions directly in the builder, then switch to the Behavioral tab in the side panel.
3. Choose an interaction type and field to aggregate (for example, counting Email Opened events per profile).
4. Set your aggregation function (count, sum, average, min, or max) along with any required filters or time windows, then save and run the measure.
5. Once calculated, use that measure as a standard attribute inside your segment conditions.

Section Summary: Marketers can access the Behavioral tab in both the Segment and Measure builders to filter by specific campaign assets, apply rolling time windows, or calculate aggregate engagement frequency per customer.

Closing the Loop: Syncing Segments Back to Journeys and Managing Load​

Creating a refined segment in Customer Insights - Data is only half the workflow; teams then need to activate it inside Customer Insights - Journeys or export it via Insights > Segments > Manage exports.

When routing a segment back into Journeys, Microsoft Learn recommends verifying that the connected applications have synchronized properly by checking Power Apps > Tables > msdynci_segmentmembership in Dataverse to confirm membership data exists, and then selecting the audience under Customer Insights segments when building a journey. If a segment fails to appear or displays zero members, administrators should check three common failure points:

• Segment not visible in Journeys: Dataverse synchronization is turned off. Enable it under Settings > Data sharing.
• Segment shows 0 members: The initial Dataverse sync has not completed yet. Wait for the next scheduled system refresh.
• "Individual segment evaluation failed" error: The segment query references a table that is missing or empty. Edit the segment and verify all referenced tables exist and contain records.

Administrators should also keep a close eye on refresh overhead. In Customer Insights - Data, active dynamic segments refresh on their configured schedule, and evaluating a large volume of daily segments and measures slows down the overall system refresh—and can even trigger out-of-memory refresh failures if service limits are exceeded. Microsoft automatically deactivates unused segments (those not referenced in exports, measures, other segments, or Journeys, and untouched for more than 45 days) and tags them as AutoDeactivated, though administrators can override this per segment via Disable auto cleanup on the command bar. Best practice is to delete one-off campaign segments once a promotion ends, deactivate recurring segments between runs, and schedule non-urgent behavioral segments to refresh weekly or on weekends rather than daily.

The Fine Print: Batch Processing vs. Real-Time Execution​

While the marketing copy around "turbocharging your pipeline" sounds instantaneous, veteran Dynamics architects know to check the execution cadence. Is this new behavioral bridge a real-time event stream? No.

According to Microsoft Learn's technical documentation, teams must plan around five explicit architectural boundaries:

• Batch-Only Processing: Behavioral interaction data in Customer Insights - Data updates strictly on the Customer Insights - Data system refresh schedule, not in real time. Segments and measures always reflect customer actions as of the last successful batch refresh.
• Initial Ingestion Lag: When first enabled or deployed in large environments, initial ingestion of behavioral data can take anywhere from 30 minutes to several hours, depending on data volume.
• Unified Profiles Only: The segment and measure builders only evaluate interactions tied to a unified Customer Profile. If a contact or lead record in Journeys has not yet been unified, its behavioral interactions will not appear in Customer Insights - Data.
• No Customer Profile Timeline View: Behavioral events from Journeys are only exposed inside the segment and measure builders. They do not render on the Customer Profile timeline inside Customer Insights - Data; to inspect chronological interaction timelines, users must view contact insights inside Customer Insights - Journeys.
• Where to Do Real-Time Branching: If your campaign requires immediate, real-time journey branching the moment a user clicks a link or submits a form, Microsoft explicitly advises keeping that logic inside Customer Insights - Journeys, which operates directly on contact and lead records in real time.

Ultimately, this update is a welcome quality-of-life improvement for data and marketing teams. By letting Customer Insights - Journeys handle immediate, millisecond-level in-flight branching while feeding its interaction logs automatically into Customer Insights - Data for batch unification, multi-channel retargeting, and lifetime-value modeling, Microsoft gives administrators the benefits of unified customer intelligence without the headache of babysitting custom Fabric data pipelines.