# What are the differences between Push v1 and Push v2?

In this documentation or when collaborating with the Batch team, you may hear the wording “Push v1” and “Push v2”, and by extension, “Mobile Landing v2”, “Imported tokens v2”, “Event targeting v2”, etc.

### What does push v1 mean?

In Batch Customer Engagement Platform (CEP), Push v1 is the way we call the **capabilities that can be used in Batch Customer Engagement Platform (CEP) and are also historically available in the Mobile Engagement Platform (MEP)**. By extension, all the features related to Push v1 get this v1 name add-on. For example: Mobile landing v1, Retargeting v1, etc.

### What does push v2 mean?

In Batch Customer Engagement Platform (CEP), Push v2 is the way we call the **capabilities that are new and enhanced versions of capabilities that were existing in the Mobile Engagement Platform (MEP).**

Retargeting, Mobile Landing, Audiences, Imported tokens, etc., are all features that we drastically improved in the Customer Engagement Platforms compared to what exists in the Mobile Engagement Platform. Hence, they get this “v2” add-on on their name.

### Why can Push v1 and Push v2 coexist?

Customers are migrating from the MEP to CEP thanks to the seamless migration paths proposed by Batch. They will thus have in the CEP some historical orchestrations running with Push v1. Progressively, they will leverage more and more v2 capabilities and fewer and fewer v1 capabilities.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.batch.com/getting-started/other/faq/what-are-the-differences-between-push-v1-and-push-v2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.