> 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.md).

# Marketing automation

Connect marketing automation platforms such as Actito, Bloomreach, Klaviyo and Salesforce Marketing Cloud to update and notify wallet passes.

Marketing automation platforms already orchestrate customer journeys. The Wallet Crew connects those workflows to wallet passes, so pass updates and wallet notifications can be driven from existing tools instead of a separate wallet-only system. Marketing automation typically remains the orchestration layer. It decides the audience, timing, and message. The Wallet Crew executes the wallet-side work and ensures Apple Wallet and Google Wallet receive the updates reliably.

<figure><img src="https://3852727835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlP7d71aYydav6e0pRkxc%2Fuploads%2Fgit-blob-89cd3d331dec3650f9bd2e2ea85a3a9c600c8977%2Fmarketing-automation-overview-en.png?alt=media" alt="The Wallet Crew connects Apple Wallet and Google Wallet pass operations to existing marketing automation platforms"><figcaption><p>Marketing automation remains the orchestration layer. The Wallet Crew runs the wallet-side work.</p></figcaption></figure>

<details>

<summary><strong>Real-world examples</strong></summary>

* **Retail loyalty**: update points after checkout, then notify when a reward unlocks.
* **Event access**: push a last-minute gate or schedule change to all tickets.
* **Gift cards**: refresh balance after redemption so the stored value stays accurate.
* **Membership**: update status and expiry on renewal without reissuing the pass.

</details>

## Real-time control from existing tools

The Wallet Crew supports real-time updates from marketing automation platforms through connectors and APIs. Common operations include updating pass fields, writing campaign messages, adjusting template-driven visuals (colors, images, branded elements), and triggering wallet notifications.

{% hint style="warning" %}
Wallet notifications can be transactional or marketing. Marketing messages usually require an explicit opt-in and proof of consent.

Notification delivery depends on wallet platform behavior and pass settings.
{% endhint %}

## Integration options (connectors, API, SFTP)

Connectors are not the only way to integrate marketing automation with wallet passes. The Wallet Crew also supports direct API calls and SFTP flat-file transfers, which works well when the marketing automation platform cannot run custom connector logic.

### Available connectors

A connector typically exposes wallet actions directly inside the marketing automation tool. This is the most common setup for issuing passes, updating fields, and triggering wallet notifications from scenarios. The pages below do not all have the same type: some are native connectors, others are API recipes or a manual procedure.

| Platform                   | Type                         | What you can do                                                            | Page                                                                                                                      |
| -------------------------- | ---------------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Actito                     | Native connector             | Update passes, notify, sync profiles and installation status               | [Actito](https://docs.thewalletcrew.io/connectors/marketing-automation/actito.md)                                         |
| Adobe Campaign Classic     | API recipe                   | Update pass data from workflows by calling the API                         | [Adobe Campaign Classic](https://docs.thewalletcrew.io/connectors/marketing-automation/adobe-campaign.md)                 |
| Batch.com                  | No connector (contact us)    | Use the API or SFTP flat files                                             | [Batch.com](https://docs.thewalletcrew.io/connectors/marketing-automation/batch.com.md)                                   |
| Bloomreach                 | Native connector             | Update passes, notify, apply benefits, receive wallet events               | [Bloomreach](https://docs.thewalletcrew.io/connectors/marketing-automation/bloomreach.md)                                 |
| Brevo                      | Manual import (no connector) | Add a wallet link to contacts through a CSV round trip                     | [Brevo](https://docs.thewalletcrew.io/connectors/marketing-automation/brevo.md)                                           |
| Klaviyo                    | Native connector             | Authenticated links, profile properties, wallet events, list subscriptions | [Klaviyo](https://docs.thewalletcrew.io/connectors/marketing-automation/klaviyo.md)                                       |
| Salesforce Marketing Cloud | Native connector             | Signed links in Email Studio, pass update and notify in Journey Builder    | [Salesforce Marketing Cloud](https://docs.thewalletcrew.io/connectors/marketing-automation/salesforce-marketing-cloud.md) |

{% hint style="info" %}
Salesforce Marketing Cloud and Adobe Campaign also exist under Email provider, with a different use case: there, The Wallet Crew sends its own transactional emails through the platform. Each page has a "Which page do I need?" note.
{% endhint %}

### Marketing automation platforms not listed

For tenant-specific requirements, use a [custom connector](https://docs.thewalletcrew.io/connectors/custom-connector.md). Tenant scripting can call the platform API and trigger wallet operations.

### API

Any marketing automation platform that can call HTTPS endpoints can integrate through The Wallet Crew API. This approach is commonly used to create passes, update pass data, and trigger notifications from workflow steps.

### SFTP flat files

When workflows are batch-oriented, or when exporting data from an internal data warehouse, pass updates can be delivered as CSV files over SFTP. The Wallet Crew processes the files and applies updates to the targeted passes.

The file format is described in [Update passes with CSV files over SFTP](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/import-and-export/update-pass-using-flat-files.md).

## Environments and URLs

Connector pages in this section refer to hosts by name. This table is the single place that lists them.

| Environment    | Host                                                 | Used for                                                                                                                                                              |
| -------------- | ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Production API | `api.thewalletcrew.io`                               | API calls (`https://api.thewalletcrew.io/api/<tenantId>/...`), webhook listeners                                                                                      |
| Production app | `app.thewalletcrew.io`                               | Pass pages and links (`https://app.thewalletcrew.io/<tenantId>/...`)                                                                                                  |
| Staging (QA)   | `api-qa.thewalletcrew.io`, `app-qa.thewalletcrew.io` | The same paths, for tests before production                                                                                                                           |
| Custom domain  | `<customdomain>`                                     | Pass pages and links, when a custom domain is configured on the tenant                                                                                                |
| SDK            | `sdk.neostore.cloud`                                 | The Add to Wallet button script (see [How the Add to Wallet button works](https://docs.thewalletcrew.io/connectors/e-commerce.md#how-the-add-to-wallet-button-works)) |

The prefix `neostore` is the platform's former name and is kept in technical identifiers such as hostnames, query parameters (`neo.authToken`) and property names.

## FAQ

<details>

<summary><strong>What can be updated from a marketing automation workflow?</strong></summary>

Any field mapped in the tenant data model and displayed by the pass template can be updated. Many projects also use `additionalData` to store campaign-specific values that are rendered on the pass.

</details>

<details>

<summary><strong>What is required to update an existing pass from a workflow?</strong></summary>

A workflow needs a stable way to target a pass. This is typically an internal `passId`, or an external identifier shared with a source system (for example a CRM customer id). Once the pass is resolved, the workflow can update mapped fields and optionally trigger a wallet notification.

</details>


---

# 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.md?ask=<question>&goal=<user_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.
