DocumentationExperience PlatformSource Connectors Guide

Salesforce

Last update: Sat Jul 22 2023 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Developer
  • User
  • Admin
  • Leader

Adobe Experience Platform allows data to be ingested from external sources while providing you with the ability to structure, label, and enhance incoming data using Platform services. You can ingest data from a variety of sources such as Adobe applications, cloud-based storage, databases, and many others.

Experience Platform provides support for ingesting data from a third-party CRM system. Support for CRM providers include Salesforce.

IP address allow list

A list of IP addresses must be added to an allow list prior to working with source connectors. Failing to add your region-specific IP addresses to your allow list may lead to errors or non-performance when using sources. See the IP address allow list page for more information.

Field mapping from Salesforce to XDM

To establish a source connection between Salesforce and Platform, the Salesforce source data fields must be mapped to their appropriate target XDM fields prior to being ingested into Platform.

See the following for detailed information on the field mapping rules between Salesforce datasets and Platform:

Set up the Salesforce namespace and schema auto-generation utility

To use the Salesforce source as part of B2B-CDP, you must first set up a Postman utility to auto-generate your Salesforce namespaces and schemas. The following documentation provides additional information on setting up the Postman utility:

With a Platform developer console and Postman set up, you can now start applying the appropriate environment values to your Postman environment.

The following table contains example values as well as additional information on populating your Postman environment:

Variable
Description
Example
CLIENT_SECRET
A unique identifier used to generate your {ACCESS_TOKEN}. See the tutorial on authenticating and accessing Experience Platform APIs for information on how to retrieve your {CLIENT_SECRET}.
{CLIENT_SECRET}
JWT_TOKEN
The JSON Web Token (JWT) is an authentication credential used to generate your {ACCESS_TOKEN}. See the tutorial on authenticating and accessing Experience Platform APIs for information on how to generate your {JWT_TOKEN}.
{JWT_TOKEN}
API_KEY
A unique identifier used to authenticate calls to Experience Platform APIs. See the tutorial on authenticating and accessing Experience Platform APIs for information on how to retrieve your {API_KEY}.
c8d9a2f5c1e03789bd22e8efdd1bdc1b
ACCESS_TOKEN
The authorization token required to complete calls to Experience Platform APIs. See the tutorial on authenticating and accessing Experience Platform APIs for information on how to retrieve your {ACCESS_TOKEN}.
Bearer {ACCESS_TOKEN}
META_SCOPE
With regards to Marketo, this value is fixed and is alway set to: ent_dataservices_sdk.
ent_dataservices_sdk
CONTAINER_ID
The global container holds all standard Adobe and Experience Platform partner provided classes, schema field groups, data types, and schemas. With regards to Marketo, this value is fixed and is always set to global.
global
PRIVATE_KEY
A credential used to authenticate your Postman instance to Experience Platform APIs. See the tutorial on setting up developer console and setting up developer console and Postman for instructions on how to retrieve your {PRIVATE_KEY}.
{PRIVATE_KEY}
TECHNICAL_ACCOUNT_ID
A credential used to integrate to Adobe I/O.
D42AEVJZTTJC6LZADUBVPA15@techacct.adobe.com
IMS
The Identity Management System (IMS) provides the framework for authentication to Adobe services. With regards to Marketo, this value is fixed and is always set to: ims-na1.adobelogin.com.
ims-na1.adobelogin.com
IMS_ORG
A corporate entity that can own or license products and services and allow access to its members. See the tutorial on setting up developer console and Postman for instructions on how to retrieve your {ORG_ID} information.
ABCEH0D9KX6A7WA7ATQE0TE@adobeOrg
SANDBOX_NAME
The name of the virtual sandbox partition that you are using.
prod
TENANT_ID
An ID used to ensure that the resources you create are namespaced properly and are contained within your organization.
b2bcdpproductiontest
PLATFORM_URL
The URL endpoint that you are making API calls to. This value is fixed and is always set to: http://platform.adobe.io/.
http://platform.adobe.io/
munchkinId
The unique ID for your Marketo account. See the tutorial on authenticating your Marketo instance for information on how to retrieve your munchkinId.
123-ABC-456
sfdc_org_id
The organization ID for your Salesforce account. See the following Salesforce guide for more information on acquiring your Salesforce organization ID.
00D4W000000FgYJUA0
has_abm
A boolean value that indicates if you are subscribed to Marketo Account-Based Marketing.
false
has_msi
A boolean value that indicates if you are subcscribed to Marketo Sales Insight.
false

Running the scripts

With your Postman collection and environment set up, you can now run the script through the Postman interface.

In the Postman interface, select the root folder of the auto-generator utility and then select Run from the top header.

root-folder

The Runner interface appears. From here, ensure that all the checkboxes are selected and then select Run Namespaces and Schemas Autogeneration Utility.

run-generator

A successful request creates the B2B namespaces and schemas according to beta specifications.

Connect Salesforce to Platform using APIs

The documentation below provides information on how to connect Salesforce to Platform using APIs or the user interface:

Connect Salesforce to Platform using the UI

recommendation-more-help
337b99bb-92fb-42ae-b6b7-c7042161d089