Setup
Configure The Wallet Crew connector, connect Bloomreach credentials, and install the Bloomreach WebHook preset activities.
Connect Bloomreach Engagement with The Wallet Crew to orchestrate wallet journeys. Bloomreach scenarios can trigger pass actions (create, update, notify). The Wallet Crew also sends events back to Bloomreach for segmentation and measurement.
Prerequisites
Before starting, make sure you have:
Bloomreach permissions
Access to Project settings → Integrations.
Access to API credentials under Project settings → Access Management → API.
The Wallet Crew permissions
Access to the admin console to configure the Bloomreach connector.
Permission to create and manage API keys.
Environment and test data
Target environment identified (staging vs production).
A test pass exists, with a known
passId, to validate calls end-to-end.Any required network allowlisting and security constraints are in place.
The Wallet Crew configuration
Configure general settings
Open the Bloomreach connector settings in the admin console (Data & integrations → Connectors → Marketing automation → Bloomreach), General tab.

Fill in:
Project token (the Bloomreach project token)
API base URL
API key ID
API secret
Bloomreach values are available under Project settings → Access Management → API.

Advanced settings (extensibility)
Advanced settings expose script entry points for the connector. These scripts control contact resolution, event transformation, and field mapping.

Details and script examples: Components and scripts.
Bloomreach configuration
Set up an HTTP authentication schema
Bloomreach calls The Wallet Crew APIs using an API key. This is configured once as an HTTP authentication schema in Bloomreach.
In Bloomreach:
Go to Data & Assets → Integrations → + Add new integration.

Select Http Authentication Schemas.

Configure the schema with an API key created in The Wallet Crew.
The API key needs the tenant.pass:write permission. Create it in the admin console under Settings → Access control → API keys & secrets. Additional permissions can be required depending on the activity set.
Bloomreach schema values:
Endpoint
https://<host>/api: the production or staging host from Environments and URLs
Type
Custom headers
Key
X-API-KEY
Value
The API key created in The Wallet Crew
Install the WebHook preset activities
Bloomreach activities are installed as WebHook preset integrations. The install payload and endpoint of each activity are in Bloomreach activities, together with the icons to use.
A Bloomreach authentication schema is bound to one endpoint. Staging therefore needs its own authentication schema and its own set of activities.
Validation checklist
A minimal validation run usually covers:
One test pass exists and its
passIdis available in Bloomreach.One Update pass activity refreshes visible content on the pass.
One Notify activity delivers a message.
One test install/uninstall produces Bloomreach events.
Event names and properties: Events.
Best practices
Staging first: validate activities and events with a test Bloomreach project token.
Progressive rollout: install only Notify first, then add Apply benefit.
Multi-team setup: IT configures credentials and allowlists, marketing installs the scenario activities.
Last updated

