We are comparing one saved view with Real-time Segment. This part is causing some differences. Like you see from this picture, there are two filters from related Quote table.
This is how the same filter is configured in Segment:
The segment is showing less contacts (~5.000) then original view is showing (7.000).
If this filter with related Quote is removed, the number of contacts is the same, so we believe that this Group 3 is causing the issue.
This is something we have heard from multiple customers.
There could be multiple reasons why this could be happening:
1. BU definitions - In OBM, we saw an issue where the BU boundaries were not being included in the segment which was an issue - In RTM, if you have defined BUs, then these take effect in limiting the segment memberships to only those that are present in the BUs added.
2. Internal changes to pipelines: We recently moved customers from an older, more error prone pipeline to a new more performant pipeline that has better responses to data syncs. This could cause some changes to how membership has been calculated.
3. Changes to the MQL queries - We have noticed that in some cases, the segment definition does not translate exactly to the backend queries between OBM and RTM - It would be useful to get the Org ID and the segment IDs for the two segments to evaluate if something is going on there.
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.
151
Share
Report
All responses (
Answers (
