Salesforce Marketing Cloud

The Salesforce Marketing Cloud integration is available on the Enterprise plan.

Radar can send events to Salesforce Marketing Cloud to trigger journeys in Journey Builder.

Use the Salesforce Marketing Cloud integration to send location-triggered messages to increase engagement and conversion.

Configuration#

On the Salesforce Marketing Cloud Setup menu, under Installed Packages, click New. Add an installed package with the name Radar. On the package details page, add an API Integration component with the Server-to-Server integration type and all permissions for the Automation, Contacts, Cross Cloud Platform, and Data scopes. Copy your Client ID, Client Secret, Authentication Base URI, and REST Base URI.

Then, on the Radar Integrations page under Salesforce Marketing Cloud, set Enabled to Yes and paste these values. When you click Save, Radar will create an event definition and data extension with the specified event definition key (radar-event by default). Whenever events are generated, Radar will send events to your Salesforce Marketing Cloud data extension to trigger journeys.

In Salesforce Marketing Cloud's Contact Builder, under Data Designer, connect the Radar data extension to your data model by linking the Customer Data's Contact Key field to the Radar Data Extension's contactKey field in a one to many relationship.

To map a Radar user to a Salesforce Marketing Cloud contact, you must specify a custom mapping by setting Radar metadata.salesforceContactKey.

Swift
Kotlin

let contactKey = SFMCSdk.mp.contactKey()Radar.setMetadata(["salesforceContactKey": contactKey])

SFMCSdk.requestSdk { sdk ->    sdk.mp {        val contactKey = it.moduleIdentity.profileId        Radar.setMetadata(JSONObject().put("salesforceContactKey",contactKey))    }}

Verify integration data delivery#

To test that the integration is configured correctly and can deliver data, use the Simulator to generate events. Click View on an event row and scroll down to the Logs section on the details page to verify delivery. Perform a similar process via a test app build with Radar location tracking enabled by spoofing location or moving into the relevant boundary.

Verify integration event delivery

Additionally, check the Radar data extension in Salesforce's Contact Builder to verify records are delivering.

All integration delivery can be monitored via the integration's event logs by clicking View event logs on the Integrations page.

Example use cases#

Send a personalized push notification when a user arrives at a store#

Create Geofences in Radar with the geofence tag set to store. The geofence tag will be used to trigger messages for the subset of geofence entries where this tag is present.
Create a Salesforce Journey triggered by an API Event from the Radar data extension. The Radar data extension will be filtered on user.entered_geofence as the type attribute and store as the geofenceTag attribute.

Radar triggered Salesforce campaign

Message all users who have been nearby a store#

Create Geofences in Radar to represent nearby store boundaries with geofence tag set to nearby-store. The geofence tag will be used to target messages for the subset of geofences where this tag has been present on an event in the last 7 days.
Create a Salesforce Mobile List filtered on the Radar data extension attributes of type equal to user.entered_geofence, geofenceTag equal to nearby and createdAt set to the last 7 days.
Create a Salesforce MobilePush Message with audience targeting set to the Salesforce Mobile List created in the step above.

Radar targeted Salesforce campaign