Salesforce Marketing Cloud
Salesforce Marketing Cloud is a cloud computing and social enterprise customer relationship management (CRM) system. Manage bulk data exports between Swrve and Salesforce and enhance the Marketing Cloud user journey with Swrve’s mobile behavioral data insights with Swrve’s Marketing Cloud integration.Supported actions
Swrve’s Salesforce Marketing Cloud integration supports the following actions:
- Create a batch CSV file of Swrve user properties and export it to Salesforce
- Use Swrve events to trigger Marketing Cloud journeys
- Update users’ contact profile in real time
- Create new contact records in Marketing Cloud
- Send transactional email
- Subscribe or unsubscribe a user from a list
Use cases
Export bulk data from Swrve
The Swrve bulk data export service passes data from Swrve to Marketing Cloud, enabling you to include mobile behavioral data to create richer user profiles in Marketing Cloud. Segment mobile users based on their actions or any user attributes in Swrve. Set up workflows to send a daily bulk export of user properties from Swrve to Marketing Cloud.
Omni-channel campaigns
Trigger Swrve user engagement campaigns from Salesforce interactions or marketing journeys. Build lifecycle marketing journeys in Salesforce that trigger campaigns in Swrve. For example, send a push notification to users who do not open marketing emails or initiate a campaign to bring the user back into the app after abandoning items in their shopping cart.
Update user profile
Use the actions a user completes (or doesn’t complete) within the app to update their user profile in Marketing Cloud in real time.
Marketing Cloud configuration
In most instances, your CSM will set up your Marketing Cloud configuration, however you might need to provide them with certain credentials. To view your active Swrve integrations, on the Manage menu, select Adaptors.
Step 1: To access the configuration settings, on the Salesforce Marketing Cloud card, select Configure.
Step 2: Complete the following fields as required:
| Field | Description |
|---|---|
| Client Id | First part of the App Key pair that Salesforce App Center generates when you create an app. Required for transactional data export. |
| Client Secret | Second part of the App Key pair that Salesforce App Center generates when you create an app. Required for transactional data export. |
| Authentication Base URI | The Authentication Base URI listed under your Salesforce API Integration Component. This is not required for legacy applications (pre-OAuth 2.0). |
| FTP Location | The FTP location where you want to upload the contact CSV file to. Required only for the Upload CSV action. |
| FTP File Path | The FTP file path where the contact CSV file will be located. Required only for the Upload CSV action. |
| FTP Username | Username credentials for the FTP site. Required only for the Upload CSV action. |
| FTP Password | Password credentials for the FTP site. Required only for the Upload CSV action. |
| Username | Username credentials for an account that has access to Salesforce Marketing Cloud Email. Required only for Email Campaign metrics. |
| Password | Password credentials for an account that has access to Salesforce Marketing Cloud Email. Required only for Email Campaign metrics. |
Salesforce App Center generates the Client ID and Secret when you initially create the application in the App Center. You also need to create a server-to-server API integration after installation.
Step 3: To save the configuration settings, select Save.
After you select Save, the configuration status changes to Active and the Deactivate button is available. If you Activate or Deactivate the integration at any time, the changes apply to both the outbound and inbound actions.
Marketing Cloud actions
This section describes the fields that are included when creating a new rule using the selected action. For certain inbound actions, Swrve automatically creates a rule, while your CSM will likely configure any outbound actions. Most fields have the option to manually enter the value or to select a user property from the list to have Swrve automatically populate the value when the rule is processed.
Create contact
Create a new user record in Marketing Cloud with the specified information in the set attribute groups.
| Field | Description |
|---|---|
| Contact Key | The unique identifier for the contact. |
| Attribute Sets Name | Name of the attribute group in Salesforce Contact Builder to which to add the contact information. |
| Attributes Sets Values | Name and value pairs indicating the attribute and applicable value. |
Send transactional email
Send a transactional email using Marketing Cloud’s triggered send functionality. In order to use this service, you must configure an entry event send definition in Salesforce Email Studio.
| Field | Description |
|---|---|
| Template ID | The name of the Triggered Send definition. |
| To Address | The recipient’s email address. |
| Subscriber Attributes | Optional subscriber parameters passed in at send time. |
| Subscriber Key | The Salesforce Marketing Cloud identifier for a specific user. |
Subscribe / unsubscribe user
Subscribe or unsubscribe a user from a list.
| Field | Description |
|---|---|
| List ID | Name of the recipient list that the entry will be added to or removed from. |
| Subscriber Key | The Salesforce Marketing Cloud identifier for a specific user. |
| Email Address | The subscriber’s email address. |
Trigger interaction
Trigger a Journey Builder campaign from an event in Swrve (for example, shopping cart abandonment).
| Field | Description |
|---|---|
| Interaction To Trigger | The Journey Builder Entry Source or campaign that you want the event to trigger. You must first create the Entry Source or campaign in Journey Builder for it to be available in the list of interactions. |
| Contact Key | The unique ID that identifies the user in Salesforce and Swrve. |
| Establish Contact Key | If set to true, the Contact Key is automatically added to the contact model if it isn’t already included, making it available to be injected into the Interaction. |
| Event Attributes | Properties of the Entry Event’s Data Extension; only required if the Data Extension has required Attributes or a Primary Key. |
Update contact profile
Update a user’s Contact Profile in the Marketing Cloud Data Extension with a set attribute in real time. To use this action in a Data Extension, you must define the Primary Key.
| Field | Description |
|---|---|
| CustomObjectID | The CustomObjectID found in the URL of the relevant Data Extension. For example, if you right-click a Data Extension name link in Marketing Cloud and select Copy Link Address or Inspect, the following highlighted text indicates the CustomObjectID: #admin/data-extension/a1234567-bc8d-e901-f23g-45hij6789k01/properties/ |
| Attributes Primary Key | Key/value pair of the Data Extension’s Primary Key. The Attributes Primary Key is used to match the user’s profile and is defined in the Data Extension. |
| Attributes | The name and value of the attributes in the Data Extension that you want to update. |
| Trigger Interaction | If set, the Update User Property will also trigger a Journey Builder event. |
| Interaction To Trigger | The Journey Builder Entry Source or campaign you want to trigger. You must first create the Entry Source or campaign in Journey Builder for it to be available in the list of interactions. |
| Establish Contact Key | If set to true, the Contact Key is automatically added to the contact model if it isn’t already included, making it available to be injected into the Interaction. |
| Event Attributes | If the Interaction is connected to a different Data Extension, add any attributes that are being used that are not in the initial Data Extension. |
Upload CSV
Creates a CSV file of selected user properties and exports the file from Swrve to the FTP server specified in the connector configuration settings.
| Field | Description |
|---|---|
| CSV Schema | Key-value mapping for the CSV headers and row values. |
| File Identifier | A value to include as an identifier when Swrve generates the file name, in the format yyyy-mm-dd-HH-MM-SS-{identifier}.csv. If you do not include a File Identifier, the default file name is yyyy-mm-dd-HH-MM-SS-Amplify-Data-{App_ID}.csv. |
| Output File Timezone | By default, output files are prefixed with a timestamp in UTC. Select a different timezone if required. |
| Scheduling Options | Sets the conditions at which the accumulated user data is flushed to a CSV file and sent to the FTP server. |