The ESP - Salesforce Marketing Cloud (SFMC) connector was earlier known as ExactTarget.
Create CDP users in the SFMC application and share at least one admin account with Acquia.
Enable Automation Studio for the connector.
See Email before integrating CDP with SFMC.
Customer Data Platform pulls the following information from your application:
Full master contact list with the latest main subscription status
Historical load: past three months of events
Earlier, CDP had an integration with SFMC’s legacy ExactTarget SOAP API. However, the SOAP API only functions with the Classic tools in Marketing Cloud and does not scale well for high volume. Therefore, to import data from Salesforce to CDP, Acquia requires that you configure the SFMC Automation Studio to schedule tracking extracts of the necessary data to an sFTP.
CDP pushes audience and content to data extensions. You can have multiple data extensions. For example, abandoned cart and browse campaigns. The connector adds data to an existing data extension by doing Add & Update or Upsert. In one data extension, all data for a given record gets overwritten with the latest data.
The following is an example of pushing different campaigns to the same data
CAMPAIGN_ID changes, the fields populated change because
the second campaign pushes different content to the same data extension.
Note the following points about the destination table:
A tenant can have multiple destination tables.
Typically, Acquia creates one table per content type that you want to send. You can request Acquia to create additional tables, if required.
One destination table corresponds to one data extension in SFMC. The name of
that destination table is prefixed with
A1_ in the corresponding data
If the data extension already exists, the creation of the destination table fails.
You must ensure that your destination table contains all the columns that you might need for your campaigns. For example, if you plan to use the destination table to run an abandoned cart campaign, you can get all the usual product-related attributes, such as product sale price, product URL, product image URL, product name, product number, added to the table.
The following is the format for the column names in the destination table:
[name of the UDM+ table]_[name of the column in that UDM+ table
By defaault, CDP exports specific columns:
Any field that ends with
pitem_limit_count: This column is required if product content is used
For recurring campaigns, you must define the primary key for the destination
table. Acquia recommends that you select
PK in the CDP user interface for
the following columns:
pitem_limit_count (for product-related content).
You can export both customer and product attributes through the same destination table. However, in that case, customer attributes are duplicated.
You can request Acquia to set the must-have attributes in your campaign as required fields in the destination table.
Sample use cases:
The following example explains the use cases for exporting customer attributes, product attributes, or both:
Only customer attributes: Export these attributes to enrich existing customer attributes on SFMC with CDP insights such as segments, ML models, and customer summary attributes. Examples of customer summary attributes are number of purchases and last time purchase date.
Only product attributes: Export these attributes to provide the list of recommended products, abandoned cart items, and browsed products. This table must include an email address field as the key column to link customers to the Data Extension table.
customer + product attributes: Export these attributes to have combination of the preceding use cases.
To set up SFMC, you must do the following:
Provide Acquia with an SFMC user interface user. This enables Acquia Support to connect to the connector for troubleshooting.
To create an API user:
Log in to the SFMC user interface, access the Admin section, click My Users > Create.
Specify the following details:
Name: Enter the CDP API user name.
Reply Email Address: Enter the CDP mailing list that was created
for your account. For example,
Notification Email Address: Enter the CDP mailing list that was
created for your account. For example,
Username: Enter a unique user name. Acquia recommends that you set
this value to be something unequivocal. For example,
API User: Select this checkbox.
Culture code: Select
Set the following user permissions:
Administrative data management
Grant the user access to the web services
Manage data extension data and retention policy
Set the following values for Marketing Cloud permissions and roles:
Applications for user:
Marketing Cloud roles for user:
Marketing Cloud Administrator
This API user must be able to retrieve data, extract data, create data extensions, and push data to data extensions.
After the user is created, share the details with Acquia.
To configure and schedule file extracts:
Click Journey Builder > Automation Studio. For more information, see Marketing Cloud Journeys and Automations.
Enter the following details:
Name: Enter the name of the data extract activity.
Description: Enter the description for the data extract activity.
File Naming Pattern: Specify the pattern for the file name. For
In Configuration, select the following options:
Extract Not Sent
Extract Send Jobs
Extract Survey Responses
Click Activities > Create Activity > File Transfer. For more information, see File Transfer.
Enter the following details:
Name: Enter the name of the file transfer activity.
File Action: Select Move a File From Safehouse.
In Configuration, specify the same name pattern in File Naming Pattern as you specified earlier.
Click Overview > New Automation.
In Workflow, drag and drop the data extract and file transfer activities created earlier.
Ensure that you select the activities that you created earlier, and do not create new data extract or file transfer activities.
Click Schedule and select the time when you want to trigger the automation process.
Repeat the process for daily incremental extracts.