Journey Builder push update

Use the Salesforce Marketing Cloud Journey Builder Push update activity to update pass data through The Wallet Crew.

The Push update activity lets Salesforce Marketing Cloud call The Wallet Crew during a journey. It resolves a pass from contact identifiers and sends the payload needed to update pass data.

Complete Setup before using the activity.

Real-world examples

• A post-purchase journey refreshes the loyalty card after a store transaction.

• A VIP flow switches the targeted pass type after a tier upgrade.

What the activity does

Journey Builder sends a payload to The Wallet Crew push update listener.

The payload contains:

• identifiers to resolve the target customer or pass

• additionalData to inject pass data or template values

• passType when the journey must target a specific pass type

Use Journey Builder notify when the goal is only to send a wallet notification.

Add the activity to a journey

1

Open Journey Builder

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

Use a multi-step journey when wallet updates must be part of a broader campaign flow.

2

Add The Wallet Crew Push update activity

Drag the The Wallet Crew Push update activity into the journey.

Add the The Wallet Crew Push update activity where the journey must refresh pass data or change template.

3

Configure the activity payload

Define the identifier mapping first. Then add any message or template data required by the flow.

Configure identifiers

identifiers must match an identifier already known by The Wallet Crew.

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

Identifiers example

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

Use a stable external identifier whenever possible.

This avoids targeting issues caused by mutable fields such as email.

Configure additionalData

additionalData carries the values used by the target pass update flow.

A simple message example looks like this.

additionalData example

{
  "sfmc_message": "Your message here"
}

The exact keys depend on the The Wallet Crew flow or template logic used by the tenant.

Use passType only to change template

passType is optional.

Leave it empty to keep the current template already associated with the targeted pass.

Set passType only when the journey must switch the pass to another template.

The expected format is passType=template.

Accepted values depend on the tenant configuration.

Test and activate

Validation should start with a small internal audience.

1

Test the journey with one contact

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

2

Check the activity payload

Confirm the identifier value resolves to the expected customer or pass.

3

Verify the pass result

Confirm the pass refreshes as expected on a test device.

4

Activate the journey

Activate the journey once the identifier mapping and wallet behavior are validated.

Troubleshooting

No pass is updated

Check the identifier mapping first.

Most failures come from an identifier name or value that does not match The Wallet Crew data.

The wrong pass type is targeted

Leave passType empty when the goal is only to update the current pass.

Set passType only when the journey must move the pass to another template.

A notification was expected, but no notification appears

Push update does not exist to send notification-only payloads.

Use Journey Builder notify for notification-only use cases.

FAQ

Is passType always required?

No. Leave passType empty to keep the current template.

Set it only when the journey must change the pass template.

Which identifier should be used first?

A stable external identifier should be preferred.

This is usually safer than a mutable field such as email.

Can the activity send a wallet notification?

No. Use Journey Builder notify to send a wallet notification without updating pass data.