Connect Salesforce Marketing Cloud
On this page
The Marketing Cloud row ("Read outcomes from the business units you add.") connects Salesforce Marketing Cloud, read-only. It holds your installed package's keys and your business units, and Test connection checks each unit.
Before you start
- You need the Owner or Admin role to connect or change it. Managers can see the connection; anyone else sees Owners and admins on the row.
- Your Marketing Cloud admin creates a package for Tapper, as the form lists under Before you start, in your own Marketing Cloud account:
- Under Setup, Apps, Installed Packages, create a package and add an API Integration of type Server-to-Server.
- Grant only: List and Subscribers: Read, Data Extensions: Read, Tracking Events: Read.
- Make the package available to every business unit you add.
- Copy the Client ID, Client secret and Authentication Base URI from the integration.
- Have each business unit's MID, from Setup, Business Units in Marketing Cloud.
Tapper asks for a read-only token. It cannot change anything in Marketing Cloud.
Connect Marketing Cloud
- With several protected entities, pick the entity in the switcher at the top of the sidebar.
- Under Setup, click Data sources. Marketing Cloud is in Leads and customers.
- Click Set up on the row.
- Enter the Authentication Base URI (it ends in
.auth.marketingcloudapis.com), Client ID and Client secret. - Under Business units, enter each unit's MID and Brand. Add business unit adds a row, up to 30.
- Click Connect.


Test the connection
Click Manage on the row, then Test connection. The Activity tab shows whether it passed and the result per business unit.
Once connected
- The row reads Connected, with the last test's result and time. A failed test shows in red.
- Settings shows the Authentication Base URI, Client ID, Client secret (last characters only) and Business units. Edit changes them.
- Activity shows the Last test and each business unit's last test.
- Disconnect deletes the stored secret. To end access on Salesforce's side, delete Tapper's API integration from the package.
If something goes wrong
- A business unit fails its test: check the package is available to it and the MID is right, then test again.
- "The save failed. Paste the Client secret again.": the secret is not kept after a failed save. Paste it and press Connect or Save.
- "Too many connection tests.": the limit is 30 tests an hour per address and per workspace. Try again in an hour.
Related
Was this helpful?
Still need help?
Chat with our team and mention this article.