CDP platform · 1 of 44 in the CdpHub directory
Chord integrations
CdpHub documents 86 listings from Chord's catalog, covering 59 distinct tools. 64 of those listings send data from Chord to a tool and 22 use a tool as a source. 43 can run server-side, 35 client-side and 9 in the warehouse; some run in more than one mode. Every listing links to Chord's own documentation.
Jump to a category
Advertising
29 listings · 19 tools · the 6 most widely listed firstMeta Ads (custom audiences and conversions). Syncs Chord data to Facebook custom audiences and conversions through Data Activations, connected by OAuth or by a system user token with ads_management, which Chord prefers.
Meta Ads (pixel). Loads the Meta Pixel through Chord's CDP and fires standard events like PageView, AddToCart and Purchase to one or several pixel IDs, for example one per agency or brand.
Google Ads (audiences and conversions). Syncs Chord data to Google Ads from Data Activations over OAuth, upserting Customer Match lists and sending call, click and enhanced conversions plus conversion adjustments.
Google Ads (gtag). Fires Google Ads gtag conversions in the browser from Chord checkout starts, orders or chosen pages, with enhanced conversion data such as email, phone and address.
TikTok (Conversions API). Sends Chord events to TikTok from Chord's servers through the Conversions API, mapping orders to CompletePayment, with an access token and pixel code.
TikTok (pixel). Loads the TikTok Pixel in the browser through Chord's CDP, identifying the user before each conversion event and offering Limited Data Use mode for CCPA.
Snapchat (Conversions API). Posts Chord events to Snapchat's Conversions API server to server with a pixel ID and access token, deduplicated against the Snap Pixel through a shared ID.
Snapchat (Snap Pixel). Loads the Snap Pixel through Chord's CDP and sends page views, product views, cart adds, checkouts, purchases and subscriptions to Snapchat Ads from the browser.
Microsoft Advertising (Conversions API). Posts Chord events to Microsoft Advertising's Conversions API server to server, pairing each with a page load event and sharing event IDs with the UET tag for deduplication.
Microsoft Advertising (UET tag). Fires the Microsoft Advertising UET tag from Chord events in the browser, sending page loads, track events with revenue and order IDs, and email or phone for enhanced conversions.
Pinterest (Conversions API). Sends Chord page and commerce events to Pinterest's Conversions API from the server with an ad account ID and conversion token, deduplicated with the tag by event ID.
Pinterest (tag). Loads the Pinterest Tag in the browser through Chord's CDP and forwards page visits, searches, category views and other commerce events, with optional enhanced match.
Show the other 13 Advertising toolsShowing all 19 Advertising tools
The Trade Desk. Loads The Trade Desk Universal Pixel through Chord and maps page views and commerce events like cart adds and purchases to its event names, with revenue and item data.
Reddit (Conversions API). Reports Chord page and commerce events to Reddit's Conversions API v3 from the server with a pixel ID and conversion token, sharing deduplication keys with the Reddit Pixel.
Reddit (pixel). Runs the Reddit pixel on the storefront through Chord's CDP, forwarding page visits, product views, searches, cart adds and purchases for Reddit Ads measurement.
Meta Conversions API. Sends Chord page and commerce events to Meta's Conversions API from the server with a pixel ID and system user token, letting Meta deduplicate them against the pixel by event ID.
Rokt (Events API). Sends Chord purchases, sign-ups, subscriptions and page views to Rokt's Events API, the successor to its deprecated Conversions API, with credentials from a Rokt account manager.
Rokt (pixel). Runs Rokt's web SDK on the storefront through Chord to record conversions and page views, and with an account ID can show Rokt offers on the confirmation page.
OpenAI Ads (Conversions API). Sends Chord conversion events to OpenAI's Conversions API for ChatGPT Ads from the server, using a pixel ID and conversion key, with a validate-only mode for testing.
OpenAI Ads (pixel). Loads OpenAI's measurement pixel for ChatGPT Ads in the browser through Chord, keeping the oppref click ID and optionally sending hashed customer details for matching.
Impact.com. Reports Chord orders to Impact as conversions through its tracking APIs from the CDP, and can also send page, identify or track events as page loads, for affiliate attribution.
StackAdapt. Loads StackAdapt's Universal Pixel through Chord's CDP, firing page views and sending every track event as a conversion along with traits from earlier identify calls.
MNTN (conversion pixel). Fires MNTN's conversion pixel in the browser for Chord purchases, and optionally sign-ups, leads and other track events, so MNTN can credit connected TV ads.
MNTN (tracking pixel). Fires MNTN's site-wide tracking pixel on each Chord page or screen event with the page URL and referrer, for connected TV audience building and visit attribution.
Email & Marketing Automation
14 listings · 8 toolsBraze (cloud mode). Forwards Chord commerce events, purchases and identity updates to Braze's users/track and users/identify REST endpoints in cloud mode, using a key from the Developer Console.
Braze (device mode). Runs Braze's web SDK through Chord's CDP in device mode, logging Order Completed as purchases, other track events as custom events and identify calls as user attributes.
Salesforce Marketing Cloud. Loads Chord data into Salesforce Marketing Cloud data extensions, contacts and API-triggered journeys through an installed package and Enhanced FTP uploads, or SOAP calls for small volumes.
Iterable (events). Passes all Chord track and page events to Iterable as custom events and upserts user profiles on identify calls, using an Iterable API key of the server-side type.
Iterable (source). Pulls Iterable campaigns, templates, lists, user history and email, SMS, push and in-app events into Chord through Iterable's REST and export APIs with a server-side key.
Klaviyo (events). Sends Chord track events that include an email or phone to Klaviyo and upserts profiles from identify calls, using a private API key with Events write access.
Klaviyo (source). Ingests Klaviyo flows, campaigns, metrics, lists, segments and events into Chord with a read-only private API key, while profile tables stay off unless Chord enables them.
Attentive (events). Passes Chord track events that carry an identifier, such as a phone, email or user ID, to Attentive's Custom Events API for SMS and email targeting, but not page views or identify calls.
Attentive (source). Receives Attentive SMS and email opt-ins, sends, opens, clicks, replies and subscriber attributes in Chord through a webhook, capturing events only from registration onward.
Dotdigital (API). Creates or updates Dotdigital contacts and imports Chord commerce events into Insight data collections over the v3 API, using a dedicated API user and the account region.
Dotdigital (tag). Loads the Dotdigital tag in the browser through Chord and feeds it page, product, cart and purchase events, which Dotdigital's abandoned browse and cart programs depend on.
Sendlane (audiences). Tags existing Sendlane contacts with their Chord audiences, staged in a DynamoDB table and pushed by an AWS Lambda function using a Sendlane v2 API key.
Sendlane (events). Sends real-time shopper behavior and conversion events from Chord's CDP to a Sendlane account, so Sendlane can personalize email and SMS journeys and segments.
Analytics & BI
11 listings · 8 toolsGoogle Analytics (device mode). Loads GA4 through Chord's CDP in device mode with a measurement ID and maps Chord commerce events to GA4 ecommerce events such as view_item, add_to_cart and purchase.
Google Analytics (Measurement Protocol). Sends Chord events to GA4 from the server through the Measurement Protocol with an API secret and measurement ID, mapping orders, refunds and cart activity to GA4 events.
Heap (cloud mode). Sends Chord track and page events to Heap's server-side track API and identify traits to its user properties endpoint, using the project App ID and a US or EU region.
Heap (pixel). Loads Heap's browser SDK through Chord's CDP, passing Chord track, page and identify calls client-side while Heap's own capture, session replay and heatmaps run in the page.
Contentsquare. Installs the Contentsquare tag for Hotjar heatmaps, recordings and surveys through Chord's CDP with a site ID, after which the script records visitor behavior on its own.
Triple Whale. Sends user-level events from Chord's client-side tracking to Triple Whale in device mode, set up with the store identifier and platform, for attribution and funnel analysis.
Northbeam. Reports Chord orders and refunds to the Northbeam Orders API from the server for multi-touch attribution, with a test mode that targets Northbeam's UAT environment.
Northbeam (pixel). Runs Northbeam's pixel on the storefront through Chord's CDP, forwarding page views, identities, purchases, email captures and custom goal events for attribution.
9 more categories
Open one to see its toolsData Infrastructure
9 listings
Snowflake (outbound share). Delivers a brand's raw and transformed Chord data to its own Snowflake account as a private listing, with Chord covering replication costs for a yearly maintenance fee.
Snowflake (inbound share). Shares database objects from a brand's Snowflake account with Chord through a direct share in the same region or a private listing that Snowflake replicates across regions.
Amazon S3 (export). Exports data from Chord's Snowflake warehouse into a brand's own S3 bucket, ideally one kept for this purpose, through an IAM role with write access and a Chord external ID.
Amazon S3 (import). Lets Chord's Snowflake warehouse read data files from a brand's S3 bucket through an IAM role that trusts Chord's user ARN and external ID, so the files can be ingested.
Google Cloud Storage (export). Writes Chord data to a brand's Google Cloud Storage bucket using a Chord service account that holds a custom role able to create, list and delete objects.
Google Cloud Storage (import). Gives Chord's Snowflake-based warehouse read access to files in a Google Cloud Storage bucket through a custom role granted to a service account that Chord supplies.
Azure Blob Storage (export). Unloads Chord data into a brand's Azure Blob Storage container after Chord's Snowflake service principal is granted the Storage Blob Data Contributor role.
Azure Blob Storage (import). Loads data files from an Azure Blob Storage container into Chord's Snowflake warehouse once Chord's service principal is approved and given the Storage Blob Data Reader role.
E-commerce
9 listings
Shopify (store data). Connects a Shopify store as a Chord data source through a custom Chord Data Ingestor app with read access to orders, customers, products, inventory and fulfillments.
Shopify (web pixel). Tracks Shopify storefront and checkout events in Chord with the @chordcommerce/analytics library and a custom web pixel added under Shopify's customer events settings.
Shopify (webhooks). Turns Shopify webhooks for checkouts, orders, refunds and deletions into Chord server events through a Shopify webhook source that reads order details with an Admin API token.
Adobe Commerce. Pulls Magento products, variants and completed orders into Chord every day with Chord Ingest, using the store URL and an API key, and maps the records to Chord's data model.
Amazon Marketplace. Brings Amazon Selling Partner sales into Chord, where the Omni-Channel Sales Explore joins Amazon and Shopify line items, an Explore offered only to Shopify OMS customers.
Personalization & Testing
6 listings
Insider (cloud mode). Upserts Chord users and events into Insider One through its server-side Upsert API, translating commerce events to Insider's reserved names like item_added_to_cart.
Insider (pixel). Loads Insider One's ins.js web SDK through Chord's CDP and pushes page views, product, cart and purchase events and profile updates into InsiderQueue in the browser.
Nosto (GraphQL API). Updates Nosto visitor sessions and reports orders and refunds from Chord over Nosto's GraphQL API, with browsing events sent only when the Nosto Tag has set up a session.
Nosto (tag). Loads Nosto's script on the storefront through Chord and keeps each visitor's Nosto session current from Chord events, so Nosto can render product recommendations.
Ninetailed. Adds Chord audience traits to Ninetailed profiles as batched identify calls from an AWS Lambda fed by a DynamoDB stream, hashing emails used as IDs, for site personalization.
Security & Privacy
3 listings
CRM & Sales
1 listing
Customer Support
1 listing
Developer Tools & APIs
1 listing
Google Tag Manager. Loads a Google Tag Manager container through Chord's CDP and pushes each Chord page, identify and track event into its data layer, clearing it before the next event.
Engagement & Feedback
1 listing
Identity & Enrichment
1 listing
Retention.com. Loads the Retention.com pixel through Chord to match anonymous visitors for remarketing, sending page views, cart adds and orders while suppressing known emails.
Integration catalog breadth
Distinct tools documented per platform: the five largest of 44, then Chord 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
- 27SAP Engagement Cloud (formerly SAP Emarsys)63
- 28Chord59
- 29Microsoft Dynamics 365 Customer Insights56
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 Chord'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 Chord.
Evaluating or implementing Chord?
Vendor-neutral help choosing between Chord and the other 43 platforms, and getting the integrations above running in your stack.