How to get ready to migrate from the Batch MEP to the CEP?

Follow these steps to prepare your upgrade from the Batch Mobile Engagement Platform (MEP) to the Batch Customer Engagement Platform (CEP).

The Customer Engagement Platform (CEP) provides enhanced capabilities, improved performance, and a more powerful approach to managing your customer engagement strategies. Ensuring these prerequisites are met will facilitate a smooth transition and enable you to leverage the full potential of the Batch CEP.

1. SDK version

The Batch CEP relies on newer versions of the Mobile and Web SDKs to support its advanced features and ensure optimal performance.

2. Tagging plan: cross-platform matching

When migrating to the CEP, your apps and websites will be grouped into omnichannel projects. Data must be consistent across the different apps and websites to ensure omnichannel features work smoothly.

An omnichannel project can contain a maximum of 1 Android app, 1 iOS app, and 1 website.

3. APIs

To ensure full compatibility with the CEP, apply the adjustments detailed below to the MEP APIs you are currently using.

Transactional & Partner APIs

If you are using the Transactional API (or its variant, the Partner API), we recommend switching from the Transactional API to the Profile API. This will especially allow your marketing teams to edit the content of these transactional messages without relying on your back-end teams.

This option is not applicable yet if you are targeting Installation IDs with the Transactional API. It will be available soon.

Campaigns API

In-app Campaigns API

Custom Audience API

This option is not applicable if you are sending Installation IDs with the MEP Custom Audience API. In this case, contact us so that we can review your needs and define the best approach together.

Custom Data API

The Custom Data API is fully compatible with the CEP, except in one specific case: if you are using the overwrite: true parameter, API calls are skipped for the data integration into the CEP.

App Data API

GDPR API

The GDPR API is fully compatible with the CEP, without any additional action on your side.

Export API

Webhooks

Trigger Events API

The Trigger Events API is fully compatible with the CEP, without any additional action on your side.

4. Additional features

Custom Exports

You may have set up custom exports to receive files from Batch on external storage that you manage (such as SFTP, S3, AWS, etc.).

There are two types of exports:

  • Userbase exports: These are fully compatible with the CEP.

CSV audience importer

You may have requested from Batch to set up a custom script to import audiences from files that you drop on external storage that you manage (such as SFTP, S3, AWS, etc.).

Editorial Dashboard

5. Third-party integrations

You may have configured connections between Batch and our partners' solutions (Analytics, CDP, etc.).

Event dispatchers (used to connect the Batch mobile SDK with external Analytics tools) are compatible with the CEP, without any additional action on your side.

Next Steps

Once you have performed the necessary checks and updates:

  1. Test: After making changes, especially SDK updates and data format adjustments, test your app extensively. Pay close attention to data collection across all relevant platforms (iOS, Android, Web).

  2. Inform us: Reach out to us to confirm that you have completed the prerequisite actions, and we will work with you to schedule the migration of your account to the CEP.

If you have any questions about any of the steps outlined above, feel free to reach out to us via your dedicated Customer Success Manager or support@batch.com.

Last updated

Was this helpful?