CDP platform · 1 of 44 in the CdpHub directory
Zeotap integrations
CdpHub documents 163 listings from Zeotap's catalog, covering 90 distinct tools. 137 of those listings send data from Zeotap to a tool, 25 use a tool as a source and 1 moves data both ways. 147 can run server-side, 3 client-side and 13 in the warehouse. Every listing links to Zeotap's own documentation.
Jump to a category
Advertising
58 listings · 36 tools · the 6 most widely listed firstMeta Ads (custom audiences, OAuth). Activates Zeotap audiences as Custom Audiences in a Facebook ad account after a one-time OAuth sign-in rather than a pasted access token, for targeting or suppression in Meta campaigns.
Meta Ads (custom audiences). Pushes Zeotap segments into Meta as Custom Audiences, matched on hashed emails or phones, MAIDs or external IDs, using a System User or Page access token, and removes users who drop out.
Meta Ads (MAID audiences). Sends Zeotap audiences of mobile advertising IDs to a Facebook ad account linked to Business Manager for targeting, once the Custom Audience terms have been accepted.
Meta Ads (offline conversions). Sends offline conversions, such as in-store purchases or offline leads, with hashed customer identifiers from Zeotap audiences to Meta for better ad attribution and optimization.
Meta Ads (product catalog). Sends Zeotap product records, such as IDs, titles, prices and availability, into a Facebook Product Catalog held in Commerce Manager, so dynamic ads can promote them.
Google Ads. Sends hashed first-party data, such as emails and transaction IDs, from Zeotap Journeys to Google Ads enhanced conversions, for more accurate conversion tracking and bidding.
TikTok (audiences). Sends Zeotap custom audiences of emails, E.164 hashed phone numbers and MAIDs into a TikTok ad account using TikTok's Marketing API, refreshing them on every scheduled sync.
TikTok (Events API). Forwards conversion and event data from Zeotap Journeys to TikTok's Events API server to server, with hashed emails, phones and external IDs or click IDs, for better attribution.
Microsoft Advertising (Conversions API). Forwards conversion and event data from Zeotap Journeys to Microsoft Advertising's Conversions API through its UET tag, with hashed emails or phones, click IDs and other user data.
Microsoft Advertising (Customer Match). Sends Zeotap audiences of SHA-256 hashed emails to Microsoft Advertising as customer match lists for Search and Audience Network targeting, authorized with a developer token and OAuth.
Show the other 30 Advertising toolsShowing all 36 Advertising tools
Criteo (audiences). Sends Zeotap audiences of MAIDs, raw or hashed emails and Criteo cookies to a Criteo ad account as a contact list, removing users who no longer qualify.
Criteo (offline sales). Sends offline transactions, such as in-store or call center sales, from a Zeotap journey to Criteo, which matches them to ad interactions to report campaign impact.
Criteo (Retail Media). Sends Zeotap audiences of raw or hashed emails and logged-in customer IDs to Criteo Retail Media, to target shoppers with ads on retailer and marketplace sites and apps.
Pinterest (Conversions API). Sends conversion events with SHA-256 emails, MAIDs and phone numbers from Zeotap Journeys to the Pinterest Conversions API server to server, to measure campaign impact and improve ad targeting.
Pinterest (customer lists). Sends Zeotap audiences of SHA-256 hashed emails and MAIDs to a Pinterest ad account as Customer Lists for targeting, removing users who no longer qualify.
The Trade Desk (audiences). Sends Zeotap audiences of MAIDs, TTD cookies, EUID or netID to The Trade Desk as a partner, advertiser or system org, so TTD campaigns can target those users.
The Trade Desk (CRM data). Sends raw or hashed emails and phone numbers from Zeotap to a Trade Desk advertiser through the CRM Data Platform API, for consented targeting based on EUID.
The Trade Desk (data monetization). Publishes Zeotap audiences as buyable third-party segments in The Trade Desk's data taxonomy, each carrying a CPM plus a percent-of-media rate, matched on TTD cookies, mobile ad IDs and ID5.
The Trade Desk (first-party data). Publishes Zeotap audiences into your own Trade Desk advertiser account as first-party segments, using the advertiser's secret key, for targeting on TTD-bought inventory.
Amazon Ads (Conversions API). Forwards conversion events from Zeotap Journeys to Amazon DSP through the Amazon Conversions API, server to server, with SHA-256 hashed emails, phones, MAIDs and names as match keys.
Amazon Ads (DSP advertiser audiences). Pushes Zeotap audiences into Amazon DSP's Advertiser Audiences as first-party segments, authorized through an Amazon sign-in, for North America or Europe accounts.
Amazon Ads (DSP segments). Sends Zeotap audiences of Zeotap cookies for Amazon and MAIDs into an Amazon DSP advertiser account as custom segments, adding Amazon's consent signal for EEA and UK users.
Amazon Ads (Marketing Cloud). Sends pseudonymized Zeotap segments with hashed emails and phone numbers, names and addresses to Amazon Marketing Cloud audiences through a connection ID, for clean room insights and targeting.
Reddit (Conversions API). Passes conversion events with SHA-256 emails and phone numbers from Zeotap Journeys to Reddit's Conversions API, set up with a Reddit pixel ID and API token.
Reddit (customer lists). Exports Zeotap segments of raw or hashed emails and MAIDs as CSV files to your Amazon S3 bucket, which you then upload to Reddit Ads as a customer list audience.
Reddit (offline conversions). Sends offline conversions with SHA-256 emails and phone numbers for a linked Zeotap audience to Reddit through a pixel ID and API token, for events up to a week old.
Meta Conversions API. Streams web and app conversion events, such as purchases, sign-ups and page views, from Zeotap Journeys to Facebook's Conversions API, with event IDs to deduplicate against the Pixel.
Google Ad Manager. Sends Zeotap audiences keyed on publisher provided IDs (PPIDs), raw or encrypted, to Google Ad Manager, passing Google's EEA consent signals as granted.
Adform (DMP). Uploads Zeotap audiences of MAIDs, Adform cookies and ID5 into an Adform DMP account through OAuth API credentials from Adform, for use in programmatic campaigns.
Adform (segments). Pushes Zeotap segments of MAIDs and Adform cookies to Adform, either private to an agency and its advertisers in a country or open to all, with ID extension and deletes.
StackAdapt. Pushes Zeotap audiences of MAIDs, IP addresses and StackAdapt cookies to an S3 bucket provided by StackAdapt for its programmatic DSP, under your 3P Marketplace advertiser ID.
Google Customer Match (contact information). Sends Zeotap audiences of hashed emails and phone numbers to Google Customer Match, to reach known customers through Google Ads or DV360 on Search, Gmail, YouTube and Display.
Google Customer Match (mobile device IDs). Uploads Zeotap audiences of IDFA or AAID mobile ad IDs to Google Customer Match as customer lists for Google Ads or DV360, with removals on each audience refresh.
Google Marketing Platform (DDP). Creates Zeotap segments of MAIDs and Google cookies as third-party data in a client's DV360 or DoubleClick for Publishers seat through Google DDP, with lookalike extension for DV360.
Google Marketing Platform (DMP). Creates Zeotap segments of MAIDs and cookies in a client's Google Ad Manager or DV360 account once Google pairs the Zeotap DMP with that account, for ad targeting.
PubMatic (audiences). Delivers Zeotap segments of PubMatic cookies, MAIDs, IDP Base or ID5 IDs to a PubMatic publisher, demand partner or buyer account for programmatic targeting.
PubMatic (Publisher). Uploads Zeotap audience identifiers to a PubMatic publisher seat identified by a data provider ID, making the segment ready for programmatic monetization.
RTB House (audiences). Sends Zeotap audiences of RTB House cookies to an S3 bucket provided by RTB House for retargeting, once cookie syncing with RTB House is enabled.
RTB House (Conversions API). Sends real-time events such as product views, add-to-cart actions and orders from Zeotap Journeys to the RTB House Conversions API, keyed on RTB House cookies.
Active Agent. Pushes Zeotap segments to an Active Agent DSP instance, keyed on IDs such as Android or iOS ad IDs, ID5, NetID or UTIQ, using an attribute Zeotap support sets up for your Adition network.
Comcast EntOS. Pushes Zeotap audiences tied to device or account IDs to Comcast EntOS, with a bearer token built from Comcast client credentials, for set-top box targeting and personalization.
Sportradar. Hands a Zeotap audience to Sportradar as user IDs that its advertising arm treats as a suppression list, so those users are left out of targeting.
Email & Marketing Automation
41 listings · 20 tools · the 6 most widely listed firstBraze (audiences). Writes Zeotap segment membership onto Braze user profiles as attributes through the Braze REST API, since Braze segments can't be set directly, and can rename or remove external IDs.
Braze (real-time). Sends profile attributes, custom events and purchases from Zeotap Journeys to Braze through its user track API, so Braze can personalize messages and trigger campaigns.
Braze (Currents source). Streams Braze engagement events into Zeotap through Braze Currents as batched JSON payloads sent to a Zeotap endpoint, set up with help from your customer success manager.
Salesforce Marketing Cloud (Data Extension). Writes any Zeotap audience identifiers and attributes into a Salesforce Marketing Cloud data extension, set up with an installed package, for segmentation and targeted campaigns.
Salesforce Marketing Cloud (Journey Builder). Sends identifiers and custom attributes from Zeotap Journeys in real time into an SFMC data extension that serves as an entry source for Journey Builder campaigns.
Iterable (audiences). Triggers pre-built Iterable API-triggered campaigns, or updates a subscriber list, for the users in a linked Zeotap audience, using an Iterable API key and data center.
Iterable (real-time). Triggers an Iterable API-triggered campaign or updates a subscriber list as each customer reaches a Send to Destinations node in a Zeotap journey.
Airship (real-time destination). Sends events from Zeotap Journeys to Airship, with event name, timestamp, transaction and value, matched on a named user or an iOS, Android or web channel ID.
Airship (static lists). Sends Zeotap audiences of Airship named users to Airship as static lists, using an Airship access token with audience modification rights and your account region.
Airship (batch source). Retrieves Airship user IDs and attributes, including Android and iOS channel IDs, into Zeotap in batches to unify profiles and target push notification campaigns.
Airship (real-time source). Brings Airship data into Zeotap through Airship's Real-Time Data Streaming, so marketers can reach customers across channels as events happen and at scale.
Oracle Eloqua. Triggers pre-built Oracle Eloqua emails from a Zeotap journey through Eloqua's Email Deployment API, using a profile attribute that holds each person's Eloqua contact ID.
Show the other 14 Email & Marketing Automation toolsShowing all 20 Email & Marketing Automation tools
Emarsys (batch). Adds Zeotap audience contacts to Emarsys contact lists or sends them as triggered events through the Emarsys API with WSSE credentials, while the old identifiers-only action is deprecated.
Emarsys (real-time). Records customer events such as cart abandonment in Emarsys from Zeotap Journeys in real time, with profile fields, so follow-up messages can go out right away.
Emarsys (source). Pulls Emarsys email engagement data into Zeotap through the Emarsys API, first requesting campaign responses such as opens, clicks or bounces and then the matching contacts.
Oracle Responsys (batch). Inserts or updates Zeotap audience records in an Oracle Responsys profile list or profile extension table, matched on columns you choose, with emails, IDs and custom attributes.
Oracle Responsys (real-time). Triggers Oracle Responsys email campaigns from Zeotap Journeys, either to existing recipients or after merging new recipients into a profile list, through the Responsys trigger APIs.
Dotdigital (destination). Sends Zeotap audiences of raw email addresses to Dotdigital through an API user tied to your account's region, with ID extension and removal of users who leave.
Dotdigital (source). Fetches customer data from Dotdigital into Zeotap through REST API calls and ingests the JSON responses, for segments and personalized cross-channel campaigns.
MoEngage (audiences). Syncs Zeotap audiences into MoEngage segments through the Cohort Sync API, matching only users already in MoEngage by user ID and not removing users who leave.
MoEngage (real-time). Creates or updates MoEngage user profiles and sends user events from Zeotap Journeys in real time, keyed on a customer ID, for personalized MoEngage campaigns.
MoEngage (source). Streams MoEngage engagement events into Zeotap continuously through MoEngage Streams, which posts them to an API URL with a write key that Zeotap issues.
Adobe Campaign (batch). Exports Zeotap segments of raw emails and custom IDs as CSV files to your Amazon S3 or Azure storage, which Adobe Campaign then imports for email, mobile and social campaigns.
Adobe Campaign (real-time). Sends raw emails and custom IDs from Zeotap Journeys to Adobe Campaign through your S3 or Azure storage, with optional batching that groups the data by size or time before sending.
Brevo (lists). Delivers Zeotap audiences to Brevo, formerly Sendinblue, as contact lists inside a folder you name, using raw email addresses and custom contact attributes.
Brevo (real-time). Appends contacts to a Brevo contact list from a Zeotap journey as customers reach it, matched on raw email, with names, phone and custom Brevo attributes.
Bloomreach. Pushes Zeotap audience segments into Bloomreach Engagement, formerly Exponea, through its API, so Bloomreach can send personalized email, SMS or push campaigns to those users right away.
Batch (audiences). Sends custom audiences of advertising IDs, install IDs or custom user IDs from Zeotap to Batch, and can push attributes such as names and email, with Batch's Live and REST API keys.
Batch (CEP). Creates named audiences in Batch CEP from Zeotap segments, or keeps attributes, topic preferences and events current on existing Batch profiles, with a REST API key and project key.
Batch (real-time). Sends user traits, events and custom audiences from Zeotap Journeys to Batch with its Live and REST API keys, for push or in-app automations triggered by those events.
Batch (source). Brings Batch user data with install, advertising and custom IDs into Zeotap as JSON or CSV files on a daily, weekly or monthly sync, using Batch's Live and REST API keys.
Optimizely Campaign. Sends raw email recipient IDs and chosen attributes from Zeotap Journeys to Optimizely Campaign through API credentials from its support team, to trigger email campaigns.
Bird (customer lists). Pushes Zeotap audiences into customer lists in a Bird workspace with raw emails, phone numbers and custom attributes, authorized by a Bird access key, for Bird campaigns.
Bird (trigger events). Forwards events in the categories you choose, such as audience or ecommerce events, from a Zeotap journey to a Bird workspace, identifying contacts by email or phone.
Inxmail. Creates an Inxmail mailing list from a Zeotap audience, or fills an existing one, importing members as recipients with mapped fields through Inxmail OAuth client credentials.
Inxmail (real-time). Sends event-triggered transactional emails through the Inxmail Commerce API, and list subscriptions through the Professional API, from Zeotap Journeys.
ELAINE. Sends Zeotap audiences with emails, names, gender and custom fields to artegic ELAINE as recipient groups, transferring files over ELAINE's SFTP and setting up groups through its API.
ELAINE (real-time). Sends event data from Zeotap Journeys to artegic ELAINE through its API, matched on customer email, to trigger the events and campaigns defined in ELAINE.
Hello Charles. Upserts contacts from Zeotap audiences into Hello Charles, with tags and custom properties, for WhatsApp and conversational commerce, through a Batched Contacts API in closed beta.
Data Infrastructure
20 listings · 10 tools · the 6 most widely listed firstSnowflake (destination). Sends Zeotap audience and journey data toward Snowflake through your Google Cloud Storage bucket, in batches or streamed with Pub/Sub notifications that trigger loading.
Snowflake (source). Loads customer data from Snowflake into Zeotap through a direct connection made in the Sources app, refreshed automatically at the sync frequency you pick.
Amazon S3 (destination). Exports Zeotap audiences to a folder in your Amazon S3 bucket as CSV files, with MAIDs, hashed emails or phones and CRM IDs, or any identifiers and attributes.
Amazon S3 (source). Imports customer data kept in your own Amazon S3 account into Zeotap, with an automatic sync at the frequency you set keeping it up to date.
BigQuery (Analytics Hub). Shares Zeotap's unified profile store, with profile, consent, ID and campaign data, with your service accounts through a private BigQuery Analytics Hub listing you subscribe to.
BigQuery (destination). Sends Zeotap segments with any identifiers and attributes into a BigQuery project, dataset and table, with a Google Cloud Storage bucket and folder also set up for the transfer.
BigQuery (source). Connects Zeotap directly to data held in Google BigQuery and syncs it in as a source for building customer segments, personalized content and ad targeting.
Google Cloud Storage. Delivers Zeotap audiences to a folder in your own Google Cloud Storage bucket as CSV files, with identifiers alone or with attributes, through a Zeotap or client service account.
Databricks (destination). Activates Zeotap audiences into Databricks Delta tables by writing JSON files to your Google Cloud Storage bucket, which Databricks Autoloader loads into the table you name.
Databricks (source). Pulls records from a Databricks table into Zeotap on a schedule, over JDBC with OAuth for smaller tables or a job-based connection advised above one million records.
SFTP (destination). Writes each linked Zeotap audience as CSV or JSON files into a folder on your own SFTP server, signing in with a password or Zeotap's SSH key, with optional PGP encryption.
SFTP (source). Pulls data files into Zeotap from an SFTP folder on your own server at the sync frequency you choose, signing in with a password or SSH keys and optionally taking only new files.
Show the other 4 Data Infrastructure toolsShowing all 10 Data Infrastructure tools
Azure Blob Storage. Writes Zeotap audiences as complete CSV files into a container and optional folder in your Azure Blob Storage account, connecting with the storage account's connection string.
Kafka (destination). Streams event data from Zeotap Journeys into a topic in your Apache Kafka cluster in real time, authenticating to the broker with an API key and secret.
Kafka (source). Consumes messages from an Apache Kafka topic into Zeotap through a consumer group, in AVRO or JSON format, so real-time customer behavior can drive journeys.
Microsoft Fabric (destination). Writes Zeotap audience identifiers and attributes into a Microsoft Fabric Lakehouse table as JSON, staged in a Google Cloud Storage bucket and appended by a Fabric Spark job.
Microsoft Fabric (source). Pulls a table or view from a Microsoft Fabric warehouse into Zeotap daily, weekly or monthly, connecting over SQL with a service principal that has read access.
Google Pub/Sub (destination). Publishes data from Zeotap Journeys to a Google Pub/Sub topic in your project, authenticating with a refresh token or a service account.
Google Pub/Sub (batch source). Brings batched messages from a Google Pub/Sub topic into Zeotap as flattened JSON, through a subscription a Zeotap service account attaches once your Zeotap contact sets up storage access.
Google Pub/Sub (stream source). Consumes JSON messages your application publishes to a Google Pub/Sub topic, one at a time as they arrive, through a subscription Zeotap attaches using its own service account.
7 more categories
Open one to see its toolsPersonalization & Testing
17 listings
Salesforce Marketing Cloud (Personalization audiences). Sends user profile objects with any attributes from Zeotap audiences to Salesforce Marketing Cloud Personalization, formerly Interaction Studio, as files over an SFMC SFTP account.
Salesforce Marketing Cloud (Personalization journeys). Sends user profile objects for people who qualify for a Zeotap journey to Salesforce Marketing Cloud Personalization, mapped to a dataset's catalog objects, for personalized targeting.
Optimizely (batch). Sends Zeotap audiences of Optimizely IDs to Optimizely through its REST APIs with an access token, so its web campaigns can personalize the experience for those visitors.
Optimizely (real-time). Sends users who qualify for a Zeotap journey to Optimizely Data Platform via its REST APIs, keyed on the Optimizely ID cookie, for real-time segments in Optimizely Web and Full Stack.
Adobe Target (Bulk Profile Update). Updates many Adobe Target visitor profiles at once from Zeotap audiences through the Bulk Profile Update API, keyed on mbox 3rd-party IDs or PCIDs, to add or remove them from activities.
Adobe Target (Delivery API). Sends ECIDs, session IDs and attributes from Zeotap Journeys to Adobe Target's Delivery API with a property token, for real-time personalized web, mobile and email experiences.
Adobe Target (Single Profile Update). Updates one Adobe Target profile at a time from Zeotap Journeys through the Single Profile Update API, streaming profile properties keyed on mbox 3rd-party IDs.
Dynamic Yield (CSV upload). Uploads Zeotap segments as CSV files to the Amazon S3 location of a Dynamic Yield user data feed, a method meant for sending large volumes of hashed emails, MAIDs or attributes.
Dynamic Yield (Events API). Sends add-to-cart, remove-from-cart, login, signup and purchase events from Zeotap Journeys to Dynamic Yield's Events API, keyed on hashed email, phone or DYID.
Dynamic Yield (real-time). Streams the Journey ID, with hashed email, MAIDs or other attributes, from Zeotap to a Dynamic Yield user data feed as soon as a user qualifies, to personalize on-site experiences.
Dynamic Yield (User Data API). Updates a Dynamic Yield user data feed from Zeotap segments through its User Data API, with hashed emails, MAIDs, membership IDs and custom attributes, suited to small user counts.
Insider (destination). Sends audience attributes and identifiers in batches, and Journeys events in real time, from Zeotap to Insider's Unified Customer Database through its Upsert API with an API key.
Insider (webhook source). Streams the Insider events you choose, such as pageviews, cart actions and email, push, WhatsApp or SMS events, into Zeotap in real time through a webhook built in Insider.
LaunchDarkly (batch). Sends Zeotap segments of custom IDs, such as user or CRM IDs, to LaunchDarkly through an API access token so feature flags and experiments can target them.
LaunchDarkly (real-time). Sends Zeotap users from Journeys into LaunchDarkly segments in real time with an access token and client-side ID, so feature flags can target them.
Personyze (batch). Sends Zeotap audiences with emails, custom IDs, names, phone and industry to Personyze as a visitor attribute that Personyze campaigns can target.
Personyze (real-time). Sends event data or profile fields from Zeotap Journeys to Personyze as customers move through a workflow, so it can tailor web content, recommendations and offers.
CRM & Sales
6 listings
Salesforce (batch). Sends Zeotap audience data into Salesforce objects such as contacts, accounts, leads, cases, opportunities, tasks, campaigns or custom objects, after a sign-in on your Salesforce domain.
Salesforce (real-time). Upserts Salesforce contact or custom object records from Zeotap Journeys in real time, through an API user and an external ID field on the target object.
Salesforce (source). Syncs standard and custom Salesforce CRM objects, such as accounts, contacts and leads, into Zeotap daily, weekly or monthly through a connected app, keeping user IDs for matching.
HubSpot (destination). Creates HubSpot contacts from Zeotap profiles and adds their email addresses to HubSpot contact lists that mirror Zeotap audiences, after you connect your HubSpot account.
HubSpot (source). Imports HubSpot contacts or companies into Zeotap with a private app token, reading only the chosen fields and refreshing on a schedule with full or changes-only fetches.
Microsoft Dynamics. Imports the Dynamics 365 CRM entities you name, such as accounts, campaigns or cases, into Zeotap in batches through an app registered on the Microsoft side.
Analytics & BI
5 listings
Google Analytics. Sends Zeotap audience membership to a GA4 web property as zeotap_event custom events through the Measurement Protocol, so GA4 audiences built on them can be used in Google Ads.
Adobe Analytics. Sends Zeotap audiences keyed on Adobe Analytics cookies to an Adobe Analytics report suite, set up with the report suite ID, namespace and Experience Cloud org ID.
Looker Studio. Writes Zeotap audiences as CSV files into your Google Cloud Storage bucket, which Looker Studio then reads through its Cloud Storage connector for dashboards and reports.
Mobile & Push
5 listings
CleverPush. Sends Zeotap audiences to CleverPush as a tag on subscription IDs, which you can target in web, app or email push campaigns on that channel.
CleverPush (real-time destination). Sends subscription IDs, names, gender, email and custom fields from Zeotap Journeys to CleverPush for each user as they move through a workflow, to trigger web, app or email push notifications.
CleverPush (batch source). Fetches subscriber details from a CleverPush channel, such as subscription and channel IDs, country, custom attributes and segments, into Zeotap with a private API key.
CleverPush (real-time source). Receives CleverPush subscriber and notification events in Zeotap as they happen, posted by a custom webhook on the channel that authenticates with a Zeotap write key.
Developer Tools & APIs
4 listings
Google Tag Manager (ID+ tag). Adds the Zeotap ID+ tag from the Google Tag Manager template gallery, hashing a visitor's email or phone at login to fetch their ID+ cookie, which is then handed to Prebid.
Google Tag Manager (Collect Tag). Adds the Zeotap Collect Tag to websites as a Google Tag Manager custom template that reads a flattened data layer and sends events and user details to Zeotap asynchronously.
Adobe Experience Platform Tags. Deploys Zeotap's Collect Tag Extension through Adobe Experience Platform tags to record site events and user identities in Zeotap, and to sync cookies on the web.
E-commerce
4 listings
Talon.One (audiences). Adds Zeotap customer profile IDs to Talon.One audiences or removes them in batches, creating missing profiles, to keep promotion and loyalty campaigns on target.
Talon.One (custom events). Triggers custom events in Talon.One from a Zeotap journey, keyed on profile ID and event name, so customer actions in a journey can set off promotion and loyalty rules.
Channable. Delivers Zeotap audience data as CSV files to your own Google Cloud Storage bucket, from where you import them into Channable's feed management platform.
Channable (real-time). Pushes product stock updates from a Zeotap journey into a Channable project, feeding the stock data Channable keeps in sync with marketplaces.
Identity & Enrichment
3 listings
Integration catalog breadth
Distinct tools documented per platform: the five largest of 44, then Zeotap and its neighbours. Breadth counts what a catalog lists; it says nothing about how deep, current or well-built each connector is.
- 1Tealium636
- 2Segment (Twilio)459
- 3Klaviyo395
- 4Hightouch296
- 5ActionIQ (Uniphore)293
- 18Blueshift91
- 19Zeotap90
- 20BlueConic88
Related CdpHub research
Independent analysis by Ed Thomas, built on the same directory data.
Integration intelIntegration Coverage Report: October 2026Oct 2026 · 8 min readPlatform reviewCDP Market Landscape 2026Oct 2026 · 14 min readResearch reportCDP Vendor Evaluation FrameworkOct 2026 · 6 min readAbout these numbers
CdpHub documents each integration from the platform's own catalog and records which way data flows and where the integration runs. A tool can appear several times when a platform lists more than one connector for it, so listings can outnumber tools. A listing that runs in more than one mode counts in each, so the mode counts can add up to more than the listings. "Listed on 38 of 44 CDPs" counts every platform in the directory that lists the tool; the listing count beside it is Zeotap's alone. Counts are updated as catalogs change; this page reflects the directory as of October 17, 2026. CdpHub is independent and not affiliated with Zeotap.
Evaluating or implementing Zeotap?
Vendor-neutral help choosing between Zeotap and the other 43 platforms, and getting the integrations above running in your stack.