Setup

Prepare Salesforce Marketing Cloud and The Wallet Crew for authenticated pass links, pass updates, and wallet notifications.

This setup prepares the shared pieces used by the Salesforce Marketing Cloud integration. It covers signing keys for authenticated links and the installed package used by the Journey Builder custom activities.

Real-world examples

• A CRM team wants personalized pass links in Email Studio.

• A marketing team wants Journey Builder to trigger pass updates after a purchase or a tier change.

• A CRM team wants Journey Builder to send wallet notifications without changing pass data.

• An implementation partner wants a staging setup before production rollout.

Prerequisites

Access is required on both sides.

• The Wallet Crew: access to the admin console.

• Salesforce Marketing Cloud: access to Setup, Key Management, Content Builder, and Installed Packages.

• The target tenant identifier is known.

• A test contact exists in Salesforce Marketing Cloud.

Configure the signing key for authenticated pass links

The Wallet Crew pass link is signed as a JWT. Salesforce Marketing Cloud needs a symmetric key to sign this token in AMPscript.

1

Copy the shared secret from The Wallet Crew

Open the tenant security secrets in The Wallet Crew admin console.

Copy the first secret. This value is used as the pre-shared key in Salesforce Marketing Cloud.

2

Create a symmetric key in Salesforce Marketing Cloud

Open Setup → Administration → Key Management.

Create a new symmetric key and paste the The Wallet Crew secret into Pre-Shared Key.

Create a symmetric key and store the The Wallet Crew secret as the pre-shared key.

3

Save the external key value

Keep the external key value available.

The AMPscript example uses this value as @keyId when calling GetJWTByKeyName.

Create the installed package for Journey Builder

This package is only required when Journey Builder needs to trigger pass updates or wallet notifications.

1

Create the package

Open Setup → Apps → Installed Packages.

Create a package named The Wallet Crew.

Create a dedicated installed package for The Wallet Crew Journey Builder activity.

2

Copy the JWT Signin Key

Open the package and copy the JWT Signin Key.

The JWT Signin Key is required by The Wallet Crew custom activity configuration.

3

Ask The Wallet Crew support to enable the Salesforce Marketing Cloud connector

The Salesforce Marketing Cloud connector must be enabled first on the tenant.

Ask The Wallet Crew support to enable the connector before continuing.

4

Paste the sign-in key in The Wallet Crew back office

Open Data & Integrations → Connectors → SFMC in The Wallet Crew back office.

Paste the JWT Signin Key copied from the Salesforce Marketing Cloud package into Sign-in Key, then save.

5

Register the Journey Builder activities

From the same package, add a Journey Builder Activity component for each activity.

Use these values for Push update:

• Category: Messages

• Endpoint URL: https://app.neostore.cloud/api/<tenantId>/webhooks/listeners/sfmc/actions/pushupdate

Use these values for Notify:

• Category: Messages

• Endpoint URL: https://app.neostore.cloud/api/<tenantId>/webhooks/listeners/sfmc/actions/notify

<tenantId> is the The Wallet Crew tenant identifier.

Register the The Wallet Crew Journey Builder activity with the tenant-specific push update endpoint.

Validate the setup

Validation should start before any campaign build.

• Confirm the symmetric key exists in Key Management.

• Confirm the external key value is available for AMPscript.

• Confirm the installed package contains the Journey Builder activity component required by the target use case.

• Confirm the Sign-in Key is saved in Data & Integrations → Connectors → SFMC.

• Confirm each endpoint URL contains the correct tenant identifier.

• Confirm a test contact is available for preview and journey testing.

FAQ

Is the installed package required for Email Studio pass links?

No. The installed package is only required for the Journey Builder custom activities.

Email Studio pass links only need the symmetric signing key.

Which environment should be configured first?

Staging should be configured first.

This makes it easier to validate token signing, contact resolution, and Journey Builder execution before production rollout.

What is the most common setup error?

The most common issue is a mismatch between the The Wallet Crew secret and the Salesforce Marketing Cloud symmetric key.

For Journey Builder, the next common issue is a wrong tenant identifier in the endpoint URL.

Another common issue is registering the wrong activity endpoint for the intended use case.