Why do you need CDP4D?
The real question is "Why do you need website behavioral data in Dynamics 365?" The answer is to help the Dynamics 365 team identify and prioritize leads based on their characteristics e.g. country, company, job title, or how they behaved on the website. Sitecore CDP can track this data but it really needs to be in Dynamics 365. Having up-to-the-minute intelligence and lead scores in Dynamics 365 helps sales reps focus on the prospects more likely to buy.
After lead qualification and prioritization, the next task is to prepare for a sales call. Sales reps use the recent, relevant, and contextual intelligence collected by the website to determine the prospect’s buying intentions. This information reveals the visitor's current state of mind, and how likely they are to purchase.
Many companies deepen engagement and increase sales by personalizing the website based on where the current visitor is in the buying journey. The field and status settings in the prospect's Dynamics 365 record can be returned to Sitecore CDP to become a deciding factor on how to personalize the website when the visitor returns. For example, if sales rep Luke, has recently spoken to a prospect, the prospect will be pleasantly surprised to see a personalized message from Luke when returning to the website a few days later.
CDP4D with S4D
S4D allows Sitecore content editors to quickly map web forms directly to Dynamics 365 entities, usually leads or contacts. When a visitor submits a mapped form, S4D creates (or updates) a Dynamics 365 record.
For Sitecore XM and Sitecore CDP customers, S4D submits the form data directly to Dynamics 365, and CDP4D independently pushes the behavioral analytics in Sitecore CDP to the matching Dynamics 365 record.
