---
title: "Marketing Cloud technical setup for Jacquard"
slug: "marketing-cloud-technical-setup-for-jacquard"
updated: 2026-10-20T08:47:13Z
published: 2026-10-20T08:47:13Z
canonical: "support.jacquard.com/marketing-cloud-technical-setup-for-jacquard"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.jacquard.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Marketing Cloud technical setup for Jacquard

For Marketing Cloud admins and developers. Covers the runtime key, code snippets, Event Notification Service and the API connection.

**Placeholders:** example values (for example names in code) and values in angle brackets are account-specific. Your Jacquard contact provides them.

**Existing customers:** only needed for new touchpoints. Existing Jacquard code and event tracking keep working.

## Technical setup

For your Marketing Cloud admin or developer. Doesn’t affect existing sends.

### 1. Jacquard | Create the Jacquard runtime key

**1.1 Create the key**

- In Jacquard, go to **Admin > API keys & webhooks** and click **+ New API key**.
- Name: `Marketing Cloud snippets`
- Scopes: `runtime:select`
- Integration type: Salesforce Marketing Cloud
- Leave other fields blank. Click **Create key**.

**1.2 Copy the key**

The key starts `jq_live_`. It’s shown once only.

### 2. Marketing Cloud | Create the code snippets

**2.1 Copy the snippet code**

From the touchpoint’s **Connect** tab in Jacquard.

**2.2 Create the snippet**

- In Content Builder, click **Create > Content Blocks > Code Snippet**.
- Name: `Jacquard – touchpoint`.
- Paste the code and add your `jq_live_` key where indicated.
- Save in a folder your marketing team can access.

**2.3 Note the customer key**

Marketing uses it to add the snippet. Check it matches the Connect tab.

**2.4 Repeat**

One snippet per touchpoint.

### 3. Marketing Cloud | Set up Event Notification Service

**Existing customers:** keep your existing event tracking. Skip this section.

**3.1 Get the endpoint token** *(Jacquard does this)*

Jacquard sends it through a secure channel.

**3.2 Open ENS**

**Setup > Platform Tools > Feature Settings > Event Notification Service**. If missing, ask Salesforce to enable it.

**3.3 Create the callback**

- **Callbacks > New**. Name: `Jacquard`.
- URL: `https://<jacquard-callback-url>/{endpointToken}`
- **Max batch size**: 1000.

**3.4 Verify the callback**

Click **Verify**. Enter the verification key your Jacquard contact sends back.

**3.5 Send the Signature Key**

Send the callback’s Signature Key to Jacquard through the secure channel.

**3.6 Create the subscription**

- **Subscriptions > New**. Name: `Jacquard signals`. Callback: `Jacquard`.
- Events: EmailSent, EmailOpen, EmailClick, EmailBounced, EmailUnsubscribe.
- Filter to your sending Business Unit. Click **Activate**.

## API connection

Imports touchpoints and checks wiring. Part 1 is still required.

### 4. Who and when

| **Who** | Marketing Cloud admin with permission to create Installed Packages. |
| --- | --- |
| **New customers** | Any time after you have Jacquard access. |
| **Existing customers** | Any time from upgrade stage 2. Doesn’t affect sends. |

#### What it adds

| Without | With |
| --- | --- |
| Touchpoints set up with your Jacquard contact | Import journeys and emails as touchpoints |
| Test send only | Jacquard runs delivery verification before activation |

### 5. Marketing Cloud | Create an Installed Package

**5.1 Create an Installed Package**

**Setup > Platform Tools > Apps > Installed Packages > New**. Name: `Jacquard`. Keep any previous Jacquard AppExchange app.

**5.2 Add a component**

**Add Component > API Integration > Server-to-Server**. Not Web App.

**5.3 Set permissions**

Only those below. Content Builder may appear under **Assets**.

**5.4 Grant Business Unit access**

On the **Access** tab. Note the MID to restrict Jacquard to one Business Unit.

**5.5 Copy credentials**

- Client ID
- Client Secret
- Subdomain: the Authentication Base URI before `.auth.marketingcloudapis.com`

| Permission | Purpose |
| --- | --- |
| `Automation > Journeys: Read` | List journeys |
| `Content Builder: Read` | Read Content Builder emails |
| `Content Builder: Write` | Create and update Jacquard snippets |

Jacquard can’t send messages, change audiences or publish journeys.

### 6. Jacquard | Connect and import

**6.1 Connect**

In Jacquard, go to **Connectors > Salesforce Marketing Cloud > Connect**. Enter Client ID, Client Secret, subdomain and optional MID. Click **Save connection**.

**6.2 Sync**

Click **Sync**. No changes are made in Marketing Cloud.

**6.3 Import**

Select journeys and emails to import as touchpoints.

### 7. Marketing Cloud | After connecting

**7.1 Verification**

Run delivery verification on each touchpoint before activating.

## Ready to send emails

1. **Confirm setup** *(Jacquard does this)*

Your Jacquard contact confirms the snippets and events work.
2. **Hand over**

Send your marketing team the snippet customer key for each touchpoint.
3. **Configure your templates**

See the guide on configuring your templates: *Set up Marketing Cloud messages for Jacquard*.

## Reference

### Reference and troubleshooting

| Item | Source | Destination |
| --- | --- | --- |
| `jq_live_` runtime key | Jacquard Admin > API keys & webhooks | Code snippet |
| Snippet code | Touchpoint Connect tab | Content Builder |
| ENS endpoint token, verification key | Jacquard (secure channel) | ENS callback |
| ENS Signature Key | ENS callback | Jacquard (secure channel) |

#### Troubleshooting

**Snippet returns nothing or an error**

Check the key in the snippet is active with `runtime:select` scope.

**ENS verification fails**

Click **Verify** again and request the new key from Jacquard.

**No events in Jacquard**

Check the subscription is active, filtered to the right Business Unit, with all five events.

#### API connection troubleshooting

**Connection failed**

Check the component is Server-to-Server, the subdomain has no `https://` or `.auth…`, and the package has Business Unit access.

**Disconnect**

Delete the Installed Package. Snippets and sends keep working.

#### Keys and tokens

- Don’t share keys by email, chat, tickets or shared documents.
- If a key is exposed: create a new one, update it everywhere, revoke the old one (**Admin > API keys & webhooks**).