> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/integrations/marketing-platforms/how-to-connect-batch-to-refiner.md).

# How to connect Batch to Refiner?

Sync Refiner survey responses and events to Batch Profiles, and send Refiner Email Surveys from your Batch campaigns and automations.

[Refiner](https://refiner.io/) is an In-app survey platform for SaaS and mobile apps. It enables product and voice-of-customer teams to launch targeted in-app surveys and continuously collect NPS, CSAT, CES, product feedback, and zero-party user data.

## Overview

The Refiner integration covers 2 features. You can use them independently or together:

* **Survey data sync (Refiner → Batch):** Refiner sends survey interaction events and response data to Batch through the [Profiles API](/developer/api/cep/profiles.md). Survey answers can also update Batch profile attributes, with or without contact data.
* **Email Surveys (Batch → your recipients):** Batch handles the audience, scheduling and delivery of your email. Refiner provides the survey and collects the responses. You add the Refiner embed code to your Batch email, whether you build it with the Email Composer or upload your own HTML template.

### Popular use cases

* Segment your audience by satisfaction scores, preferences, or needs collected through surveys.
* Follow up with dissatisfied customers or invite happy customers to join an advocacy program.
* Send an NPS or CSAT survey as part of a post-purchase or onboarding journey.

## Prerequisites

You’ll need:

* Access to both the [Batch](https://dashboard.batch.com) and [Refiner](https://app.refiner.io/) dashboards
* Your Batch **Project Key** and **REST API Key**, available in [Settings](/getting-started/features/customer-engagement-platform/settings.md).
* A [Custom User ID](https://doc.batch.com/developer/technical-guides/how-to-guides/how-to-choose-the-right-custom-user-id-to-use-in-batch) implemented in Batch. Refiner uses it to match each survey response to the right Batch Profile.

{% hint style="warning" %}
Access to the REST API Key requires Administrate rights in Batch. If the field shows "Insufficient Privileges", refer to [this documentation](https://doc.batch.com/getting-started/other/faq/why-do-i-have-insufficient-privileges-in-the-rest-api-key-field).
{% endhint %}

## 1. Implementation steps

To get started, follow the steps described in Refiner's documentation: [Batch Integration](https://refiner.io/docs/kb/integrations/batch-integration/)

{% hint style="info" %}
Note: This integration is maintained by Refiner.
{% endhint %}

## 2. Using Refiner data in Batch

Once synced, Refiner data works like any other Batch profile data, e.g.:

* **Targeting:** build [Segments](https://doc.batch.com/guides-and-best-practices/profiles/how-to-create-and-use-a-segment) based on survey answers or scores.
* **Automations:** use Refiner events to trigger [omnichannel automations](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/trigger-automations).
* **Personalization:** insert survey answers into your messages with [personalization](https://doc.batch.com/getting-started/features/customer-engagement-platform/message/personalization).


---

# 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://doc.batch.com/integrations/marketing-platforms/how-to-connect-batch-to-refiner.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.
