> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-integrations/zap-post-integrations/bloomreach.md).
# Bloomreach
Connect Bloomreach Engagement to ZAP\~POST to send direct mail from scenarios and track delivery/scan events on profiles.
Use Bloomreach Engagement (formerly Exponea) with ZAP-POST in two directions:
### 1) Push recipient data from Bloomreach to ZAP-POST
Use Bloomreach scenarios to send customer and address data via webhooks. ZAP-POST creates a submission against your campaign.
* Start here: [Pushing Data to ZAP\~POST with Bloomreach Scenarios](/zap-integrations/zap-post-integrations/bloomreach/pushing-data-to-zap-post-with-bloomreach-scenarios.md)
### 2) Write ZAP-POST events back to Bloomreach profiles
When ZAP-POST processes mail, it can create events on Bloomreach profiles. Typical events include submission created, mail rejected, mail sent, mail returned, and QR scans.
* Install and connect: [Installation Guide](/zap-integrations/zap-post-integrations/bloomreach/populating-bloomreach-with-zap-post-events/installation-guide.md)
* Then configure events: [Populating Bloomreach with ZAP\~POST Events](/zap-integrations/zap-post-integrations/bloomreach/populating-bloomreach-with-zap-post-events.md)
* Event payload reference: [ZAP\~POST Events in Bloomreach](/zap-integrations/zap-post-integrations/bloomreach/populating-bloomreach-with-zap-post-events/zap-post-events-in-bloomreach.md)
{% hint style="info" %}
Most teams use both directions: scenarios to trigger mail, then profile events to measure and automate follow-ups.
{% endhint %}
---
# 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://userguide.zappost.com/zap-integrations/zap-post-integrations/bloomreach.md?ask=&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.
