Skip to main content
All Collections3rd-party integrationsMarketing Platforms
What can you do with our SFMC (Salesforce Marketing Cloud) connector?
What can you do with our SFMC (Salesforce Marketing Cloud) connector?

With our brand new connector, you can run complex push automation scenarios from the famous Salesforce Journey Builder.

Laurent Canestrier avatar
Written by Laurent Canestrier
Updated over a week ago

Salesforce Marketing Cloud is an extensive marketing suite that allows marketers to create complex omnichannel journeys that are more tailor-made and more interesting for the end user. 

💡 In case you missed it, we just released a connector with them.

Get in touch with us to set up this integration.

Looks great. How do I use it?

Once the integration has been set up on your account, you should see a new Batch Custom Activity in your Journey Builder, start by adding it to your Journey and click on it!

> Choose between an existing template and a new campaign

We let you either use Batch's interface or Salesforce's to create your campaign content. If you feel comfortable with Batch dashboard and feature, you can create a campaign there with Mobile Landings, personalization and previsualization, and save it as a draft.

Otherwise, you can choose "New campaign" to create new campaign content from scratch.

Option A : Template

> First step, adding the Campaign Name and Apps

Input a unique campaign name for this push notification and choose on which would you like to send a push notification to.

> Second step, choosing templates

If you've chosen the Template option on the second step, you will be asked now to choose for each app which draft campaign you wanna use for your push notification on Salesforce.

Note that it is also possible to override the draft content with new values if you choose the option in the bottom bar. Switching it on will bring you to the fourth step. Otherwise, you are done!

Option B : New Template

> First step, adding the Campaign Name, Apps and optionnal features

Input a campaign name for this push notification and choose on which would you like to send a push notification to.

You can also add opptional features such as :

  • Mobile landing

  • Capping

  • Payload

> Second step, creating new campaign content

You are now prompted to write campaign content for your push notification. If a template was chosen in Step 3, these new values will override the template values.

Note that the image URL should be secured.

You can easily add other languages to your message using the "Add language..." module :

  • Mobile landing :

Mobile Landings allow you to easily introduce continuity between your app, and your pushes: A user opening a push will be greeted by a rich message related to what they opened, rather than just ending up on your app's main menu.

You can now manage them in the data activity:

  • Capping :

Use the "Labels" field to implement capping define in your Batch dashboard and regulate your marketing pressure, ensuring your audience isn't overwhelmed with messages.

  • Payload :

It's an optional JSON string that can contain additional parameters that your application can handle when receiving push notifications if configured to do so.

> Third step, preview and test your push

You can easily preview your pushes or send you a push of tests on your different platforms and in the languages defined in the previous section.

Nice, but how do I run automated scenarios based on push reactions?

How to do it 

Create a new Decision Split, and use the campaign ID below the Batch tile, and use it as a group-id to refer to a specific notification in your request. 

If you want to target users that received the push notification, add a   event: sent  request. If you want to target users that opened the push notification, add a   event: open  request as shown below :

A few technical details ...

Every day, Batch will fill a Data Extension called BATCH_PUSH with reaction events, so the day following the sending of the push notification, we will provide you with data concerning each push that has been sent.

In this database, the push is referred to by their group-id, which is a slug of the campaign name you've chosen (= a campaign ID). Note that this slug is available as the push tile name:

In the BATCH_PUSH data extension, this data is available as the group-id. Use it to retrieve information on the state of a push of a certain user such as demonstrated below:

There are four states in which a push can be, those states are represented by the event attribute :

  • accepted: the push request has been accepted by Batch and will be processed asap.

  • sent: the push notification has been sent to the user.

  • open: the push notification has been opened by the user

  • error: the push notification encountered an error (device unreachable in most cases).

This article belongs to Batch's FAQ. Need more help? Find insightful articles, documentation, case & market studies, guides, and even more in our website's Resources section on and our blog.

Did this answer your question?