Salesforce Marketing Cloud - MobilePush provides businesses with a platform for targeting and delivering push notifications to the right audience. This integration is limited to customers who have been approved by Salesforce.
MobilePush allows you to create and send push messages to mobile application users. You can use MobilePush to accomplish the following tasks:
Salesforce Marketing Cloud has limits around the lengths of attributes their platform can process:
In order to enable mParticle’s integration with Salesforce Marketing Cloud, you will need to a Salesforce Marketing Cloud account and an App Center account with Salesforce Marketing Cloud enabled for MobilePush, and have created a MobilePush Application Type app to obtain your credentials (Application ID and Access Token) for mParticle configuration.
Below are references in the Salesforce Marketing Cloud documentation to assist with the creation of a MobilePush application:
Any user attributes or tags that your app is sending to mParticle will be forwarded to Salesforce Marketing Cloud. There is no setup for tags, but in order for attributes to be processed by Salesforce Marketing Cloud, you will need to configure these attributes in Salesforce Marketing Cloud.
Repeat steps 4 and 5 to add all user attributes you want to be processed by Salesforce Marketing Cloud.
The following mParticle reserved attributes already exist in the MobilePush Demographics table and therefore do not need to be created. They will be sent if available:
If you want any of the other mParticle reserved attributes to be sent, you’ll need to add them as attributes following the steps above using the following Attribute Names:
|Setting Name||Data Type||Default Value||Description|
||This is the unique identifier for an application from the Marketing Cloud App Center. It is one half of the AppId/AccessToken pair. This is always in the form of a v4 UUID.|
||An Access Token corresponds to an Application ID. It functions almost as if it were a unique password for the corresponding Application ID|
|Setting Name||Data Type||Default Value||Platform||Description|
|GCM Sender ID||
||Android||The GCM Sender ID from the Google Developers Console Project Number configuration.|
||customerId||All||Subscriber Key is used to aggregate devices under a single user and to coordinate cross-channel messaging activity.|
Was this page helpful?