CDP platform · 1 of 44 in the CdpHub directory
Snowplow integrations
CdpHub documents 48 listings from Snowplow's catalog, covering 40 distinct tools. 32 of those listings send data from Snowplow to a tool and 16 use a tool as a source. 27 can run server-side, 9 client-side and 12 in the warehouse. Every listing links to Snowplow's own documentation.
Jump to a category
Data Infrastructure
16 listings · 15 tools · the 6 most widely listed firstAmazon Redshift. Loads enriched Snowplow events from AWS pipelines into Amazon Redshift, Redshift Serverless included, as an events table plus a joinable table for each custom event or entity.
Google Cloud Storage. Copies Snowplow events from a Pub/Sub subscription into Google Cloud Storage with a Dataflow job, writing windowed files that can be compressed and partitioned by date or schema.
Databricks (batch). Loads Snowplow events into a Databricks events table with the RDB Loader's Databricks loader, which creates the schema and table itself and needs a Databricks cluster and access token.
Databricks (streaming). Streams Snowplow events to Databricks at low latency, staging files in a Unity Catalog volume for a Lakeflow Declarative Pipeline to load, which needs a premium Databricks plan.
Show the other 9 Data Infrastructure toolsShowing all 15 Data Infrastructure tools
PostgreSQL. Loads enriched or failed Snowplow events from Kinesis or Pub/Sub into a PostgreSQL database with the Postgres Loader, meant for testing and development rather than production.
Amazon Kinesis. Writes Snowplow events relayed by Snowbridge into Amazon Kinesis streams, authenticating with AWS credentials or a role ARN and retrying throttled records with growing back-off.
Google Pub/Sub. Publishes Snowplow events from Snowbridge to Google Pub/Sub topics using a service account credentials file, connecting through Google's Go client over gRPC with TLS.
Azure Event Hubs. Pushes Snowplow events from Snowbridge into Azure Event Hubs, authenticating with the environment variables that the Azure Event Hubs client library supports.
Amazon SQS. Puts Snowplow events relayed by Snowbridge onto Amazon SQS queues, with access granted through AWS environment credentials or an optional role ARN.
Elasticsearch. Indexes enriched and failed Snowplow events read from Kinesis in Elasticsearch or OpenSearch clusters with the Elasticsearch Loader, offered on AWS or within Snowplow Mini.
Apache Iceberg. Lands enriched and failed Snowplow events in Apache Iceberg tables registered in AWS Glue or a REST catalog such as Snowflake Open Catalog, for AWS and GCP pipelines only.
Delta Lake. Writes enriched and failed Snowplow events to Delta tables in your own S3, GCS or ADLS storage in the pipeline's cloud, ready for tools such as Athena, Spark, Synapse or Fabric.
Developer Tools & APIs
9 listings · 6 toolsWebhooks (GTM Server Side HTTP Request tag). Forwards events from a GTM Server Side container to any JSON HTTP endpoint with Snowplow's HTTP Request tag, building the request body from Snowplow Client or GA4 event data.
Webhooks (Snowbridge HTTP target). Delivers Snowplow events from Snowbridge to any HTTP endpoint, such as a GTM Server Side container, with basic auth or OAuth2, request templating, dynamic headers and beta response rules.
Google Tag Manager (server-side Snowplow Client). Receives Snowplow events in a Google Tag Manager server container, straight from the tracker or enriched by the pipeline, and maps them to common event data that GTM tags can use.
Google Tag Manager (server-side Snowplow Tag). Forwards events from a Google Tag Manager server container to the Snowplow collector with the Snowplow Tag, including events it builds from other clients such as GA4.
Google Tag Manager (web container). Deploys the Snowplow JavaScript tracker on your site through Google Tag Manager with the Snowplow v4 tag template from the gallery and its settings variable, plus an ecommerce tag.
CloudFront. Forwards Amazon CloudFront standard access logs to the Snowplow collector through an Amazon Data Firehose stream, where Enrich makes each log entry a page view, bots and AI agents included.
Google AMP. Tracks AMP pages in Snowplow through the amp-analytics component, which has Snowplow built in, sending page views, page pings, structured and custom events to your collector.
Cloudflare. Turns requests served through Cloudflare into Snowplow page view events with a Worker script, so visits from AI agents and bots that skip JavaScript are tracked too.
getanalytics.io. Runs Snowplow tracking inside the getanalytics.io analytics library through its @analytics/snowplow npm plugin, which Snowplow suggests only when web or Node apps feed several providers.
Analytics & BI
8 listings · 6 toolsGoogle Analytics. Reads Google Analytics cookies on your site, GA4 ones by default and Universal Analytics ones when enabled, and attaches their values to every Snowplow web event as entities.
Amplitude (event forwarder). Sends Snowplow events to Amplitude through a Console event forwarder that calls the HTTP API v2, mapping fields to Amplitude event, user and group properties.
Amplitude (GTM Server Side tag). Passes events from a GTM Server Side container to Amplitude's HTTP API v2 with Snowplow's Amplitude tag, merging self-describing event data into Amplitude event properties.
Kantar Focal Meter. Sends the Snowplow domain user ID from the web tracker to a Kantar Focal Meter endpoint whenever it changes, optionally hashed, so the router meter can measure content audiences.
Kantar Focal Meter (mobile). Lets the Snowplow iOS and Android trackers pass the session user ID to a Kantar Focal Meter endpoint at app start or when it changes, for router-based audience measurement.
6 more categories
Open one to see its toolsEmail & Marketing Automation
8 listings
Braze (event forwarder). Updates Braze user attributes and logs custom events and purchases from Snowplow data through an event forwarder calling the Track Users API with a REST API key.
Braze (GTM Server Side tag). Relays events from a Google Tag Manager server container to Braze with Snowplow's official Braze tag, built mainly for Snowplow Client events though GA4 client events work too.
Iterable (GTM Server Side tag). Converts Snowplow events in a GTM Server Side container into Iterable events, identity events included, with Snowplow's Iterable tag and a server-side Iterable API key.
Iterable (webhook). Collects Iterable system webhook events, such as email opens and clicks or SMS and push sends, at the Snowplow collector so they reach your warehouse with your other events.
Bloomreach. Forwards Snowplow events to Bloomreach Engagement through the Batch Commands API, identifying customers by user ID as a hard ID and domain user ID as a soft cookie ID.
Advertising
2 listings
Meta Conversions API. Sends Snowplow events to Meta's Conversions API for ad measurement and optimization, one event per request, passing the user ID and the click and browser IDs from Meta cookies for matching.
Personalization & Testing
2 listings
Optimizely. Adds Optimizely X experiment and variation details as an entity on every event the Snowplow web tracker sends, through the Optimizely X plugin, for A/B test analysis.
LaunchDarkly. Feeds events from a GTM Server Side container into LaunchDarkly's metric import REST API with Snowplow's LaunchDarkly tag, for use as metrics in LaunchDarkly experiments.
Customer Data Platform
1 listing
Census. Recommends Census, now Fivetran Activations, as the reverse ETL tool for syncing audiences, scores and attributes built from Snowplow data in your warehouse to ad, CRM and email platforms.
Customer Support
1 listing
Integration catalog breadth
Distinct tools documented per platform: the five largest of 44, then Snowplow 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
- 34Odie (formerly Totango)41
- 35Snowplow40
- 36CaliberMind35
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 35 of 44 CDPs" counts every platform in the directory that lists the tool; the listing count beside it is Snowplow'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 Snowplow.
Evaluating or implementing Snowplow?
Vendor-neutral help choosing between Snowplow and the other 43 platforms, and getting the integrations above running in your stack.