On the platform, it is possible to define a specific configuration for the import and/or update of campaigns managed on Salesforce.
In the context bar Salesforce Configuration, you need to access the CRM Campaigns page.
The Salesforce Campaign Configuration concerns the activities of importing campaigns from Salesforce to the magnews platform and exporting communications from the platform to Salesforce campaigns:
Setup: mapping Salesforce custom fields on the platform
Still on the Salesforce Campaign Configuration page, in the Setup section, it is necessary to map the Salesforce fields on the platform, as per the example:
Below is the list of all the custom fields necessary for the correct functioning of the Salesforce Connector
| Entity | Field | Datatype | UI visibility | Recommended name | Required |
|---|---|---|---|---|---|
| Campaign | Magnews unique ID: field generated and managed by the Salesforce connector | string | no | MN_UniqueID | yes |
| Campaign | Magnews campaign info: JSON data structure used to restore the connector in case of a reset by magnews | string | no | MN_TechnicalInfo | yes |
| CampaignMember | Contact responses: type to which the most significant event of the contact belongs | Picklist Not Sent Sent Bounced Opened Clicked Converted Complained Unsubscribed |
yes | MN_Response | yes |
| CampaignMember | Channel (email or SMS) of the event generated by the contact in the communication | String | yes | MN_Channel | no |
| Contact/Lead/Account | Flag for Import Failed | Boolean | - | MN_ImportFailed | no |
| Contact/Lead/Account | Timestamp of the last import attempt | Date/Time | - | MN_LastImport | no |
| Contact/Lead/Account | Debug message of a failed import | String | - | MN_ImportErrors | no |
For more information regarding the preliminary CRM-side configuration, please refer to the Installation Prerequisites section of this documentation.
Campaigns imported from Salesforce to the platform
To activate the synchronization of campaign activities from Salesforce, it is necessary to enable the option:
On Salesforce, there are various types of campaigns, and the document Platform-SalesforceConnector_prerequisites indicates how to add the platform to the list of campaign types. It is recommended to ensure that the magnews campaign type is correctly created in the Salesforce configuration and to select this value as Salesforce Campaign Type as shown below:
On the platform, it is possible to create a journey (it is reminded that on the platform, the journey is a "container" of communications) dedicated to Salesforce and set it as the default for the creation of communications linked to the journey, imported from Salesforce.
Depending on the configuration of the platform user permissions (see user profiles) and the tasks they must perform to create communications, it is possible to allow or disallow the selection of a journey different from the default set one (see above) during the creation of a new communication:
During the synchronization phase of a communication’s target, if the following contact profile update option is enabled, all target contacts will be updated in real-time:
Return statistics for campaigns imported from Salesforce
The performance results (e.g., opens, clicks, bounces, etc.) of communications sent from the platform can be reported on the campaign members present in Salesforce:
On the platform, it is necessary to configure the event (open, click, or conversion) that corresponds to the “Response” status of the Salesforce campaign member. For example, the “Response” status for a Salesforce campaign is considered for those who record at least one click on the related platform communication:
An automatic synchronization of results from the platform to Salesforce can be defined. It is recommended to set it to 15 or 21 days to obtain a complete result and manually synchronize the responses to see the initial results in Salesforce:
Example of configuring Salesforce tasks:
Campaigns exported from the platform to Salesforce
To activate the creation of Salesforce campaigns starting from platform communications, it is necessary to enable the option:
which allows exporting communications from any journey or a specified one:
Similarly to import, it is necessary to define into which type of Salesforce campaign to export the platform communications:
The following options allow filtering the creation of Salesforce campaign members based on the most significant event recorded by the contact for each specific communication:
On the platform, it is necessary to configure the event (open, click, or conversion) that corresponds to the response status of a Salesforce campaign member.
For example, the "Response" status to a Salesforce campaign is considered for those who record at least one click on the related platform communication: