Skip to main content
All CollectionsIntegrationsSalesforceEmail campaigns
Trigger an email campaign when contacts or leads are synchronised
Trigger an email campaign when contacts or leads are synchronised

Learn how to automatically trigger an email campaign when a contact or lead is synchronised from Salesforce to Dotdigital.

Gareth Burroughes avatar
Written by Gareth Burroughes
Updated over a week ago

When synchronising contacts or leads from Salesforce to Dotdigital, you might want to send a communication to your contacts as soon as they enter the Dotdigital list. For example, a welcome email, promotional email, or a message that’s time-sensitive. You can do this by setting up a campaign join action on the list.

Set up your campaign join action

A campaign join action will send a triggered campaign of your choice to any contact that is individually added to the list.

Campaign join actions are not triggered for bulk additions to a list, for example, a contact import through uploading a .csv file.

To set up a campaign join action:

  1. In Dotdigital, go to Audience > Lists.

  2. Find the list you want to add the join action for and select the Properties icon.


  3. For Campaign join action, select SELECT CAMPAIGN.


  4. Select the radio button for the triggered campaign you want to send.

  5. Select SAVE.

Enable the join action in Salesforce

  1. In Salesforce, go to Email Address Books and select the name of the address book corresponding to the list in Dotdigital.

  2. Select Advanced.


  3. On the Settings tab, select the Join trigger checkbox then select Save.


Understand the synchronisation process

The next time your email address book syncs from Salesforce, each contact within it is synced individually to the matching list in Dotdigital. This individual contact sync is necessary to allow the campaign join action email to be triggered to each email address in the sync.

Syncs and API allowance

As each email address in the email address book is synced individually into Dotdigital this will use the corresponding number of API calls, which may use a significant amount of your API allowance.

Learn more in the Rate limits section of our API documentation.

Did this answer your question?