Setting up your campaign sync to Salesforce

Mutiny can write your experience data back to Salesforce to enable more robust reporting. Before going through this article, be sure that you've set up your Salesforce integration. You'll also need to be sure that Mutiny is able to identify your users, otherwise, we won't be able to write their data back to Salesforce. Learn more about identification here.

Configuring the campaign sync

When enabled, Mutiny will sync experience impression data to Salesforce using campaigns and campaign members. Mutiny will create a new campaign for each Mutiny experience you sync and then add campaign members based on who has seen that experience. Follow the steps below to configure your campaign sync settings.

1. First, you'll want to decide which experiences will be synced to Salesforce. For each experience selected, Mutiny will create a new campaign in Salesforce. Select your experiences under the "Website Experience Settings" dropdown. By default, all active experiences are set to sync with Salesforce.
2. Next, you'll want to define the values for campaign fields for the campaigns that Mutiny creates for website experiences. Any changes will apply to existing and future campaigns. You can set these values by clicking "Set Values" under the Website Experience Settings dropdown. You'll then have the option to set the value for any campaign fields you want. Any required campaign fields will need to be filled out here.
3. Next, you'll want to map Mutiny impression types to your campaign member statuses. You can learn more about Salesforce campaign member statuses here.
4. For customers with access to legacy outbound functionality, you'll want to configure all of the same settings for your outbound campaigns under the "Outbound campaign settings" dropdown.

Turning on the integration

Once you've configured all of the settings above, you'll want to confirm your reporting state and turn on the integration. You can do this under the "Reporting State" dropdown. If all items have a green check mark, switch the integration toggle to "On". If all fields aren't green, revisit the configuration items above to ensure you've completed all the steps.

By default, all data will sync every 24 hours. If you'd like to trigger a sync manually, you can do so by clicking the "Sync Now" button.

Viewing the data in Salesforce

Once you've fully configured your campaign sync, you'll be able to view your Mutiny experience data in Salesforce.

Salesforce Campaign

Each Mutiny-created Salesforce campaign represents a distinct experience in Mutiny. To view your Mutiny data in the campaign detail views, be sure to add your Mutiny custom fields to the page layout.

For each campaign, you can expect the following information

Standard Campaign Fields

• Campaign Name: Mutiny Experience [Mutiny Experience Name] for [Segment Name]

Custom Campaign Fields

• Mutiny Experience Name: The name of the Mutiny experience
• Mutiny Segment Name: The name of the Mutiny segment targeted in the experience
• Mutiny Experience Page: The page the Mutiny experience is running on
• Mutiny Experience URL: A link to the experience in Mutiny
• Other: Mutiny will set any fields according to the mapping you configured above

Salesforce Campaign Members

Each Campaign Member in a Mutiny Salesforce Campaign represents a Lead or Contact that saw the Mutiny experience.

Custom Campaign Member Fields

• Mutiny Variation Name: The name of the specific variation of the experience the visitor saw
• Mutiny Personalized Impression Count: The total number of times a visitor has seen a personalized version of the experience
• Mutiny Control Impression Count: The total number of times a visitor has seen the control version of the experience
• Mutiny Total Impression Count: The total number of times a visitor has seen the experience.
• Mutiny First Personalized Impression Date: The date that a visitor first saw a personalized version of the experience
• Mutiny Last Personalized Impression Date: The date that a visitor last saw a personalized version of the experience
• Mutiny Converted: TRUE/FALSE representing if the visitor performed a conversion event set as the goal of the experience
• Mutiny Conversions: A comma-separated list of conversion events performed by the visitor

Next Steps

Now that your integration is up and running, head on over to this article to see how you can pull this data into some of your reports.