01 · Records and state owned
Warehouse-governed models, audiences, journeys, campaign concepts, creative/performance context, and destination state.
Hightouch
Hightouch
Curated major addition platform in composable cdp and reverse etl with material relevance to the Marcom operating stack and a first-party developer surface.
Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaSReverse ETL / activation
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Warehouse-governed models, audiences, journeys, campaign concepts, creative/performance context, and destination state.
03 · Actions and write paths
Build/save audiences and journeys and generate supported marketing assets; verify destination execution tools.
04 · Authentication and permissions
Hightouch account authentication Plan, workspace, source-model, and destination permissions apply.
05 · Monitoring, approval, and recovery
Consequential writes should require explicit review; use vendor confirmation controls where available. Plan-gated; warehouse governance and downstream destination approval remain essential.
06 · Gaps and implementation limits
Plan-gated; warehouse governance and downstream destination approval remain essential.
First-party access
Documented surfaces
Warehouse SQL models ↗Hightouch runs queries directly against connected customer warehouses and databases to build models. SQL executes against the customer's source; source-specific credentials, roles, and Hightouch permissions govern access.Source: Sources overviewHightouch Reverse ETL ↗Hightouch explicitly calls its warehouse-to-destination data activation process Reverse ETL. Destination execution is a native platform capability and must not be attributed wholesale to the separately documented Hightouch MCP server.Source: Data activation conceptsMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceEvents / extensions ↗Webhooks, apps, or extensionsProduct ↗Native platform experience
Agent access
MCP and adjacent posture
Verified first-party provider MCPHightouch hosted marketing MCPCurrent documented service
Role: provider
Read scope: Warehouse-governed models, audiences, journeys, campaign concepts, creative/performance context, and destination state.
Write scope: Build/save audiences and journeys and generate supported marketing assets; verify destination execution tools.
Authentication: Hightouch account authentication
Approval boundary: Consequential writes should require explicit review; use vendor confirmation controls where available.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability3
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Hightouch ships these experiences.
Single-platform patterns
- Warehouse-native audience and activation control room
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- Hightouch + CRM or commerce system: lifecycle journey debugger
- Hightouch + warehouse or CDP + content-production platform: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
7 recorded sources
MCP / agent-role validationRepresentative source
https://hightouch.com/docs/ai-integrations/mcp ↗Hightouch documents a server that builds audiences, journeys, content, ads, and performance analyses in natural language.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://hightouch.com/docs/api-reference ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://hightouch.com/docs ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://hightouch.com/docs/webhooks ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://hightouch.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Warehouse SQL modelsTargeted review
Sources overview ↗Hightouch runs queries directly against connected customer warehouses and databases to build models. SQL executes against the customer's source; source-specific credentials, roles, and Hightouch permissions govern…
- Publisher updated
- May 20, 2026
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party access review
Hightouch Reverse ETLTargeted review
Data activation concepts ↗Hightouch explicitly calls its warehouse-to-destination data activation process Reverse ETL. Destination execution is a native platform capability and must not be attributed wholesale to the separately documented…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party access review
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.