Move your Marketing Cloud setup to the new Jacquard

Guides: New customer setup · Existing customers: moving to the new Jacquard · API connection (optional) · All guides

For existing Jacquard customers. Jacquard moves your account to the new version in the background, and your sends keep working throughout. Your existing Jacquard code snippets, tokens and event connections keep working too, so you don’t need to update existing touchpoints or set up new events. Your Marketing Cloud admin or developer creates a new runtime key for new touchpoints (Part 1), and new touchpoints you add after the move use the new code snippet (Part 2).

Your move (Led by Jacquard). Jacquard moves your account to the new version in four stages. Your sends keep working throughout.

• Accept your invitation

• Review the parity checklist with us

• Sign off when we confirm the move is complete

Update Marketing Cloud (Part 1, technical). For your admin or developer. Start from stage 2 of your move.

• Create your new runtime key

• Leave your existing event tracking as it is

Your emails and push messages (Part 2, marketing). For the team that builds your emails and push messages. Start once we confirm your move is complete.

• Leave existing Jacquard code snippets in place

• Use the new code snippet only for new touchpoints

Your move to the new Jacquard

Jacquard moves your account for you, in four stages. Your emails and push messages keep sending as they do today the whole way through, and afterwards.

The four stages

• Stage 1: Account copied (Takes minutes)

  Jacquard copies your campaigns, approved content, users and send history into the new version.

  You: nothing to do.

• Stage 2: Side by side (At least 24 hours)

  The new Jacquard learns from your last 30 days and runs alongside your current setup. Your sends still use the current platform’s choices.

  You: accept your invitation and review the parity checklist. Your admin can start Part 1.

• Stage 3: Switch-over (At least 48 hours of checks)

  Jacquard switches your existing connection so it serves content chosen by the new version. Your email code doesn’t change.

  You: keep sending as normal.

• Stage 4: Settling (7 days after switch-over)

  Jacquard checks your reporting lines up across old and new, then confirms with you that the move is complete.

  You: confirm sign-off with your Jacquard contact.

• Move complete (Your contact confirms)

  Nothing changes in your existing emails and push messages. New touchpoints use the new code snippet (Part 2).

What to do during your move

1. Share your key dates

   Tell your Jacquard contact about any code freezes, peak periods or big sends coming up, so we can schedule the move around them.

2. Tell us about new campaigns

   If you set up a new Jacquard campaign after your account has been copied, let your contact know so it comes across too.

3. Accept your invitation

   At stage 2, you and your team get an email invitation to the new Jacquard. Accept it to see your account, touchpoints and history. Campaigns that sent recently arrive active; older ones come across for reporting.

4. Review the parity checklist

   Your Jacquard contact shares a short checklist to confirm everything carried over: channels, personalisation variables, tags and in-app metrics. Tell them if anything looks wrong.

5. Leave your existing Jacquard code in place

   The Jacquard code snippets already in your emails and push messages and your existing Jacquard tokens and event connections keep working with the new version of Jacquard, so there’s nothing to update. Don’t remove or replace them. The technical setup in Part 1 is safe to do early because it doesn’t change your sends.

6. Confirm sign-off

   At the end of stage 4, your Jacquard contact confirms your reporting and asks you to sign off. After that, you can add new touchpoints (Part 2).

Who does what, and when

Part 1: Update Marketing Cloud (technical)

For your Marketing Cloud admin or developer. Do this any time from stage 2 of your move, once you’ve accepted your invitation, and before you add your first new touchpoint. None of this changes your sends.

1.1 Create your runtime key

New touchpoints you add after your move use this key in their code snippet. Your existing Jacquard code keeps working as it is.

1. Create your Jacquard runtime key (From stage 2)

   In Jacquard, go to Admin > API keys & webhooks and click + New API key. Set:

   • Name: Marketing Cloud snippets

   • Scopes: RUNTIME:SELECT

   • Integration type: Salesforce Marketing Cloud

   Leave the other fields as they are and click Create key. Copy the key, which starts jq_live_, straight away: it’s only shown once.

2. Leave your existing Jacquard content as it is

   Don’t edit or delete the Jacquard AMPscript, content blocks or data extension lookups already in Content Builder.

3. Leave your event tracking as it is

   Leave your existing Jacquard event tracking exactly as it is. Jacquard keeps using it. You don’t need to set up a new events connection.

1.2 Hand over to your marketing team

1. Confirm the setup (Jacquard does this)

   Your Jacquard contact confirms everything is in place.

2. Tell your marketing team Part 1 is done

   Point them to Part 2. Existing emails and push messages need no changes.

Part 2: Your emails and push messages (marketing)

Your existing emails and push messages need no changes. This part covers what to leave alone, and how to add new touchpoints after your move.

2.1 Your existing emails and push messages

Nothing to change.

1. Leave your existing Jacquard code snippets in place

   The code snippets already in your emails and push messages keep working with the new version of Jacquard. You don’t need to update existing touchpoints. Don’t remove, replace or edit the code.

2. Don’t look for your existing code in Jacquard

   Jacquard doesn’t display the code your existing touchpoints use. A touchpoint’s Connect tab only shows the code for adding it to a new message. That’s expected; your existing code is still working.

3. Keep sending as normal

   Activate journeys and schedule sends the way you do today.

2.2 Add new touchpoints after your move

New touchpoints use the new code snippet, set up the same way as for a new customer.

1. Create the touchpoint in Jacquard (After stage 4)

   Set up each new touchpoint in Jacquard with your Jacquard contact, or import it if you’ve connected your account (see the API connection guide).

2. Your admin creates the code snippet

   Your admin follows Part 1.1 of the setup guide for the new touchpoint, creating a code snippet with the key from Part 1.1 here.

3. Your marketing team adds it to the message

   Your marketing team follows Part 2 of the setup guide to add the code snippet and variables to the new email or push message, then tests it.

4. Approve and activate

   Approve the experiment plan on the touchpoint in Jacquard, then activate it and launch as normal.

Reference

Who sends what, and what to check when something doesn’t look right.

Handover checklist and troubleshooting

Troubleshooting

I can’t find my existing code on the Connect tab

That’s expected. Jacquard doesn’t display the code your existing touchpoints use, but it keeps working. Leave it as it is.

An existing message has stopped showing Jacquard copy

Don’t replace the code. Tell your Jacquard contact, who can check the touchpoint.

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.