> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/connectors/marketing-automation/salesforce-marketing-cloud.md).
# Salesforce Marketing Cloud
Connect Salesforce Marketing Cloud to Apple Wallet and Google Wallet passes in The Wallet Crew: pass links, Journey Builder updates and notifications.
Connect Salesforce Marketing Cloud with The Wallet Crew to distribute authenticated pass links from Email Studio, update pass data from Journey Builder, and send wallet notifications.
Salesforce Marketing Cloud remains the orchestration layer. The Wallet Crew resolves pass identifiers, signs wallet links, updates pass data, and delivers wallet notifications.
Real-world examples
* A loyalty email opens the right pass page for each contact.
* A reminder campaign targets contacts who still did not install the pass.
* A Journey Builder step refreshes a pass after a purchase.
* A separate Journey Builder step sends a wallet notification for a birthday or an expiring offer.
## What this integration covers
This section focuses on three core Salesforce Marketing Cloud use cases.
* authenticated pass links in **Email Studio**
* pass updates in **Journey Builder**
* wallet notifications in **Journey Builder**
## Pages in this section
* [Setup](/connectors/marketing-automation/salesforce-marketing-cloud/setup.md): prepare signing keys, register the installed package, and validate the configuration.
* [Send pass links in Email Studio](/connectors/marketing-automation/salesforce-marketing-cloud/send-pass-links-in-email-studio.md): generate JWT-based links in AMPscript and use them in content blocks.
* [Journey Builder push update](/connectors/marketing-automation/salesforce-marketing-cloud/journey-builder-push-update.md): configure the custom activity used to update pass data with `additionalData`.
* [Journey Builder notify](/connectors/marketing-automation/salesforce-marketing-cloud/journey-builder-notify.md): configure the custom activity used to send wallet notifications only, including identifier mapping and browser-based default reuse.
## How the integration works
{% stepper %}
{% step %}
### Email Studio
Salesforce Marketing Cloud signs an authenticated link with AMPscript.
The Wallet Crew verifies the token and opens the right pass page for the contact.
{% endstep %}
{% step %}
### Journey Builder
Journey Builder sends an activity payload to The Wallet Crew.
Use **Push update** to update pass data.
Use **Notify** to send a wallet notification without changing pass data.
{% endstep %}
{% endstepper %}
## Scope note
This section covers Salesforce Marketing Cloud as a marketing automation platform.
Transactional email delivery through Salesforce Marketing Cloud is documented separately in [Salesforce Marketing Cloud email provider](/connectors/email-provider/salesforce-marketing-cloud.md).
## FAQ
Which Salesforce Marketing Cloud feature should be used first?
Start with **Email Studio** when the goal is to distribute a pass link in an email or SMS.
Use **Journey Builder** when the goal is to automate a pass update or a wallet notification after a customer event.
What is the difference between Push update and Notify?
**Push update** updates pass data with `additionalData`.
**Notify** sends a wallet notification only. It does not update pass data.
Is Salesforce Marketing Cloud required to distribute Wallet passes by email?
No. The Wallet Crew can distribute pass links through other channels and connectors.
Salesforce Marketing Cloud is useful when journeys, segmentation, and campaign orchestration already live there.
Who usually owns the setup?
Connector enablement, package creation, and signing keys are usually handled by IT or an implementation partner.
Campaigns, journey logic, and message content are usually handled by CRM or marketing operations.
Can the same contact receive both email and wallet notifications?
Yes.
Email Studio can distribute the pass link first, then Journey Builder can use wallet activities later once the pass exists and is installed.
Does this section also cover transactional email sending through Salesforce Marketing Cloud?
No.
This section covers Salesforce Marketing Cloud as a marketing automation and journey orchestration platform. Transactional sending through Salesforce Marketing Cloud is documented separately in [Salesforce Marketing Cloud email provider](/connectors/email-provider/salesforce-marketing-cloud.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.thewalletcrew.io/connectors/marketing-automation/salesforce-marketing-cloud.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.