Journey Builder notify

Use the Salesforce Marketing Cloud Journey Builder Notify activity to send wallet notifications without updating pass data.

The Notify activity sends a wallet notification from Salesforce Marketing Cloud through The Wallet Crew. It does not update pass data and it does not change the pass template.

Use Journey Builder push update when the journey must update pass data with additionalData.

Complete Setup before using this activity.

Real-world examples

• A birthday journey sends a wallet notification without changing the pass content.

• A campaign reminds customers that an offer is about to expire.

• A store event journey sends a local reminder to contacts who already installed the pass.

What the activity does

Journey Builder sends a payload to The Wallet Crew notify listener.

The payload contains:

• identifiers to resolve the target customer or pass

• content for a single notification message

• localizedContent when the message must vary by language

Endpoint URL

Use this endpoint when registering the custom activity:

https://app.thewalletcrew.io/api/<tenantId>/webhooks/listeners/sfmc/actions/notify

<tenantId> is the The Wallet Crew tenant identifier.

Add the activity to a journey

1

Open Journey Builder

Create a new journey or open an existing multi-step journey.

2

Add The Wallet Crew Notify activity

Drag the The Wallet Crew Notify activity into the journey where the wallet notification should be sent.

3

Configure the payload

Define the identifier mapping first. Then define either content or localizedContent.

Configure identifiers

identifiers works the same way as in Journey Builder push update.

A common Salesforce Marketing Cloud example uses a customer identifier stored on the contact.

Identifiers example

{
  "id.sfmc.customerId": "{{Contact.Attribute.Identifier}}"
}

Configure content

Use content when one message is enough for every recipient.

Notify payload with content

{
  "identifiers": {
    "id.sfmc.customerId": "{{Contact.Attribute.Identifier}}"
  },
  "content": "Your pass has been updated. Open Wallet to see the latest information."
}

Configure localizedContent

Use localizedContent when the message must vary by language.

Notify payload with localizedContent

{
  "identifiers": {
    "id.sfmc.customerId": "{{Contact.Attribute.Identifier}}"
  },
  "localizedContent": {
    "en": "Your pass has been updated.",
    "fr": "Votre pass a été mis à jour."
  }
}

Choose between content and localizedContent

Use content for one message shared by every recipient.

Use localizedContent when the notification text must be localized.

Do not use Notify to update pass fields or template variables. That belongs to Journey Builder push update.

Test and activate

Validation should start with a small internal audience.

1

Test with one contact

Use a contact with a known identifier and an installed pass.

2

Check the message payload

Confirm the journey sends either content or localizedContent.

3

Verify the notification on a device

Confirm the notification appears on a real device with the pass installed.

Troubleshooting

No notification is sent

Check the identifier mapping first.

Then confirm the target pass is installed on a real device.

The wrong language is used

Check the keys used in localizedContent and confirm the pass language context matches an available entry.

The pass content does not change

This is expected.

Notify only sends a wallet notification. It does not update pass data.

FAQ

Does Notify update pass fields?

No. Notify only sends a wallet notification.

Use Journey Builder push update to update pass data with additionalData.

Can both content and localizedContent be used together?

One source of notification text should be used per activity configuration.

Use content for one message, or localizedContent for language-specific messages.

Should Notify be used to change template?

No. Notify does not change template and does not use passType.

Template changes belong to Journey Builder push update.