Sitecore Best Practice Series:


Sitecore CDP & Personalize Best Practices


# Practice Rationale
1. Use optimized testing for automation Optimized testing involves AI for dynamically managing traffic allocation and starts automatically sending more traffic to the best performing variant saving manual effort.
2. Enable debug feature when troubleshooting configuration The Debug feature allows viewing all configuration data in a table or in JSON in certain screens, which is helpful when performing troubleshooting.
3. Drop the tracking code on your current implementation early If you are thinking about migrating to Sitecore Personalize and CDP with XM from Sitecore XP, drop the embed code on your current website prior to starting the migration. Personalize does not provide the REST API for importing contact events, making it difficult to implement historical data personalization from the start. Capturing data early will allow accumulate some event data for historical personalization.
4. Enable two factor authentication Your customer data is your most precious asset, so make sure it is properly secured by enabling the two-factor authentication (2FA) no matter whether the rest of the organization's applications use it or not.
5. Pay close attention to AND, OR, NO operators in rules The rules joined using the AND operator get evaluated prior to the ones using OR or NOT. Incorrect order of rule processing may lead to unintended outcomes.
6. Interrogate CDP data before creating segments Interrogate the daa in Sitecore CDP so you can see the exact number and percentage of your contact that hold the attribute or value. This will give you the size of the segment and help you decide whether it is sufficient for the intended purpose in advance.
7. Limit the number of programmable decisions on the canvas to 3 Programmable decisions add processing overhead, therefore, try to use fewer than 3 programmable decisions in your decision models on the canvas.
8. Reduce the number of components on a decision canvas Processing overhead is caused by each additional component in a decision model. Try to reduce the number of components, if possible, in general, and for the models that cannot compromise on performance, try to create a custom component that would combine multiple ones at the cost of reusability, flexibility, and potentially higher maintenance cost in the future.
9. Add comments to decision model variants Comments help understand the reason for variant creation and the changes made. It is recommended to also include an internal tracking system reference number in the comment to help create a complete audit trail of the changes.

%d bloggers like this: