Rank #4 of 5 in Customer Data Platforms
Showcase


Try itExperimental
See what an agent can do with Hightouch before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si https://api.hightouch.com/api/v1/syncs # REST API answers keylessly with a structured auth errorrecorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai cdp — stories about ai cdp in this arenaAi cdpevidence →
Stories about ai cdp in this arena
Audiences activation — stories about audiences activation in this arenaAudiences activationevidence →
Stories about audiences activation in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Destinations integrations — stories about destinations integrations in this arenaDestinations integrationsevidence →
Stories about destinations integrations in this arena
Event collection — stories about event collection in this arenaEvent collectionevidence →
Stories about event collection in this arena
Identity resolution — stories about identity resolution in this arenaIdentity resolutionevidence →
Stories about identity resolution in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pipeline observability — stories about pipeline observability in this arenaPipeline observabilityevidence →
Stories about pipeline observability in this arena
Privacy consent — stories about privacy consent in this arenaPrivacy consentevidence →
Stories about privacy consent in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Replay portability — stories about replay portability in this arenaReplay portabilityevidence →
Stories about replay portability in this arena
Transformations quality — stories about transformations quality in this arenaTransformations qualityevidence →
Stories about transformations quality in this arena
Warehouse native — stories about warehouse native in this arenaWarehouse nativeevidence →
Stories about warehouse native in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 1 free · 0 paid · 0 enterprise · 32 not stated in evidence
Follow the green: where the map greys out is where Hightouch stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Machine-readable spec · Versioning policy · API sandbox · Official CLI
Subscribe to events via webhooks
—0/10
Build against official SDKs
✓7/10
Issue scoped/least-privilege API credentials for an agent
~4/10
Connect an agent via an official MCP server
✓9/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~5/10
unlocks → MCP client
Operate the product with natural-language commands
✓8/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
~6/10
Set up automations that run autonomously in the background
✓7/10
Ai cdp — stories about ai cdp in this arenaAi cdp
Stories about ai cdp in this arena
An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop
✓7/10
An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server
✓7/10
Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema
✓8/10
AI decisioning agents pick messages, timing, and channels per customer autonomously within guardrails I set, with measurable lift
~5/10
Audiences activation — stories about audiences activation in this arenaAudiences activation
Stories about audiences activation in this arena
Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time
~6/10
Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating
~6/10
Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting
~5/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Destinations integrations — stories about destinations integrations in this arenaDestinations integrations
Stories about destinations integrations in this arena
Event collection — stories about event collection in this arenaEvent collection
Stories about event collection in this arena
Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees
~6/10
Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)
✓8/10
Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps
—0/10
Identity resolution — stories about identity resolution in this arenaIdentity resolution
Stories about identity resolution in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Openness
Self-host the core product
—–
Pipeline observability — stories about pipeline observability in this arenaPipeline observability
Stories about pipeline observability in this arena
Privacy consent — stories about privacy consent in this arenaPrivacy consent
Stories about privacy consent in this arena
User consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically
—–
Process user deletion and suppression requests (GDPR/CCPA) and have them forwarded to connected destinations
—–
Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes
—–
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Replay portability — stories about replay portability in this arenaReplay portability
Stories about replay portability in this arena
Transformations quality — stories about transformations quality in this arenaTransformations quality
Stories about transformations quality in this arena
Warehouse native — stories about warehouse native in this arenaWarehouse native
Stories about warehouse native in this arena
Sorted by importance (agentic first) (high → low) · 51/51 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 5/10 | Cclaimed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | untested | none yet | |
Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page) C Sdks | data engineer | Event collection — stories about event collection in this arenaEvent collection | 3 | full | 8/10 | Cclaimed | |
An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server C Agent pipeline | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 3 | full | 7/10 | Tprobed | |
An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop C Agent audiences | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 3 | full | 7/10 | Tprobed | |
Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control C Warehouse sync | data engineer | Warehouse native — stories about warehouse native in this arenaWarehouse native | 3 | full | 7/10 | Xcommunity | |
Route events to a large catalog of documented destination integrations with per-destination mapping and filtering C Destinations | data engineer | Destinations integrations — stories about destinations integrations in this arenaDestinations integrations | 3 | fullfree | 7/10 | Xcommunity | |
Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rules C Stitching | data engineer | Identity resolution — stories about identity resolution in this arenaIdentity resolution | 3 | partial | 6/10 | Cclaimed | |
Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating C Audiences | marketer | Audiences activation — stories about audiences activation in this arenaAudiences activation | 3 | partial | 6/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 6/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 5/10 | Xcommunity | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
User consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically C Consent | privacy lead | Privacy consent — stories about privacy consent in this arenaPrivacy consent | 3 | none | untested | none yet | |
Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema C Ai assist | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 2 | full | 8/10 | Tprobed | |
Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL) C Composable | data engineer | Warehouse native — stories about warehouse native in this arenaWarehouse native | 2 | full | 8/10 | Xcommunity | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | full | 7/10 | Tprobed | |
Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time C Activation | marketer | Audiences activation — stories about audiences activation in this arenaAudiences activation | 2 | partial | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 6/10 | Cclaimed | |
Query unified customer profiles — traits, identifiers, event history — through a documented profile API or store C Profiles | data engineer | Identity resolution — stories about identity resolution in this arenaIdentity resolution | 2 | partial | 6/10 | Tprobed | |
Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees C Ingest | data engineer | Event collection — stories about event collection in this arenaEvent collection | 2 | partial | 6/10 | Cclaimed | |
Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alerting C Observability | data engineer | Pipeline observability — stories about pipeline observability in this arenaPipeline observability | 2 | partial | 6/10 | Xcommunity | |
AI decisioning agents pick messages, timing, and channels per customer autonomously within guardrails I set, with measurable lift C Ai decisioning | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 2 | partial | 5/10 | Cclaimed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 5/10 | Xcommunity | |
Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting C Traits | marketer | Audiences activation — stories about audiences activation in this arenaAudiences activation | 2 | partial | 5/10 | Cclaimed | |
Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations C Transformations | data engineer | Transformations quality — stories about transformations quality in this arenaTransformations quality | 2 | partial | 5/10 | Cclaimed | |
A tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream data C Data quality | data engineer | Transformations quality — stories about transformations quality in this arenaTransformations quality | 2 | none | 0/10 | ||
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Replay archived events into a new destination or backfill history when a tool is added or a pipeline breaks C Replay | data engineer | Replay portability — stories about replay portability in this arenaReplay portability | 2 | none | 0/10 | ||
Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes C Pii controls | privacy lead | Privacy consent — stories about privacy consent in this arenaPrivacy consent | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Process user deletion and suppression requests (GDPR/CCPA) and have them forwarded to connected destinations C Deletion | privacy lead | Privacy consent — stories about privacy consent in this arenaPrivacy consent | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 5/10 | Xcommunity | |
Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps C Sources | data engineer | Event collection — stories about event collection in this arenaEvent collection | 1 | none | 0/10 |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 36 stories with headroom
What would move Hightouch’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
All evidence describes Hightouch exposing its own MCP server so external AI assistants can call Hightouch's tools (server role), not Hightouch's built-in agent acting as an MCP client that can plug in and use other services' MCP servers/tools.
Privacy consent — stories about privacy consent in this arenaUser consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically
nonemoves PA Scoreimpact 30
No evidence pack items mention consent management, opt-outs, consent categories, or any suppression/enforcement mechanism honored across destinations; Hightouch's docs focus on syncs, audiences, identity resolution, and events, none of which describe consent capture or enforcement.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
Hightouch is presented throughout as a hosted SaaS platform (workspace, pricing tiers, API auth) with no mention of self-hosting or on-premise deployment options anywhere in the evidence pack.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
The evidence pack covers Hightouch's REST API, Git Sync, and MCP server for AI assistants, but no official CLI tool is mentioned anywhere in the docs, pricing, or community evidence.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
Evidence shows sync alerts/notifications (docs-28) and a REST API (docs-13, docs-33) but no documentation of a webhook subscription mechanism for events; Hightouch Events (docs-5/6/7) is about ingesting customer behavior data, not emitting webhooks for system/sync events.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
Hightouch documents a REST API with auth guidance (hightouch-docs-13, hightouch-docs-33) but there is no evidence of an interactive API reference with runnable examples — probes for openapi.json/swagger.json all returned 404 across every candidate path, and no docs mention a try-it console, Postman collection, or embedded API explorer.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
Hightouch has a REST API (hightouch-docs-13, hightouch-probe-rt-1) but explicit probes for an OpenAPI/Swagger spec at all standard paths returned 404 (hightouch-probe-3), and no docs page offers a downloadable machine-readable spec.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Missing: any mention of API version numbers, changelog, or deprecation/sunset policy for the REST API or MCP server.
Showing the top 8 of 36 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map5 surfaces · 33 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs32 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop
- An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server
- Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema
- AI decisioning agents pick messages, timing, and channels per customer autonomously within guardrails I set, with measurable lift
- Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time
- Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating
- Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
- Route events to a large catalog of documented destination integrations with per-destination mapping and filtering
- Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees
- Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)
- Query unified customer profiles — traits, identifiers, event history — through a documented profile API or store
- Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rules
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alerting
- Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations
- Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL)
- Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control
llms.txt8 stories
- Point an agent at llms.txt or agent-oriented docs
- Connect an agent via an official MCP server
- Issue scoped/least-privilege API credentials for an agent
- Operate the product with natural-language commands
- An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop
- An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server
- Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema
- Schedule recurring jobs or workflows
Hacker News8 stories
- Version, review, and roll back my automations
- Route events to a large catalog of documented destination integrations with per-destination mapping and filtering
- Query unified customer profiles — traits, identifiers, event history — through a documented profile API or store
- Export all of my data in open formats and leave
- Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alerting
- Choose where my data is stored (region/residency)
- Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL)
- Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si https://api.hightouch.com/api/v1/syncs # REST API answers keylessly with a structured auth errorreproduced$ curl -si https://api.hightouch.com/api/v1/syncs # REST API answers [redacted]lessly with a structured auth error
HTTP/2 401
date: Tue, 08 Sep 2026 22:00:17 GMT
content-type: application/json; charset=utf-8
{"message":"Authentication error","details":"No authorization header found"}
$curl -s https://hightouch.com/llms.txt | head -4reproduced$ curl -s https://hightouch.com/llms.txt | head -4 # Hightouch > Hightouch is an Agentic Marketing Platform powered by the industry-leading Composable CDP.
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
12 of 21 testable claims verified · 1 contradicted → integrity 48/100
29 distinct capability claims found in Hightouch’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
12
Verified
8
Unverified
1
Contradicted
13
Undersold
Verified (20)
“Data teams define reusable models via SQL, dbt, BI queries, or a visual builder”
Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL)fullproof ↗
“Syncs run on a schedule or trigger and report the outcome of each run”
“Syncs run on a schedule or trigger and report the outcome of each run”
Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alertingpartialproof ↗
“Sync debugger lets you inspect a run and diagnose rejected rows”
Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alertingpartialproof ↗
“Hightouch Events collects web, mobile, and backend behavioral data into the warehouse”
Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I controlfullproof ↗
“Golden Record produces a one-row-per-identity table of canonical field values via survivorship rules”
Query unified customer profiles — traits, identifiers, event history — through a documented profile API or storepartialproof ↗
“MCP server lets an AI assistant build audiences, manage syncs, design journeys, and generate emails/ads in plain language”
“MCP server lets an AI assistant build audiences, manage syncs, design journeys, and generate emails/ads in plain language”
Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schemafullproof ↗
“Natural-language prompts can create an audience definition and wire it to a sync destination”
An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loopfullproof ↗
“REST API exposes syncs, models, sources, and destinations as manageable resources”
Drive the product through a documented public APIfullproof ↗
“REST API exposes syncs, models, sources, and destinations as manageable resources”
An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP serverfullproof ↗
“Built-in agent lets users explore segments and analyze campaign performance in natural language”
Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schemafullproof ↗
“Syncs modeled data to sales, support, analytics, and internal tools on a schedule or when data changes”
Route events to a large catalog of documented destination integrations with per-destination mapping and filteringfullproof ↗
“Lightning sync engine computes CDC directly in the warehouse for higher-scale performance”
Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL)fullproof ↗
“A sync maps one model's rows into one destination object, list, or table”
Route events to a large catalog of documented destination integrations with per-destination mapping and filteringfullproof ↗
“Sync alerts notify users when a run fails”
Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alertingpartialproof ↗
“Git Sync allows managing workspace resources programmatically via version control”
“API requests are authenticated with an API key passed as a bearer token”
Drive the product through a documented public APIfullproof ↗
“Models can be queried directly, built on in Customer Studio, or synced downstream”
Query unified customer profiles — traits, identifiers, event history — through a documented profile API or storepartialproof ↗
“Models can be queried directly, built on in Customer Studio, or synced downstream”
Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL)fullproof ↗
Unverified (13)
“No-code UI lets marketers build audiences and journeys once schema is configured”
Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activatingpartialproof ↗
“Official SDKs (browser, iOS, Android, Node.js) plus an HTTP API for server-side event ingestion”
Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)fullproof ↗
“Official SDKs (browser, iOS, Android, Node.js) plus an HTTP API for server-side event ingestion”
Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guaranteespartialproof ↗
“HTTP Tracking API records event data from any website or application”
Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guaranteespartialproof ↗
“Identity Resolution links related customer records into a single unified identity in the warehouse”
Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rulespartialproof ↗
“Ad Studio generates visual ad creatives from a prompt and refines them via follow-up instructions”
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
“AI Decisioning uses reinforcement learning to pick the best message, channel, and timing per customer and measures results”
AI decisioning agents pick messages, timing, and channels per customer autonomously within guardrails I set, with measurable liftpartialproof ↗
“Personalizes website and app experiences in real time based on current customer behavior”
Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-timepartialproof ↗
“Adds extra identifiers to synced audiences/conversions so ad platforms recognize more customers”
Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rulespartialproof ↗
“Built-in agent lets users explore segments and analyze campaign performance in natural language”
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
“Tracking spec supports five event types: identify, track, page, screen, and group”
Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)fullproof ↗
“Batch endpoint submits multiple events to the collector in a single request”
Perform bulk operations across many items at oncepartialproof ↗
“Apps can be instrumented via SDK, HTTP API, or a streaming source like Kafka or Google Pub/Sub”
Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guaranteespartialproof ↗
Contradicted (1)
“Apps can be instrumented via SDK, HTTP API, or a streaming source like Kafka or Google Pub/Sub”
Pull customer data in from third-party cloud apps and feeds — not just my own instrumented appsnoneproof ↗
Undersold (13)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundfullproof ↗
Operate the product with natural-language commandsfullproof ↗
Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targetingpartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinationspartialproof ↗
Claims outside our story set (2)
Real capability claims found in Hightouch’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Change-data-capture sends only new, changed, and removed rows instead of a full result set each run”
source ↗“Configurable permissions, approvals, and ownership boundaries per team”
source ↗
Business model
Reverse ETL has a free tier (up to 2 active syncs, unlimited destinations and seats); Customer Studio (the composable-CDP suite) and AI Decisioning are sales-quoted, scaling with usage.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt up (tracking since Sep 10 '26)
