Technical Guide

This page contains technical information for experienced Salesforce administrators who are looking for a deeper explanation of the key jobs.

API usage

Salesforce imposes strict governor limits on API usage, which can impact various operations. However, it's important to note how these limits apply when syncing with Mailchimp:

Types of API Calls:
Salesforce categorizes API calls as either inbound or outbound:
Inbound API Calls: These are calls made to Salesforce from an external system.
Outbound API Calls: These are calls made from Salesforce to an external system.

Impact on Governor Limits:
Outbound Calls:
Crucially, outbound calls from Salesforce do not count against the governor limits. This is significant when syncing with Mailchimp.
Inbound Calls: Only these calls count against your Salesforce API limits.

Syncing with Mailchimp:
All syncing operations to and from Mailchimp are performed using outbound calls. For example, sending 100,000 emails to Mailchimp through various syncing methods (like subscriber rules, import wizard, list views, etc.) will not impact your Salesforce API limits. The only scenarios where inbound API calls are used, and thus count against your limits, are:
a) When using a Salesforce list view for bulk operations, such as adding contacts to a subscriber list. This will consume just 1 inbound API call.
b) When navigating to the sync settings page, which also uses up just 1 inbound API call.

In general, you should not need to worry about the Mailchimp application using up your inbound API limits.

Custom Objects

When the installation has been completed, the Salesforce objects below will be created in your Salesforce Org. These objects contain either records or settings required for our application to work. Our product has been designed to be self-contained, not to impact standard objects.

  • Mailchimp Account
  • Mailchimp Campaigns
  • Mailchimp Email Activity
  • Mailchimp Group
  • Mailchimp Group Category
  • Mailchimp Import
  • Mailchimp List
  • Mailchimp List History
  • Mailchimp Member

Our object structure should not be customized as it may stop our application from working correctly or stop automated upgrades.

Background jobs

The list below are the batch jobs that can run in the background within Salesforce.


Pulls in email history from Campaign Monitor into Salesforce. The records are stored in email tracking history (wbsendit__Campaign_Activity__c). This table may contain a large number of rows. See: Storage. This job runs as part of the primary sync between Salesforce and Campaign Monitor.


You can install our integration in one or more sandboxes. You can also refresh a sandbox and our application will be copied across below is some more detailed information.

How to install in a sandbox

  1. Go to our Salesforce AppExchange listing.

  2. Click the Get it now button.

  3. If you are not already logged in you will be prompted to do so.

  4. Choose Sandbox.

  5. Select I have read and agree to the terms and conditions, then click Confirm and Install.

  6. Choose whether to install for admins only, all users or specific profiles.  We recommend you select Admins only and once installed give users access via our permission sets.

  7. Click Install.

  8. Select Yes, grant access to these third-party websites then click Continue.

Sandbox refresh

When you start a sandbox refresh a copy of your installed applications will also be copied. This will include Campaign Monitor for Salesforce and there are some important points below to consider.

  • We do not recommend you connect any sandbox to your live Mailchimp account.
  • When a sandbox refresh happens we use a standard Salesforce process to disconnect Mailchimp from Salesforce.
  • You can also manually run a process before or after the sandbox refresh to clear out connection settings.
  • When performing a refresh, whether for a full or partial sandbox, data from our objects can be copied from the production environment.

We don't recommend connecting a sandbox to your live Campaign Monitor account. Changes made in a sandbox can incorrectly update your Campaign Monitor data.

Sandbox conflicts

As mentioned above when refreshing a Salesforce sandbox, there may be some settings carried across from production. It is worth noting we do have some code that runs as part of the refresh to avoid this.  But in very rare scenarios, the code can be conflicted with. So to help we have two options to return settings to their default state.

Before starting the sandbox refresh
When refreshing the Salesforce sandbox, there is now an option to run a post-installation script. You can enter the value McSandboxPostCopy this will execute our code to clear out the settings. Ater performing these steps you will need to connect to M

How to test in a sandbox

When you have our product in a sandbox we recommend connecting it to a test Mailchimp account. The best way to setup a test account is to create a new Mailchimp account that is pay-as-you-go. This will allow you to test features in a dedicated account.

In this article