Salesforce Marketing Cloud – User Guide


This historical connector is key for us to extend Salesforce Marketing Cloud mobile engagement capabilities thanks to GROW. As Marketing Cloud helps build cross-channels journeys, GROW will enhance:

  • Messaging capabilities in Journey Builder as GROW push and in-app formats will be available through a Bryj activity.
  • Data collection as GROW will be able to send the data collected on the mobile apps to Marketing Cloud. Such capabilities will improve user journeys based on Usage or previous Campaign behavioral data.

Check more on Salesforce Marketing Cloud in their official documentation. The rest of this Article will focus on the GROW 2.0 x Marketing Cloud Connector provided by Bryj. The following will be covered:

  • Pre-requisites to enable the connector
  • Integration guidelines to enable the connector (15min)
  • Messaging through Bryj activity
  • Data Extension creation to make GROW data come up in Marketing Cloud
  • Troubleshooting section in case any issue is encountered while using our connector!


The use of our Salesforce Marketing Cloud Connector has a few requirements:

  • Your CSM needs to activate the connector in your Service Plan. Upon activation, a Key will be communicated to you which is required for integration.
  • Your apps needs to have the GROW solution embedded so it collected the Salesforce Contact ID as a User Identifier.

If the apps are unable to collect the Salesforce Contact ID, the connector will be useless as it will not be able to map GROW Data with Marketing Cloud Data.


Find below some easy steps to configure a Bryj activity! This will enable GROW push and in-app notifications in your journeys.

Configure a message

To configure your Message, first go in Journey Builder either a new journey or one of your existing journeys.

Then locate the Bryj activity. It must look like this:

Drag and drop the activity in your journey, it will appear with a grey background. It means that the Bryj Activity is not yet configured!

Click on your activity to start your configuration.

You might be asked to enter GROW credentials at this step. This is to ensure the proper level of access and improve the connector security.

Then let’s proceed with the activity setup! This can be summed up in 5 steps.

Step 1: Select your project

Select the project containing the apps you would like to target in this activity.

Step 2: Select or create your campaign

Select the campaign you would like to use. The targeted apps (All live apps or a Single app) will be determined based on the Campaign’s Audience

Draft campaigns are listed, though they cannot be selected to go to the next step until they launch. If you need to use a draft: go on the draft and launch it to enable selection in the activity.

If a new campaign needs to be configured, click on the New Campaign CTA at the top right. This will display the same campaign editor as the one available in GROW.

More information on the campaign editor in the GROW User guides, only Manual campaigns can be created through the Bryj activity as it’s an API-based campaign leveraged by Journey Builder (Marketing Cloud is handling the API tech-savvy part seamlessly for you!).

Step 3: Map your message variables with Marketing Cloud Data Extension fields

Once your campaign is picked, if some variables are set you will need to map them to valid inputs in Marketing Cloud. This will be represented by a table listing all the variables you set in your campaign and some columns to define in which DE the data should be collected and which field to leverage.

In the example below, the Order confirmation campaign has 2 variables: name and orderid which I map to Data extension fields.

When using variables, to ensure the reception of a meaningful message. The notification will not be delivered to a targeted contact if the matching Data Extension fields are empty.
If you still would like the notification to be delivered, you will be required to fill in a default value to replace the missing variable. In the example above, you would replace the contact’s name in the message

Most of the time you will not need to edit the Data Extension primary keys suggested. The connector will rely on this table to map variables with Marketing Cloud Contact IDs. If the primary key field automatically suggested does not match a Contact ID, you will need to correct it prior to going to the next step.

Step 4: Refine your delivery options for better marketing pressure handling

You can handle marketing pressure for your Contact using several devices (professional & personal phones, tablets), you can choose if you would like to fire the message to all devices associated with the Contact or only to the latest device used by the Contact.

Step 5: Review your configuration prior activation

A summary page will show so that you can review your setup. Click on Done at the bottom right to save your configuration.

Now your activity is configured!

Edit a message

You can double-check your setup by clicking on a configured activity.

If you need to edit your setup, just go on the configured activity, and go back to the step you would like to edit. That’s it!

Similarly, to other activities, once a journey is launched the activity cannot be edited anymore! You will have to edit your journey to be able to edit the activity again!

Data Extensions


Data extensions are used to sync GROW data to Marketing Cloud. Their configuration will occur in the App Exchange in the Bryj connector’s interface.

Configure a Data Extension

To configure a Data Extension, click on Create DE (Data Extension).

Step 1 – General

Provide some General information on your DE such as its name, where the DE should be created, and which GROW project & apps should be used to populate the DE.

If you have an iOS and Android live apps, no need to create 2 separate DEs! Just select All live apps in the App field as shown in the example above and you will be all set.

If you have an iOS and Android live apps, no need to create 2 separate DEs! Just select All live apps in the App field as shown in the example above and you will be all set.

Step 2 Data source configuration

Select which type of data you would like to export. The connector will provide 3 types of data sources:

  • Usage – Device technical activity such as its language setup, the device model, when was the app last used, is the app still installed…
  • Attributes – Linked to the User profile data collected by GROW. Useful if some attributes are collected in Marketing Cloud already such as app-specific configuration (ApplePayConfigured…)
  • Campaigns – GROW campaign-related stats such as push sent, push opened, in-app displayed, button clicked, goal reached… This will be useful to execute journeys based on this data!

Select all the fields you need for you DE before clicking on next and move on to the 3rd step!

Step 3 Review & Create

Check the summary of your setup and click on Create if everything looks good!

Watch your DE appear in the list.

The data may take a while to populate upon creation. Do not worry if the Last updated field is still empty after a few hours. Come back the next day to witness your data.

Data sync checks

Your Data Extensions are configured to be refreshed once per day by default.

If needed, you can check when your Data Extension was last updated from the GROW Data Extensions list available in our connector entry in the App Exchange. Just look at the “Last updated at” field!