web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested answer

Major architecture decision about whether to use segment based journeys or realtime journeys

(1) ShareShare
ReportReport
Posted on by 54
Hello guys,
      I have a question and not sure to decide whether to use segment based journeys or realtime journeys. Below is the requirements:

- we're migrating data from on-premise to customer insights, we're migrating 4 types of records, those records are then converted into notifications and created as notification . those records are related to contact as the below:

Each contact could have multiple "customer accounts", each "customer account" has multiple "notifications"
 
these notifications should be sent to the customer who exists in contact entity. The load of records in each batch is arround 400k
 
Note: Please take in consideration the below:
 
1- service protection limits
2- journeys will be used to send sms, email and push notifications, data for the notification sent to customer mainly exists in the notification and the imported record, only email and customer mobile number and device token exists in contact record
I have the same question (0)
  • Suggested answer
    Muhammad Shahzad Shafique Profile Picture
    2,336 Most Valuable Professional on at
    Major architecture decision about whether to use segment based journeys or realtime journeys
    Use Segment-Based Journeys 
    1. Batch Processing Efficiency 
       - You’re migrating 400K records per batch—real-time journeys would trigger 400K API calls instantly, risking throttling (Service Protection Limits). 
       - Segment-based journeys process data in bulk, avoiding API spikes. 
    2. Data Structure Alignment 
       - Your data is batch-imported (not real-time) and mapped to Contacts via relationships. 
       - Segment-based journeys sync pre-filtered audiences (e.g., "Contacts with unread Notifications") once, reducing runtime load. 
    3. Service Protection Limits 
       - Real-time journeys can hit Dynamics 365 API limits (e.g., 60K API calls/min per org). 
       - Segment-based journeys use asynchronous processing, staying within limits. 
    4. Cost & Performance 
       - Real-time journeys are expensive for high-volume batch operations. 
       - Segments are refreshed on schedule (e.g., hourly/daily), aligning with your batch imports. 
  • Mazex Profile Picture
    54 on at
    Major architecture decision about whether to use segment based journeys or realtime journeys
       Thank you for your reply. I understand what's written above in comparison between both as I totally understand that segment based has more scalibility.
     
    However one important aspect here is the number of notifications, as mentioned, in the batch as a customer you would receive multiple notifications. Even thought the segment can be refreshed multiple times, the journey will run only one time a day, so as a customer if you have let's say 10 notifications, in the best cases you'll get them on 10 days. as the journey will retrieve one unread notification per run.
     
    Also, one more thing, how we can update the notification to be as "sent" to avoid reading the same notification again? We can't pass anything other than customer data from the journey to a custom action
     
    Thanks.

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.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Rishabh Kanaskar Profile Picture

Rishabh Kanaskar 228

#2
Tom_Gioielli Profile Picture

Tom_Gioielli 156 Super User 2025 Season 2

#3
MVP-Daniyal Khaleel Profile Picture

MVP-Daniyal Khaleel 149

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans