Guides: New customer setup · Existing customers: moving to the new Jacquard · API connection (optional) · All guides
Optional, for new and existing customers. Connecting a Server-to-Server Installed Package lets you import your journeys and emails into Jacquard as touchpoints, and lets Jacquard check your wiring before you activate. You still need the code snippets from the setup or move guide. Jacquard can’t send messages, change audiences or publish journeys.
Your account details. Your Jacquard contact will give you your own account URLs and values. Wherever you see a value in angle brackets, such as https://<jacquard-callback-url>, use the value we’ve given you for your account.
Who does this: A Marketing Cloud admin who can create Installed Packages.
New customers: Any time once you have access to Jacquard, before or after the setup guide.
Existing customers: From stage 2 of your move, once you’ve accepted your invitation. It doesn’t change your sends. See the move guide.
Without a connection | With a connection |
|---|---|
You set up touchpoints in Jacquard with your contact | You import journeys and emails as touchpoints yourself |
A test send is your check | Jacquard runs delivery verification before you activate |
Connect your Marketing Cloud account
Optional. Your admin creates one Server-to-Server Installed Package; Jacquard uses it to import touchpoints and check your wiring.
1.1 Create an Installed Package
Create an Installed Package
In Marketing Cloud, go to Setup > Platform Tools > Apps > Installed Packages and click New. Name it
Jacquardand save.If you installed the previous Jacquard app from AppExchange, the new version doesn’t use it. Leave it in place until your move is complete.
Add a Server-to-Server API Integration
Click Add Component, choose API Integration, then Server-to-Server. This uses the OAuth client-credentials flow. Don’t choose Web App.
Grant only the permissions below
Tick the scopes in the table and leave everything else unticked. Content Builder access sits in the Assets group in some accounts.
Give the package access to your Business Unit
Open the package’s Access tab and grant access to the Business Unit that sends your Jacquard campaigns. To keep Jacquard to one Business Unit, grant only that one and note its MID.
Copy the credentials
From the component, copy the Client ID, Client Secret and Authentication Base URI. Your subdomain is the part of that URI before
.auth.marketingcloudapis.com.
Permissions
Permission | Why Jacquard needs it |
|---|---|
Automation > Journeys: Read | List journeys so you can import them |
Content Builder: Read | List and read your Content Builder emails |
Content Builder: Write | Create and update the Jacquard code snippets your marketing team adds to messages |
Not needed: Automation Studio, email, SMS or push send APIs, Contacts or Journey write access. Jacquard can’t send messages, change audiences or publish journeys.
1.2 Connect and import your touchpoints
Connect Marketing Cloud in Jacquard
In Jacquard, open Connections > Salesforce Marketing Cloud > Connect. Enter the Client ID, Client Secret, subdomain and, optionally, the MID. Click Save connection. The button changes to Connected once Jacquard has tested it.
Sync
Click Sync. Jacquard reads your journeys and Content Builder emails. Nothing in Marketing Cloud changes.
Import your touchpoints
Choose the journeys and emails you want to optimise and import them as touchpoints. Only what you import is affected.
1.3 What changes once you’re connected
You still need your code snippets
Connecting doesn’t replace the Jacquard code snippets. Your admin still creates them as described in the setup guide or move guide. Don’t edit, rename, move or delete them.
Carry on with Part 2 of your guide
Your marketing team still adds the snippet reference and variables to each message, as in the setup or move guide.
Run delivery verification
On each touchpoint in Jacquard, run verification. Jacquard reads back what’s in Marketing Cloud and flags anything missing before you activate.
Reference
What to check when something doesn’t look right.
Troubleshooting
Jacquard says the connection failed
Check the component is Server-to-Server, the subdomain is copied without https:// or .auth…, and the package has access to the Business Unit.
You want to disconnect
Delete the Installed Package. Jacquard stops importing and checking your journeys, but your snippets and sends keep working.
Handling secrets safely
Keys, tokens and secrets on this page give access to your account. Enter them directly into Jacquard’s Connections screen or share them through the secure channel your Jacquard contact sets up. Never paste them into email, chat, tickets or shared documents. If one is exposed, create a replacement, update it wherever it’s used, then revoke the old one. For Jacquard keys, you do this under Admin > API keys & webhooks.