Salesforce Source Connector into B2C AEP

[neeravg]

Had a question about Salesforce Source Connector. How does the object mapping work? Salesforce is primarily B2B unless you enable person accounts for B2C. If you have a B2C AEP, what object do you ingest from Salesforce to enhance your customer profile? Is it contact object? Also do you need to enable person account in Salesforce before you ingest into B2C AEP? Some guidance and considerations for this integration would be helpful. 

[ChetanyaJain]

Hi @neeravg, 

The most important thing to identify is how you wish to use the SF data for your use case.

Here are some tips:

• Identify your use case
• Based on that, identify what essential data you need to bring in.
• Create a model for that data - remember SF to AEP need not be 1-1 mapping. You will need to consider how you have defined your profile in AEP. At times your profile will be for customers or accounts. It purely depends on the use case that you are trying to resolve.

Please let me know if you have specific questions or want to share the use case you are trying to resolve.

Thanks,

Chetanya

[neeravg]

Thank for your reply, @ChetanyaJain . Question was around the mapping. Understand about the usecase and so on. If a customer has a B2C License and not b2b, how does it work? Because in the mapping i saw lot of b2b fields mapped from Salesforce to AEP. Link here. So in that case what happens to those fields - can we just leave in blank? Also in B2C Scenario what object in Salesforce will primarily contribute to the profiles info? Last question - How the stitching would happen - based on which Id and that ID will have to be part of the salesforce record right? So for first time how that ID mapping would happen and will Salesforce will have to load the ID? 

[ChetanyaJain · Accepted solution]

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!

[neeravg]

Thank you @ChetanyaJain Will look into it. Any thoughts on the last question for ID mapping question between Adobe and Salesforce as to how it works? Also for first time how it will work? 

[ChetanyaJain]

Hi @neeravg,

For ID, focus on which property makes an ID field in AEP. Once defined, create the appropriate identity namespace and create the schema. While loading the data from Salesforce map the field, and ensure that this field is not empty.

Ensure that the schema and dataset are enabled for profile, before loading the data from Salesforce - otherwise this data will not be shown in the profile view upon searching.

Please let me know if you have any specific questions.

Regards,

Chetanya

[neeravg]

Thanks Chetanya!