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

# Batch CEP

Send audiences to the Batch Customer Engagement Platform, to use in engagement and activation workflows.

The Batch CEP connector sends your audiences to the Batch Customer Engagement Platform, so a segment built in mediarithmics can be used in Batch engagement and activation workflows. It can create audiences in Batch CEP and keep them up to date by adding and removing users.

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Server-side</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/esp-and-marketing-automation.md">ESP &#x26; marketing automation</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>Mobile IDs, User account IDs, Device IDs</td></tr><tr><td><strong>Authentication</strong></td><td>Batch CEP Project key and REST API key, one pair per project</td></tr></tbody></table>

## Description

### What is Batch CEP?

The Batch Customer Engagement Platform helps brands manage and activate user audiences across their engagement channels.

With Batch CEP, you can:

* Create and manage user audiences.
* Use those audiences for customer engagement campaigns.
* Add or remove users from audiences through API-based workflows.
* Manage data at project level, with one authentication context per Batch project.

### What you can do with this connector

* Create a Batch CEP audience from a mediarithmics segment.
* Update an existing audience by adding or removing users as the segment changes.
* Activate into several Batch projects, each configured separately.

### Which identifiers are sent

When you share a segment through this connector, mediarithmics sends:

* **Mobile IDs**
* **User account IDs**
* **Device IDs**

{% hint style="warning" %}
The identifier type used for the audience must match the audience configuration in Batch CEP. A mismatch produces an audience that resolves to nobody.
{% endhint %}

## Connector setup

### Prerequisites

* Access to the **Batch CEP platform**.
* A **Batch CEP project**.
* The **REST API key** and **Project key** for the Batch CEP project you want to use.
* Access to the mediarithmics platform.

Each Batch CEP project has its own REST API token. The connector operates at project level, so one project is one authentication context.

### Authentication

The connector authenticates with a **REST API key** and a **Project key**, both retrieved from the Batch CEP platform. Batch documents where they come from in its [project APIs reference](https://doc.batch.com/developer/api/cep#using-project-apis).

One REST API token is required per Batch CEP project. To activate audiences in several Batch projects, configure each project with its own token.

Authentication is **self-service**: you retrieve the pair from Batch and set it on the connector yourself, with no exchange through your account manager.

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## FAQ

#### Do I need a Batch CEP account?

Yes. You need access to Batch CEP and to the Batch project where the audience will be created or updated.

#### How is authentication performed?

With a REST API token retrieved from the Batch CEP platform. The connector uses it to authenticate its API calls to Batch CEP.

#### Is one token enough for all my Batch projects?

No. Authentication is project-based, and each Batch project has its own REST API token. If you use several projects, configure each one separately.

#### Do I need my account manager to set this up?

No. This connector is self-service. Retrieve the REST API key and Project key from Batch CEP and set them on the connector yourself.

#### Which identifier should I select?

Whichever one the target audience is configured for in Batch CEP. The connector can send mobile IDs, user account IDs and device IDs, but the type has to match on the Batch side.

## Partner documentation

Batch documents its own platform at <https://doc.batch.com/>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>ESP &#x26; marketing automation</strong></td><td>What these platforms need from your CDP, and every mediarithmics connector that reaches one.</td><td><a href="/connectors/partner-types/esp-and-marketing-automation.md">ESP &amp; marketing automation</a></td></tr><tr><td><strong>Getting started</strong></td><td>Every documented connector, by partner type and by name.</td><td><a href="/connectors/readme.md">Getting started</a></td></tr></tbody></table>


---

# 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.mediarithmics.io/connectors/destinations/batch.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.