Articles on: Integrations

Salesforce Integration Setup

Salesforce Integration Setup


Purpose


Connect your Salesforce org to SuperSend so campaign activity — email sent, opens, and replies — appears on the matching Contact in Salesforce. This guide covers the one-time Salesforce package install and the OAuth connection in SuperSend.


SuperSend does not use a separate middleware app for this integration. You install the SuperSend Integration package in Salesforce, then authorize SuperSend from the Admin area.


How the Salesforce Integration Works


When a contact in SuperSend matches a Salesforce Contact by email address:


  • Email sent — logged on the Contact (as an email message or task, depending on your org)
  • Email opened — logged when opens sync is enabled
  • Email replied — logged when a reply is received


SuperSend does not create new Salesforce Contacts automatically. Events only sync when a Contact with the same email already exists in Salesforce.


Prerequisites


  • SuperSend: Org admin access (Admin Settings → Integrations).
  • Salesforce: A user who can install packages (typically a Salesforce admin). Install is done once per Salesforce org.
  • Salesforce org type: Use the production install link if you sign in at login.salesforce.com. Use the sandbox install link if you sign in at test.salesforce.com.
  • Browser: Allow popups for SuperSend when you click Connect To Salesforce (OAuth opens in a popup).


Step 1: Connect Salesforce at the Team Level


  1. Go to Admin Settings → open the Integrations tab (URL includes tab=integrations).
  2. Select your team from the team dropdown at the top.
  3. On Integration Library, find Salesforce in the list.
  4. Click Add.
  5. Complete Step 1 — Install SuperSend in Salesforce in the panel:
  • Click Open Install (Production) or Open Install (Sandbox). Salesforce opens in a new tab.
  • Sign in as a Salesforce admin and follow the install prompts. Install for All Users unless your admin restricts access.
  • In Salesforce, confirm Setup → Installed Packages lists SuperSend Integration (or your package display name).
  • Back in SuperSend, check Package is installed in my Salesforce org.
  • Optional: use Copy production link or Copy sandbox link to send the install URL to your Salesforce admin if someone else performs the install.
  1. Complete Step 2 — Authorize SuperSend:
  • Leave Sync campaign activity to Salesforce enabled (recommended).
  • Click Connect To Salesforce.
  1. In the popup, sign in to the same Salesforce org where you installed the package and approve access.
  2. When the popup closes, Salesforce shows as connected in the Integration Library.


If you need to share only the install step, use the copy-link actions on Step 1 — you do not need a separate email from SuperSend support.


Step 2: Enable Salesforce on a Campaign


Connecting at the team level does not turn on sync for every campaign automatically.


Option A — Campaign Integration Matrix (bulk):


  1. Stay in Admin Settings → Integrations.
  2. Open the Campaign Integration Matrix sub-tab.
  3. Select the same team.
  4. In the Salesforce row, connect or enable the integration for each campaign you want.


Option B — Inside a campaign:


  1. Open the campaign.
  2. Go to Settings → Integrations.
  3. Find Salesforce and turn it on for this campaign.
  4. Configure toggles as needed:
  • Enabled — master on/off for this campaign
  • Sync Activity to Salesforce Contacts — sync sends, opens, and replies to Contacts
  • Per-event toggles for email sent, replies, and opens when shown


Expected Result


  • Integration Library shows Salesforce connected for your team (connected account / org label).
  • For enabled campaigns, activity appears on matching Salesforce Contacts shortly after events occur in SuperSend.
  • Replies and sends are visible on the Contact record in Salesforce for contacts that already exist there with the same email.


Troubleshooting


  • Issue: Connect To Salesforce is disabled or shows “Complete step 1 before connecting.”

Fix: Check Package is installed in my Salesforce org after the Salesforce admin finishes the package install.


  • Issue: OAuth fails immediately or says the integration is not configured.

Fix: SuperSend may still be deploying Salesforce on the server side. Retry in a few minutes. If it persists, contact SuperSend support.


  • Issue: redirect_uri_mismatch or invalid client during OAuth.

Fix: The SuperSend package must be installed in the org you sign into, and your SuperSend environment must use the production API callback URL. Ask support if you use a custom or white-label domain.


  • Issue: Connected successfully but no activity in Salesforce.

Fix: Confirm Salesforce is enabled on that campaign (Settings → Integrations or the matrix). Confirm a Contact exists in Salesforce with the same email as the SuperSend contact. Confirm Sync Activity to Salesforce Contacts and the relevant event toggles are on.


  • Issue: Works in production Salesforce but not sandbox (or the reverse).

Fix: Install the package using the matching link — Open Install (Production) vs Open Install (Sandbox) — and sign in to that same environment during Connect To Salesforce.


  • Issue: Popup blocked.

Fix: Allow popups for app.supersend.io (or your white-label app URL), then click Connect To Salesforce again.


  • Issue: Need to reconnect after revoking access in Salesforce.

Fix: In SuperSend, open the Salesforce integration → disconnect if available, then run Add again and repeat Step 1 (if the package was removed) and Step 2.




Updated on: 19/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!