Integrations
Salesforce Marketing Cloud - A platform that enables marketers to provide engaging and personalized customer experiences through automation of timely and relevant messages across e-mail, mobile and social at massive scale.
Email Studio allows you to:
Salesforce Marketing Cloud has limits around the lengths of attributes their platform can process:
Additional processing notes:
Tags - If you want tags to be sent to Salesforce Marketing Cloud, you must use the following minimum SDKs which added the details for processing changed attribute/tags.
Subscriber Key
Subscriber Key
configuration setting, which has not been provided, no data is sent to Salesforce Marketing Cloud.Subscriber Key
mapping, the MPID is assigned if the Subscriber Key
field can be mapped, otherwise, this falls back to the Email identity.Subscriber Key
field is used for all SFMC types going to Email identity.Subscriber Key
field used for all SFMC types going to defined identity.A special case is the subscribers.csv
file since this file doesn’t contain the Subscriber Key
field, therefore this still uses the Email field.
Data Refresh - Once you have entered all configuration settings, mParticle will obtain key information from Salesforce Marketing Cloud for sending data. You will need to refresh the integration by clicking Save on the Settings tab if you:
In order to enable mParticle’s integration with Salesforce Marketing Cloud, you will need a Salesforce Marketing Cloud account and an App Center account with Salesforce Marketing Cloud. Your account must be enabled for API Integrations. Create a Marketing Cloud App of type API Integration Application and save your Client ID and Secret.
If your Salesforce package uses OAuth2 authentication you must check the Enable OAuth2 Authentication box in the Configuration Settings. If your integrations package displays a banner like the one below, you are not using OAuth2 and should leave the box unchecked.
For Salesforce customers on version S11 or later — or on any version if using OAuth2 — you will need to know your Client Subdomain. This can be found on your Salesforce configuration page. The subdomain is part of your Authentication Base URI. For example if your Authentication Base URI is https://mc5jy4nwsrslmfnb4c274lnhns2m.auth.marketingcloudapis.com
, then your Client Subdomain is mc5jy4nwsrslmfnb4c274lnhns2m
.
The mParticle integration with Salesforce Marketing Cloud uses data extensions to store the data. You will also need to create the following data extensions to support the integration:
Event Mappings to External Keys
configuration setting.Below are references in the Salesforce Marketing Cloud documentation to assist with the creation of an API Integration app and the data extensions:
You can organize your data extensions within your Salesforce Marketing Cloud in any way that works for your organization. The following information contains a recommendation for the location and naming convention of the required data extensions. From Salesforce Marketing Cloud, follow these steps:
Follow these steps to create your subscriber data extension. mParticle requires that there is only one Primary Key in your subscriber data extension.
The value entered in the Subscribers Data Extension External Key
configuration setting, should be used as the field name in the Subscriber data extension, and in all event data extensions.
The following table describes the fields which you can add to the subscriber data extension for mParticle to send to Salesforce Marketing Cloud.
Name | Data Type | Nullable | Notes | |||
---|---|---|---|---|---|---|
SubscriberKey | Text | No | mParticle will send the user identity specified in the Subscriber Key configuration setting to this field. This must be set as the primary key. |
|||
TimeStamp | Date | Yes | mParticle will send a timestamp with every call to Salesforce Marketing Cloud. | |||
Email Address | Yes | If you want the Email attribute to be sent, add this field. | ||||
GUID | Text | Yes | If you want mParticle to generate a GUID to be sent, add this field. | |||
Age | Text | Yes | If you want the Age reserved attribute to be sent, add this field. | |||
Gender | Text | Yes | If you want the Gender reserved attribute to be sent, add this field. | |||
FirstName | Text | Yes | If you want the FirstName reserved attribute to be sent, add this field. | |||
LastName | Text | Yes | If you want the LastName reserved attribute to be sent, add this field. | |||
Address | Text | Yes | If you want the Address reserved attributes to be sent, add this field. | |||
City | Text | Yes | If you want the City reserved attribute to be sent, add this field. | |||
State | Text | Yes | If you want the State reserved attribute to be sent, add this field. | |||
Country | Text | Yes | If you want the Country reserved attribute to be sent, add this field. | |||
Zip | Text | Yes | If you want the Zip reserved attribute to be sent, add this field. | |||
Mobile | Phone | Yes | If you want the Mobile reserved attribute to be sent, add this field. | |||
User Attribute Name1-N | Text | Yes | Add fields for any user attributes that you send to mParticle that you want to be sent. | |||
Tag1-TagN | Boolean | Yes | Add fields for any user tags that you send to mParticle that you want to be sent. Tags are stored as boolean fields, where true indicates the presence of the tag, and false indicates the tag was removed. |
You will need to create a separate event data extension for each type of event you want to send to Salesforce Marketing Cloud. Multiple Primary Keys are supported in the event data extensions.
The following event types can be configured to be sent to Salesforce Marketing Cloud:
Commerce Events
A recommended naming convention for these data extensions is to use mP-Event. Some examples are listed below:
Follow the steps noted above in the Subscriber Data Extension Setup section for creating your event data extensions. mParticle suggests that you set the SubscriberKey and TimeStamp fields as the Primary Keys in your Event Data Extensions.
Every event data extension should contain the following fields:
Name | Data Type | Nullable | Notes |
---|---|---|---|
SubscriberKey | Text | No | mParticle will send the user identity specified in the Subscriber Key configuration setting to this field. |
TimeStamp | Date | Yes | mParticle will send a timestamp with every call to Salesforce Marketing Cloud. |
GUID | Text | Yes | If you want mParticle to generate a GUID to be sent, add this field. |
IDFA | Text | Yes | If you want the IDFA device id to be sent, add this field. |
IDFV | Text | Yes | If you want the IDFV device id to be sent, add this field. |
GAID | Text | Yes | If you want the Google Advertising ID device id to be sent, add this field. |
Android ID | Text | Yes | If you want the Android ID device id to be sent, add this field. |
Platform | Text | Yes | If you want Platform to be sent, add this field. |
OS Version | Text | Yes | If you want OS Version to be sent, add this field. |
Country | Text | Yes | If you want Country to be sent, add this field. |
Locale | Text | Yes | If you want Locale to be sent, add this field. |
Application Name | Text | Yes | If you want Application Name to be sent, add this field. |
Application Version | Text | Yes | If you want Application Version to be sent, add this field. |
Event Attribute Name 1-N | Text | Yes | Add fields for any event attributes that you send to mParticle that you want to send to Salesforce Marketing Cloud. |
You will need to create a separate data extension for each action that you want to send to Salesforce Marketing Cloud:
Name | Data Type | Primary Key | Nullable | Notes | |
---|---|---|---|---|---|
Checkout Step | Text | No | Yes | ||
Checkout Options | Text | No | Yes | ||
Product Action List | Text | No | Yes | ||
Product List Source | Text | No | Yes | ||
Transaction Id | Text | No | Yes | ||
Affiliation | Text | No | Yes | ||
Total Amount | Decimal | No | Yes | ||
Tax Amount | Decimal | No | Yes | ||
Shipping Amount | Decimal | No | Yes | ||
Coupon Code | Text | No | Yes | ||
Product Count | Number | No | Yes | If you want the Product Count to be sent to Salesforce Marketing Cloud, add this field. This indicates the number of products in the Product Action event when the action is Purchase or Refund . |
Additionally the following fields can be added to track product specific information:
Name | Data Type | Primary Key | Nullable | Notes | ||
---|---|---|---|---|---|---|
ID | Text | No | Yes | |||
Name | Text | No | Yes | |||
Brand | Text | No | Yes | |||
Category | Text | No | Yes | |||
Variant | Text | No | Yes | |||
Position | Number | No | Yes | |||
Price | Decimal | No | Yes | |||
Quantity | Decimal | No | Yes | |||
Coupon Code | Text | No | Yes | |||
Add To Cart Timestamp | Date | No | Yes | |||
Total Product Amount | Decimal | No | Yes | |||
Product Attribute Name 1-N | Text | No | Yes | Add fields for any product attributes that you send to mParticle that you want send to Salesforce Marketing Cloud. |
Name | Data Type | Primary Key | Nullable | |||
---|---|---|---|---|---|---|
Product Impression List | Text | No | Yes |
The Product specific fields are listed above should be added to the Impression data extension.
Name | Data Type | Primary Key | Nullable | |||
---|---|---|---|---|---|---|
Action Type | Text | No | Yes | |||
ID | Text | No | Yes | |||
Name | Text | No | Yes | |||
Creative | Text | No | Yes | |||
Position | Text | No | Yes |
Name | Data Type | Primary Key | Nullable | |||
---|---|---|---|---|---|---|
Event Name | Text | No | Yes |
Name | Data Type | Primary Key | Nullable | |||
---|---|---|---|---|---|---|
Screen Name | Text | No | Yes |
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
Client ID | string |
Your Client ID from Salesforce Marketing Cloud App Center | |
Client Secret | string |
Your Client Secret from Salesforce Marketing Cloud App Center | |
Client Subdomain | string |
The subdomain of your Authentication Base URI in Salesforce. For example if your Authentication Base URI is https://mc5jy4nwsrslmfnb4c274lnhns2m.auth.marketingcloudapis.com , then your Client Subdomain is mc5jy4nwsrslmfnb4c274lnhns2m . |
|
Enable OAuth2 Authentication | bool |
false |
Set to true if your package uses OAuth2 authentication. |
Setting Name | Data Type | Default Value | Platform | Description |
---|---|---|---|---|
Subscriber Key | string |
customerId | All | Subscriber Key |
Subscribers Data Extension External Key | string |
All | External Key of the Data Extension used to store Subscribers | |
Event Mappings to External Keys | Custom Field |
All | Define the mapping of mParticle event names to the corresponding Salesforce Marketing Cloud Data Extension External Keys |
Was this page helpful?