Northern Trail Outfitters has a contact count of nearly 10 million records. They have noticed slower processing times when sending using Journey Builder.
Which two actions could they take to optimize Journey performance? (Choose 2 answers)
A.
Perform large-scale segmentation in Automation Studio before admitting contacts into Journey Builder.
B.
Use Data Extension Entry Sources with Filters applied to perform segmentation activities for Journey Builder.
C.
Include data for decision splits in Attribute Groups in Contact Builder, use contact data rather than journey data.
D.
Create a prefiltered, sendable copy of data extensions for each journey instead of using the same entry source.
A — Performing large segmentation in Automation Studio reduces the processing load inside Journey Builder, helping Journeys to focus only on eligible contacts.
C — Storing decision split data in Contact Builder’s Attribute Groups allows journeys to reference Contact Data instead of relying on static Journey Data, enabling faster and dynamic splits.
❌ Why others are wrong:
B: Applying filters inside the Journey can slow down entry and cause processing delays.
D: Creating multiple copies of DEs can cause unnecessary data duplication and still doesn't solve processing speed.
Exact Extract from Salesforce Official Documentation:
Salesforce Help — Journey Performance Best Practices:
"Optimize journey performance by filtering contacts prior to journey entry and by using Contact Data for decision splits rather than static Journey Data."
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit