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.
Type
Server-side
Category
Identifiers sent
Mobile IDs, User account IDs, Device IDs
Authentication
Batch CEP Project key and REST API key, one pair per project
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
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.
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 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
Last updated
Was this helpful?