Hi @neeravg,
The Salesforce to AEP mapping you shared works well when you have a B2B instance. However, if you are dealing with a B2C instance, you may want to recreate your model in AEP based on the use cases for activation.
You don't necessarily need to always go with the OOB schema; you must make changes based on what works best in your scenarios. Here's how I would approach it:
- Identify what's your use case
- Identify what attributes will be the right ID fields
- Define what profile is in AEP. Here are some examples:
- The customer is the profile
- An account is a profile (if a customer has multiple accounts, then the account is a profile)
- In the pet industry - the pet can be a profile (however, the pet owner is the target to receive the communication), or PET & pet owner both can be profiles.
- To activate your use case, what data is essential that you need to bring from various sources (e.g., salesforce)
- Design your schema accordingly - you may need to consider arrays or create relationship datasets. Don't restrict yourself to using only OOB schemas.
- Get only the essential fields required for the use case and leave the rest - Do not bring the fields that will have no value for segmentation or activation.
Hope this helps!
