# Bloomreach
Use Bloomreach Engagement to run wallet journeys with the same logic you already use for email and SMS: segmentation, timing, personalization, and automation. The Wallet Crew is the execution layer that turns those journeys into **Apple Wallet and Google Wallet** behavior, including pass creation, real-time updates, wallet notifications, and tracked in-wallet and in-store signals.
This integration is designed to keep marketing teams autonomous for day-to-day activation, while giving IT the controls needed for identifiers, security, and governance.
Real-world examples
* **Loyalty and CRM** : Keep a loyalty card accurate at all times.\
After a purchase or a tier change, Bloomreach triggers an update and the customer sees the new status almost immediately on the pass.
* **Post-visit automation**\
A scan at checkout or at entry can become a high-intent signal in Bloomreach. Use it to trigger post-visit follow-ups, satisfaction flows, re-engagement, or VIP handling.
* **Acquisition and registration**\
A form embedded in the wallet experience can create or update a Bloomreach contact, then immediately start an onboarding sequence.
### What you can do with it
With Bloomreach + The Wallet Crew, you can:
* **Update passes in real time** based on segmentation and events (tier, points, eligibility, content, visuals).
* **Send wallet notifications** for high-value moments (time-sensitive reminders, important changes, exclusive drops).
* **Trigger scenarios from wallet behavior** with deterministic signals (install, uninstall, scan).
* **Extend Bloomreach with wallet-native touchpoints** that stay visible on the phone, even when email and push are missed.
### How the integration works
{% stepper %}
{% step %}
### Bloomreach → The Wallet Crew (Activities)
Bloomreach “activities” are scenario steps that call The Wallet Crew APIs. They are used to update a pass, add a benefit, or notify a customer.
Common activities:
* **Notify** (wallet notification, optionally with a refresh)
* **Apply privilege** (attach a benefit to a pass, often with a visual/content change)
* **Update pass** (refresh pass data and content)
You can learn the full catalog and when to use each one in [Bloomreach activities](https://docs.thewalletcrew.io/connect/marketing-automation/bloomreach/bloomreach-activities).
{% endstep %}
{% step %}
### The Wallet Crew → Bloomreach (Events)
The Wallet Crew forwards wallet events to Bloomreach so you can segment, trigger scenarios, and measure performance using wallet behavior.
Typical signals include:
* pass created
* installed
* uninstalled
* scanned
See [Events](https://docs.thewalletcrew.io/connect/marketing-automation/bloomreach/events) for the full list, naming, and properties.
{% endstep %}
{% endstepper %}
### Key concepts
* [Setup](https://docs.thewalletcrew.io/connect/marketing-automation/bloomreach/setup): how to connect credentials, configure endpoints, and install the Bloomreach integrations.
* [Bloomreach activities](https://docs.thewalletcrew.io/connect/marketing-automation/bloomreach/bloomreach-activities): scenario actions (Notify, Update pass, Apply privilege, and more).
* [Events](https://docs.thewalletcrew.io/connect/marketing-automation/bloomreach/events): wallet event taxonomy and properties sent into Bloomreach.
* [The Wallet Crew components](https://docs.thewalletcrew.io/connect/marketing-automation/bloomreach/the-wallet-crew-components): *PassDataProvider* and *CustomerFlowElement* (useful when Bloomreach is also a data source, not only an orchestration tool).
* [Extensibility](https://docs.thewalletcrew.io/connect/marketing-automation/bloomreach/extensibility): scripts for identifier resolution, event transformation, and field mapping.
### Consent and frequency
Wallet notifications are highly visible and can feel as “official” as an SMS from your brand. Used well, they build trust and drive action. Used too often, they create fatigue and opt-outs. Always send notifications only to customers who have explicitly consented, and apply frequency caps to protect the experience.
For practical recommendations on content, timing, and throttling, see [Push notifications](https://docs.thewalletcrew.io/engage-and-animate/push-notification). For GDPR framing and consent collection patterns, see [Consents & GDPR compliance](https://docs.thewalletcrew.io/engage-and-animate/push-notification/consents-and-gdpr-compliance).
### FAQ
Does Bloomreach replace email and SMS in this setup?
No. Email and SMS remain key distribution and follow-up channels. Wallet passes add a persistent, always-available surface on the phone.
Which data should be the source of truth?
This depends on the project. Bloomreach can own profile attributes and segmentation. Another system can still own transactional values like purchases, points, or ticket state.
Can wallet adoption be measured in Bloomreach?
Yes. The Wallet Crew forwards install/uninstall events and can forward scan events when the Scan API is used. Details: [Events](https://docs.thewalletcrew.io/connect/marketing-automation/bloomreach/events).
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.thewalletcrew.io/connect/marketing-automation/bloomreach.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
