> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/connectors/marketing-automation/bloomreach/extensibility.md).

# Components and scripts

Bloomreach connector components (PassDataProvider, CustomerFlowElement) and scripts for contact resolution, event transformation and data mapping.

Extensibility customizes how the connector resolves contacts, maps fields, and formats events. This is mainly used by technical teams when default behavior does not match the data model. The complete reference of the three Bloomreach scripts, with their registration, their handlers and worked examples, is the [Bloomreach scripts](https://docs.thewalletcrew.io/developers-guides/scripting/extensions/bloomreach.md) page of the Developers guides.

## The Wallet Crew components

The Bloomreach integration is implemented as a connector plus optional components that read and write Bloomreach customer data as part of wallet flows. The connector credentials are described in [Setup](https://docs.thewalletcrew.io/connectors/marketing-automation/bloomreach/setup.md).

<div data-with-frame="true"><figure><img src="https://3852727835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlP7d71aYydav6e0pRkxc%2Fuploads%2Fgit-blob-c000a2feea2457d5e6feccacfbd5cc767a4a8a4a%2Fdocumentation-bloomreach-wallet-crew-components.png?alt=media" alt="Diagram of The Wallet Crew components involved in the Bloomreach integration"><figcaption><p>Main building blocks: activities, events, and connector-side components.</p></figcaption></figure></div>

### PassDataProvider

PassDataProvider retrieves customer information from Bloomreach and exposes it to pass rendering. This makes Bloomreach a data source for fields displayed on Apple Wallet and Google Wallet passes, such as tier labels, points, expiry dates and personalization attributes.

* Display Bloomreach attributes directly on the pass.
* Refresh data when the pass is opened or explicitly updated.
* Reduce duplicated storage across systems when Bloomreach is the CRM source of truth.

### CustomerFlowElement

CustomerFlowElement can create or update a Bloomreach contact as part of a wallet flow. A common usage is linking an enrolment form submission to Bloomreach profile creation. In `flows.yml`, the step is named `bloomreachCustomer`.

* Create a Bloomreach contact from enrolment forms.
* Update Bloomreach attributes when a customer edits their profile.
* Control matching rules (email, phone, member ID, ...) through the scripts below.

## Rollout of scripts

Scripts are stored in the Bloomreach connector **Advanced settings** of the admin console, one slot per script: **Contact finder configuration**, **Event interceptor configuration** and **Customer mapper configuration**.

<p align="center"><a href="https://admin.thewalletcrew.io/tenant/~/integrations/bloomreach/advanced" class="button secondary" data-icon="chevrons-right">Open Advanced settings page</a></p>

Start in staging and with the smallest possible change: Contact Finder first when email is not the primary identifier, Event Interceptor first when event naming or governance is required. Then validate both directions: an activity still works (Update pass, Notify, Apply benefit), and an event is still attributed to the expected Bloomreach contact with its final name and properties. Roll out to production in a change window when events trigger scenarios.

## Extensibility entry points

{% hint style="warning" %}
Changes can impact event tracking and scenario execution. A staging environment is recommended for testing.
{% endhint %}

### Contact Finder

A pass is linked to external identifiers (email, phone, member ID, ...). When an event happens on a pass, the connector needs to attach it to a Bloomreach contact. Without a Contact Finder script, a pass with an `email` identifier is matched on the Bloomreach `registered` identifier only (its other identifiers are not sent); a pass without `email` sends its identifiers unchanged.

Contact Finder customizes how those identifiers are converted into Bloomreach contact identifiers.

### Event Interceptor

Event Interceptor can transform `eventName` and `properties` before sending the event to Bloomreach. This is useful for naming conventions, filtering, and enrichment.

Returning `null` drops the event.

### Customer Mapper

Customer Mapper customizes mapping between The Wallet Crew enrolment form fields and Bloomreach fields. This is used when data is sent to or retrieved from Bloomreach with components like PassDataProvider and CustomerFlowElement.

## FAQ

<details>

<summary><strong>Can Contact Finder call external services?</strong></summary>

This is typically used when the Bloomreach contact identifier is not directly stored on the pass. Common patterns include resolving a `memberId` into an email, or mapping multiple identifiers to a single “registered” Bloomreach identifier.

</details>

<details>

<summary><strong>Can an event be dropped before reaching Bloomreach?</strong></summary>

This is useful for governance and noise reduction. Examples include filtering out scan events from test passes, removing sensitive properties, or ignoring high-volume events that are not actionable in Bloomreach.

</details>

<details>

<summary><strong>When is Customer Mapper used?</strong></summary>

It is not used by every activity. For example, sending a Notify message does not require Customer Mapper unless Bloomreach properties are also used as a data source for pass rendering.

Customer Mapper is the right place to align naming conventions, data formats, and optional fields. It also helps keep pass templates stable when Bloomreach field names change.

</details>

<details>

<summary><strong>Does PassDataProvider overwrite pass fields, and when does Bloomreach data appear on the pass?</strong></summary>

PassDataProvider exposes data to the pass template. What is displayed depends on the template field configuration. The data appears after a pass refresh, triggered by an explicit update or by the rules configured for the pass.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/connectors/marketing-automation/bloomreach/extensibility.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
