> ## Documentation Index > Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt > Use this file to discover all available pages before exploring further. # Cleverpush > Send audience identifiers out of Zeotap CDP to Cleverpush, where they arrive as a tag you can target in a web, app or email push campaign. The Cleverpush destination sends audience identifiers **out of Zeotap CDP** to your Cleverpush account, where each activated audience arrives as a Cleverpush tag you can target in a push campaign. To bring Cleverpush subscriber data **into** Zeotap CDP instead, use the [Cleverpush (Batch) Source](/articles/integrate-customer/cleverpush-batch-source) or the [Cleverpush Real-Time Source](/articles/integrate-customer/cleverpush-real-time-source). ## What this is Cleverpush is a web-based platform that lets website owners and developers send push notifications to users who have subscribed to receive them. Integrated with Zeotap CDP, it lets marketers engage their customers in real time and at scale, across mobile applications, websites and email. This page covers the **batch** Cleverpush destination, which you configure once per Cleverpush channel and then reuse for every audience you link to it. If you want to activate users from a Journeys workflow as they qualify rather than on a scheduled audience refresh, see [Cleverpush Real Time Integration](/articles/integrate-customer/cleverpush-real-time-integration) instead. ## Supported identifiers and actions This integration supports **Subscription ID**. The destination exposes a single action: | Action | ID Extension | Delete | Delta Upload | | - | - | - | - | | Send identifiers to Cleverpush | — | — | — | The action does not support [ID Extension](/articles/segment-customer/extend-your-audience#id-extension), [Delete or Delta Upload](/articles/segment-customer/delta-upload-and-delete-functions). ## Prerequisites Before you configure the destination, make sure you have the following: * **A Cleverpush source in Zeotap CDP.** The destination matches users on their Cleverpush Subscription ID, so that identifier has to already be present in Zeotap CDP. You get it either by connecting a Cleverpush source or by ingesting a flat file. * **Your Cleverpush Private API key.** Found in the Cleverpush console under **Settings > API**. See [Private API key](#private-api-key) below. * **The Channel ID of the push notification channel you want to send to.** Found in the Cleverpush console under **Channels > Platforms > General**. See [Channel ID](#channel-id) below. ## Get your Cleverpush credentials Gather both values from the Cleverpush console before you start the destination form in Zeotap CDP. ### Private API key A Private API key is a unique identifier associated with your Cleverpush account. Cleverpush uses it to authenticate and authorise access to certain features and APIs. Log into the Cleverpush console and navigate to **Settings**. In the left panel, click **API** and copy the **Private API key** shown on the screen. To restrict a key to particular channels, click **Add additional API key** and select the channels where you intend to use it. The API page in Cleverpush Settings, with the Generate new API key button, and the Additional API keys section with its Channels selector open. ### Channel ID A Channel ID is a unique identifier assigned to a push notification channel you create within Cleverpush. Log into the Cleverpush console and open **Channels** on the top navigation bar. Click the channel you want to send push notifications to. If it does not exist yet, create one by clicking **Add Channel** in the drop-down menu. For the full steps, see [Create a new channel in Cleverpush](/articles/integrate-customer/appendix-cleverpush-destination#create-a-new-channel-in-cleverpush). The Cleverpush dashboard with the Channels drop-down open, listing the most recent channels above the All channels and Add Channel entries. Set up the platforms you want to send notifications on. Zeotap CDP supports: * Web Push * App Push * Email Push For the setup steps for each platform, see [Setup Web Push](/articles/integrate-customer/appendix-cleverpush-destination#set-up-web-push-in-cleverpush), [Setup App Push](/articles/integrate-customer/appendix-cleverpush-destination#set-up-app-push-in-cleverpush) and [Setup Email Push](/articles/integrate-customer/appendix-cleverpush-destination#set-up-email-push-in-cleverpush). A Cleverpush channel's Basic settings panel above its Platforms panel, where each platform such as Web Push or App Push can be added or removed. Open the platform you want to use and go to **General > Advanced settings**. The **Channel ID** is the first row of that panel. The Advanced settings panel for a Web Push platform in Cleverpush, with the Channel ID row highlighted at the top, above Subdomain and the Firebase settings. ## Create the Cleverpush destination In the Zeotap CDP app, go to **Integrate > Destinations**. Click **+ Create Destination**. The Destinations listing page in Zeotap CDP, with the Create Destination button highlighted above the list of configured destinations. Under **All Destinations**, search for **Cleverpush**. The All Destinations catalogue in Zeotap CDP, with the search field highlighted above the grid of available destination cards. Click **Cleverpush**. The destination opens on the **Destination Details** step, with a description of the integration on the left and the configuration fields on the right. Fill in: a. **Destination Name** — a short, descriptive name that identifies the Cleverpush channel this destination sends to, so it is easy to find when you link an audience. b. **Private Key** — the Private API key you copied from the Cleverpush console. c. **Channel Id** — the Channel ID of the push notification channel you want to send to. d. Review the fields and click **Next**. To open the help documentation for this integration from inside the product, click **Integration Guide** under **Related Links**. The Destination Details step of the Cleverpush destination in Zeotap CDP, showing the Destination Name, Private Key and Channel Id fields with placeholder values, and the Integration Guide link under Related Links. On the **Mapping** step, choose the action and the field mapping: a. Under **Choose your Action**, select **Send identifiers to Cleverpush**. Then, under **Map the Fields**, map the catalogue field that holds each user's Cleverpush Subscription ID to the **Subscription Id** destination field. The [output identifiers](/articles/segment-customer/choose-the-output-identifiers) accepted by the platform are offered by default, and you can edit that selection so that only the identifiers you intend to send are mapped to **Subscription Id**. For more on how mapping works across destinations, see [Define the mapping](/articles/integrate-customer/destinations#define-the-mapping). b. Click **Create Destination**. The destination is now available in the Audiences application and can be linked to an audience. The Mapping step of the Cleverpush destination in Zeotap CDP, with Send identifiers to Cleverpush selected as the action and a catalogue field mapped to the Subscription Id destination field. ## Link an audience to the destination For the steps to link an audience to a created destination, see [Link an audience to the destination](/articles/integrate-customer/link-an-audience-to-the-destination). It can take up to two hours for the audience to become available in your Cleverpush seat. The terms *Audiences* and *Segments* are used interchangeably to refer to customer cohorts belonging to a specific category. For example, an audience or a segment could be a specific group of customers who are over 18 years of age and who have performed an `addToCart` event within the last 30 days. ## Verify the audience reached Cleverpush Confirm the delivery from both sides: 1. **In Zeotap CDP** — open the destination and review its activity. A successful delivery records a run with a non-zero qualified count and a completed status; a failed run records an error message. See [Verify the activation worked](/articles/integrate-customer/destinations#verify-the-activation-worked) for what to check, and [Why deliveries fail](/articles/integrate-customer/destinations#why-deliveries-fail) for the errors that surface on an audience–destination pair and what to do about them. 2. **In Cleverpush** — open **Create new**, select your channel, and open the **Tags** drop-down. The activated audience appears there as a tag. Selecting it updates the **Will be sent to** subscriber count shown alongside the target group, which tells you how many of your Cleverpush subscribers matched. The two counts will not match exactly, because Cleverpush only counts users it could match to an existing subscription, but both should be non-zero. ## Send a campaign to the audience in Cleverpush Log into the Cleverpush console and click **Create new**. The Cleverpush dashboard with Create new highlighted in the top navigation bar, above the clicks, opt-ins and growth summary tiles. In the **Channels** drop-down, choose the channel you created, matching the type of push notification you want to send. To create a new channel first, see [Create a new channel in Cleverpush](/articles/integrate-customer/appendix-cleverpush-destination#create-a-new-channel-in-cleverpush). The Create new page in Cleverpush with the Target group Channels drop-down open, listing each channel's Web Push, App Push and Email entries. Use the **Tags** drop-down to choose the audience you want to target. The **Will be sent to** count updates to show how many subscribers the selection reaches. The Target group panel of a new Cleverpush campaign, with the optional Tags drop-down open and highlighted, and Countries, Languages and Platforms filters on the right. Under **Message**, enter the headline and text of the push notification you want to send. A live preview of the notification appears alongside. Review all the fields and click **Send notification**. A completed Cleverpush campaign with a channel and a tag selected in the Target group and the Send notification button highlighted next to Discard and Save draft. ## Next steps * [Bring Cleverpush subscriber data into Zeotap CDP with the batch source →](/articles/integrate-customer/cleverpush-batch-source) * [Bring Cleverpush subscriber data into Zeotap CDP in real time →](/articles/integrate-customer/cleverpush-real-time-source) * [Activate from a Journeys workflow with the Cleverpush real-time integration →](/articles/integrate-customer/cleverpush-real-time-integration) * [Set up Cleverpush channels and platforms →](/articles/integrate-customer/appendix-cleverpush-destination) * [Understand how destinations work in Zeotap CDP →](/articles/integrate-customer/destinations) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.