Skip to main content
The Cleverpush Real-Time source brings data into Zeotap CDP: a Cleverpush channel posts subscriber and notification events to Zeotap over a webhook as they happen. To send data in the opposite direction — out of Zeotap CDP to Cleverpush — use the Cleverpush destination for audiences, or the Cleverpush Real Time Integration destination for Journeys workflows.

​
What this is

Cleverpush is a web-based platform that enables website owners and developers to send to users who have subscribed to receive them. Integrated with Zeotap, it enables marketers to engage with their customers in real time and at scale. This source fetches information related to the subscribers of a Cleverpush channel, such as the subscription ID, channel ID, created_at, country, custom attributes and segments. In the Zeotap CDP App it sits under the Customer Engagement Channels source category, alongside the other engagement platforms listed on Customer Engagement Channels. Cleverpush has two source integrations and two destination integrations, and their names are easy to confuse. Use this table to confirm you are on the right page:

​
Supported identifiers

The source brings in subscriber records from the Cleverpush channel it is connected to. The identifiers are:
  • Channel ID
  • Subscription ID
  • Subscription platform name (Subscription.platformName)
Alongside them, the payload carries subscription and notification attributes including Subscription.browserType, Subscription.createdAt, Subscription.syncedAt, Subscription.language, Subscription.country, Subscription.timezone, Subscription.customAttributes, Subscription.emailAddress, Subscription.optInIpAddress, Subscription.optInUrl, Subscription.topics, Notification.campaignId, Notification.campaignName, Notification.customData and Notification.feedGuid. Which of these actually arrive depends on the webhook events you select in Cleverpush when you configure the webhook. The Subscription ID is also the identifier the Cleverpush destination needs in order to send audiences back to Cleverpush. Connecting a Cleverpush source is one of the two documented ways to obtain it; the other is ingesting it from a flat file.
Although a country value appears in the Cleverpush payload, the records for the country and city columns are excluded from ingestion — Zeotap CDP resolves the country and the city from the user’s IP address instead. For the complete list, see Blacklisted fields for data ingestion.

​
Prerequisites

  • Access to the Sources application under Integrate in the Zeotap CDP App.
  • A Cleverpush channel with at least one platform set up on it. The webhook that feeds this source is configured per platform in Cleverpush, so the channel needs Web Push, App Push or Email Push configured before there is anywhere to add the webhook. For the channel-creation and platform-setup steps, see the Cleverpush appendix.
  • Access to the Webhooks settings of that platform in the Cleverpush console.
You do not need a Cleverpush Private API Key or Channel ID to create this source — those are asked for by the Cleverpush (Batch) Source. The real-time form asks only for a name, a region and a data entity. Authentication runs the other way round here: Cleverpush authenticates to Zeotap using the write key that Zeotap generates when the source is created. Treat that write key as a secret — copy it straight into the Cleverpush webhook rather than pasting it into a ticket, an email or a shared document.

​
Create the Cleverpush Real-Time source

Setting this source up takes two stages, one on each side of the integration. Each stage has its own page:
1

Create the source in Zeotap CDP

Create the source under Sources, choosing Customer Engagement Channels as the category and Cleverpush Real-Time as the data source, then enter a name, select a Region and choose the Data Entity. On successful creation, an API URL and a Write Key are generated and appear under the source’s IMPLEMENTATION DETAILS tab. Both are needed for the next stage.See Create a Cleverpush Real-Time Source.
2

Configure the webhook in Cleverpush

In the Cleverpush console, open the channel and the platform you want to stream from, and add a webhook of Type Custom. Enter the API URL as the Webhook URL, supply the Write Key as the Authorization Header Value, choose the webhook events you want to send to Zeotap, and save.See Implement a Cleverpush Real-Time Source.

​
Verify the source is receiving data

Open the source from the SOURCES listing page and check its status:
  • Created — the source exists but has not received any data yet. If it stays here, check that the webhook in Cleverpush is saved and uses the API URL and Write Key from the IMPLEMENTATION DETAILS tab, and that the events you expect are selected.
  • Integrated — data has started flowing in. You can now preview the incoming records on the PREVIEW DATA tab of the source.
For what each status means, see Components of the Source Listing Page; for how to read the sample, see Components of the Preview Data Tab.

​
Next steps

Create a Cleverpush Real-Time Source

Create the source in Zeotap CDP and collect the API URL and Write Key.

Implement a Cleverpush Real-Time Source

Configure the webhook in Cleverpush and choose the events to stream.

Cleverpush (Batch) Source

The other way to bring Cleverpush subscriber data into Zeotap CDP.

Cleverpush destination

Send an audience from Zeotap CDP out to Cleverpush.
Last modified on September 24, 2026