Marketing & Acquisition AI

Hightouch CDP: Turn customer data into marketing audiences

Hightouch CDP turns warehouse customer data into audiences for your marketing tools; the wider platform adds AI-assisted content, AI Decisioning and direct email, SMS and push. Data teams prepare customer models for Hightouch CDP; marketers build audiences, create content and activate campaigns through connected tools or Hightouch’s own sending channels.

Visit Hightouch
Share

Hightouch CDP: who is it for?

Hightouch CDP, sold as Composable CDP, works on top of the customer data a team already keeps in a warehouse such as Snowflake or BigQuery, without copying it into a separate customer database. Marketers build audiences from the modeled data, and Hightouch syncs customer attributes, events and audience membership to tools such as Braze, Klaviyo or Meta. The separately sold Agentic Marketing Platform adds content creation and Hightouch AI Decisioning, which picks the message each customer receives.

A retailer using Hightouch CDP can combine order history, loyalty status and product interests to target a replenishment campaign or exclude recent purchasers from acquisition ads. A data owner prepares the models and identifiers; marketers reuse those fields in campaigns. Hightouch CDP is particularly relevant when the required customer context spans several systems.

For a store that only needs standard welcome and abandoned-cart emails, start by comparing its existing marketing platform’s store integration and flows. Hightouch CDP becomes more useful when shared customer data, richer audience rules or decisions across multiple channels are the actual bottleneck.

Hightouch CDP and AI: what each part does

Hightouch CDP handles customer data and audiences; the Agentic Marketing Platform handles content and message decisions. Each module can be bought on its own, so list the jobs you need first. The table shows what each module takes in and produces.

ModuleWork and output
Customer StudioMarketers filter customer attributes, orders and events in Hightouch CDP’s visual audience builder, preview the results and save audiences for activation.
Reverse ETLWithin Hightouch CDP, data teams map model columns to destination fields and keep customer records or lists updated on a configured schedule or trigger.
Lifecycle Studio and Ad StudioTeams generate and edit campaign messages or ad variants using brand guidance, templates and assets, then review the content before it is sent or published.
AI DecisioningA configured Hightouch AI Decisioning agent learns which prepared message, channel and timing to choose for each person using campaign and conversion events.
Journeys and Native DeliveryJourneys arrange waits, branches and exits for Hightouch CDP audiences on a set run schedule. Native Delivery sends email, SMS and push from Hightouch and writes delivery and engagement results back to the warehouse. Roles and sending domains are set up with the Hightouch team; the public pricing page does not say which plan includes it.
Events, identity and personalizationAdditional Hightouch CDP modules collect events, join customer identities and support website or app personalization. Include the modules your data design needs in the quote.

Hightouch Reverse ETL: use warehouse data in campaigns

Within Hightouch CDP, Reverse ETL moves modeled data from a source such as Snowflake or BigQuery into an operational tool. For example, a team can send each customer’s last purchase date and lifetime value to Klaviyo, or keep a high-value audience updated in Meta. The model identifies the records; the sync defines their destination and field mapping.

A standard Hightouch CDP sync connects one model to one destination object, list or table. Configure the matching key, write mode and field types, then test a row where supported. Later runs compare model results with the previous run and process changes. Check the rejected-row details when a destination refuses a record.

From customer data to a live audience

The data team exposes customer and order fields in Hightouch CDP. Marketers preview the audience, then choose a direct sync or a journey with timed steps. After activation, they check destination results and route rejected records to the person responsible for the mapping.

From customer data to a live audienceThe data team exposes customer and order fields in Hightouch CDP. Marketers preview the audience, then choose a direct sync or a journey with timed steps. After activation, they check destination results and route rejected records to the person responsible for the mapping. NoYesYesNoStart:preparedcustomer dataBuild and previewaudienceMultiple timedsteps?Map fields and testsyncSet tiles, exits andscheduleRun the configuredactivationAny rejectedrecords?Owner reviews rowerrorsConfirm destinationresultsEnd: resultsreviewedFrom customer data to a live audienceThe data team exposes customer and order fields in Hightouch CDP. Marketers preview the audience, then choose a direct sync or a journey with timed steps. After activation, they check destination results and route rejected records to the person responsible for the mapping. NoYesYesNoStart:preparedcustomerdataBuild andpreview audienceMultiple timedsteps?Map fieldsand testsyncSet tiles,exits andscheduleRun theconfiguredactivationAny rejectedrecords?Ownerreviews rowerrorsConfirmdestinationresultsEnd:resultsreviewed

Hightouch Journeys: audiences that move through steps

Journeys use Hightouch CDP audiences to coordinate follow-ups that depend on elapsed time or customer behavior. An abandoned-cart journey can wait, check for a purchase and send a reminder to the remaining customers. A direct audience sync is sufficient when the only task is to keep a destination list up to date.

Journey entry, exits, advancement and destination actions are evaluated when the journey runs. Set the run schedule to match the response time the campaign needs. Journeys require a configured Hightouch CDP schema with a parent model, the Lightning sync engine and a connected destination or enabled direct-send channel.

Before launch, test the journey with sample members and review who reaches each branch. Hightouch CDP’s journey test simulates movement without sending data and skips time delays. After launch, compare entry, step and destination counts at their respective stages to locate drop-offs.

Hightouch AI Decisioning: choose the next message

Hightouch AI Decisioning uses reinforcement learning to choose among prepared messages, channels and send times for each customer. The team defines the goal, audience, message options, schedule and guardrails. A purchase or win-back goal gives the agent an outcome to learn from as campaign results return.

Hightouch AI Decisioning needs customer identifiers, related profile data and timestamped events for purchases and message engagement. Hightouch recommends audiences of at least 500,000 users for AI Decisioning training. Smaller teams should discuss data sufficiency and pilot design with Hightouch before committing to this module.

Hightouch AI Decisioning selects messages from configured destinations such as Braze, Iterable or Salesforce Marketing Cloud. Use Inspector and the channel QA checklist to inspect eligibility and upcoming sends; use Insights to compare creative performance, timing and lift. Lifecycle Studio supplies the content-creation workflow when the team needs new message candidates.

One AI Decisioning cycle

The team supplies an audience, a purchase goal, message options and sending limits. Hightouch AI Decisioning selects a message, channel and time for an eligible customer, delivers through a configured destination and uses returned events for later decisions. Smart suppression can skip a send.

One AI Decisioning cycleThe team supplies an audience, a purchase goal, message options and sending limits. Hightouch AI Decisioning selects a message, channel and time for an eligible customer, delivers through a configured destination and uses returned events for later decisions. Smart suppression can skip a send. NoYesStart:configuredagentSelect message, channel,timeSend thismessage?Skip this sendConnected platformsendsReturn purchase andsend eventsEnd: informthe nextdecisionOne AI Decisioning cycleThe team supplies an audience, a purchase goal, message options and sending limits. Hightouch AI Decisioning selects a message, channel and time for an eligible customer, delivers through a configured destination and uses returned events for later decisions. Smart suppression can skip a send. NoYesStart:configuredagentSelect message,channel, timeSend thismessage?Skip thissendConnectedplatformsendsReturnpurchase andsend eventsEnd: informthe nextdecision

Lifecycle Studio and Ad Studio: create campaign content

Lifecycle Studio starts from the team’s business context, brand rules, templates and images. For a one-off email, the marketer describes the message and refines a draft. For an ongoing welcome or win-back program, Campaigns prepares a brief and message plan, then generates candidates for review.

Approved content can be exported to an existing email service provider as a template. Teams using Native Delivery build the email there, preview it with a real profile and send a test before launching. Platform admins arrange sending domains and roles; marketers manage the campaign and review delivery results.

Ad Studio creates ad variants from brand assets and product information. A marketer can edit copy, resize the creative or adjust individual layers, then approve the asset for launch. This is useful when campaigns need many creative variations while the design team retains control over brand and product presentation.

From a brief to approved campaign content

Lifecycle Studio and Ad Studio both use brand context and existing assets. The team selects the production task, reviews the draft and corrects it before export or launch. The email route below uses an existing email service provider; Native Delivery is another sending option for enabled workspaces.

From a brief to approved campaign contentLifecycle Studio and Ad Studio both use brand context and existing assets. The team selects the production task, reviews the draft and corrects it before export or launch. The email route below uses an existing email service provider; Native Delivery is another sending option for enabled workspaces. MessagesAdsNoYesStart: briefand brandassetsWhich contenttask?Lifecycle: draftmessagesAd Studio: createvariantsTeam approvescontent?Return to editor forchangesExport template orlaunch adEnd: handoffcompletedFrom a brief to approved campaign contentLifecycle Studio and Ad Studio both use brand context and existing assets. The team selects the production task, reviews the draft and corrects it before export or launch. The email route below uses an existing email service provider; Native Delivery is another sending option for enabled workspaces. MessagesAdsNoYesStart:brief andbrandassetsWhich contenttask?Lifecycle:draftmessagesAd Studio:createvariantsTeam approvescontent?Return toeditor forchangesExporttemplate orlaunch adEnd:handoffcompleted

Hightouch implementation: data and team responsibilities

Hightouch CDP setup starts with a shared use case: the audience to reach, the data needed to recognize them, the destination and the result to measure. A replenishment campaign might require customer IDs, order dates, purchased products and a repeat-purchase event. Agree on those fields before building the audience.

OwnerPreparation and ongoing work
Data teamConnect the data source to Hightouch CDP, define models and identifiers, expose fields to marketers and maintain purchase and engagement events.
Platform administratorSet workspace access, destination credentials, approval rules and brand or regional boundaries. Configure sending domains when using Native Delivery.
Marketing teamBuild and preview Hightouch CDP audiences, review creative, configure journeys or AI goals and compare results with a defined baseline or holdout.
Campaign and data owners togetherRun a small launch, inspect rejected rows and delivered messages, and verify that purchase events return with the correct customer and timestamp.

Hightouch pricing: free syncs and usage-based plans

Hightouch publishes three commercial entry points: Basic Reverse ETL, Composable CDP and Agentic Marketing Platform. Basic Reverse ETL has a free tier; Hightouch CDP and the AI marketing offering use modular, usage-based quotes. The public page gives no paid list price, and says usage pricing has no monthly-tracked-user limits or caps on sources, destinations and seats.

Official plan scope

Product or sales surfaceScopePublic price and status
Basic Reverse ETL ↗

Try limited data-sync use cases.

Included plan entitlements
  • Up to 2 active syncs
  • Unlimited destinations and user seats
Free tier
Composable CDP ↗

Choose the full Hightouch CDP or individual data capabilities: Reverse ETL, Events, Customer Studio, Real-time Personalization, Identity Resolution and Match Booster.

Included plan entitlements
  • Unlimited seats, premium extensions, advanced observability and access management
  • Enterprise security, dedicated expert support, custom SLAs and Data Agents
Usage-based; request a tailored quote.
Agentic Marketing Platform ↗

Ad Studio, Lifecycle Studio and AI Decisioning for advertising and lifecycle marketing. Confirm the purchased modules in the quote.

Included plan entitlements
  • Marketing-platform integrations, enterprise security and observability
Usage-based; monthly personalized-action allowance set in the quote.

A sync sends one model to one destination, so the free tier covers two such tasks, for example a Klaviyo profile sync and a Meta audience. For paid plans, complete cost depends on the modules, usage allowances and services in the quote, plus the team’s warehouse and connected-platform costs. Hightouch AI Decisioning can be purchased without buying the full Hightouch CDP.

What to include in a Hightouch quote

Which usage should the quote cover?

List normal and peak-month data volumes, active syncs, selected Hightouch CDP modules, AI audiences, personalized actions and sending channels. Ask for each allowance, overage rate and minimum commitment in writing.

Which implementation costs sit outside the software quote?

For Hightouch CDP, separate model preparation, identity cleanup, event collection, destination setup and ongoing campaign ownership. Ask who performs each task, whether onboarding services are included, and how warehouse and sending-provider costs are paid.

Hightouch alternatives compared

ProductProduct scopeBest-fit scenarios and implementation responsibilitiesPricing and billing
HightouchCurrent productHightouch is a customer data and AI marketing platform that turns warehouse data into audiences, campaigns and personalized messages.

Best fitUse existing customer models to build and activate audiences, with optional content production and individualized AI decisions.

ImplementationData owners maintain models and events; marketers maintain audiences, approved content and campaign settings.

Twilio SegmentTwilio Segment is a customer data platform that collects events, unifies profiles and activates audiences across connected tools.

Best fitCompare Segment when the team wants customer profiles built and kept inside Segment. Hightouch is a closer fit when warehouse models already define the audiences the team wants to activate.

ImplementationSegment teams configure event tracking, identity rules and destinations. For audiences and journeys, evaluate the CDP scope with Unify and Engage.

Segment Unify documentation ↗

Connections and the full CDP have different commercial scopes. Twilio lists custom pricing for CDP plans; request a quote covering the same data volume, audience and activation requirements.

Twilio customer data pricing ↗
Fivetran Activations (Census)Fivetran Activations, formerly Census, sends modeled data from data sources to business applications.

Best fitCompare this with Hightouch Reverse ETL when the immediate job is keeping business tools updated from warehouse models, especially for teams already operating Fivetran.

ImplementationThe team configures models, matching keys and destination mappings. Evaluate Hightouch’s content production and AI Decisioning separately from this data-sync comparison.

Census to Fivetran Activations ↗

Activations uses Monthly Active Rows (MAR) for inserted, updated and deleted data, measured per activation. Compare the expected changed rows and destination scope with Hightouch’s quote.

Fivetran usage pricing ↗
BrazeBraze is a customer engagement platform for coordinating email, mobile messaging and customer journeys using customer data.

Best fitCompare Braze when CRM operators want to manage messages and Canvas journeys in their engagement platform. Hightouch can also supply Braze with warehouse audiences or AI Decisioning, so an existing Braze deployment may remain in the stack.

ImplementationBraze setup connects identities and events and configures channels and Canvas. A combined deployment also needs Hightouch model mapping and, for AI Decisioning, its separate campaign or Canvas connection.

AI Decisioning with Braze ↗

Braze is quote-based. Compare platform scope, audience scale, channel usage, AI access and implementation services with the Hightouch quote.

Braze pricing ↗
KlaviyoKlaviyo is a customer marketing platform that connects store data to campaigns and automated flows, including an official Shopify integration.

Best fitCompare Klaviyo when a store’s immediate need is email and mobile campaigns built around its store integration. Hightouch adds a way to reuse modeled data from other systems in those campaigns.

ImplementationKlaviyo operators configure store synchronization, templates, triggers and exclusions. Using Hightouch alongside it adds customer matching and profile, event or list mappings.

Klaviyo connector ↗

Email pricing uses active profiles and send allowances. Compare mobile-message usage and additional products separately using the same audience and monthly campaign volume.

Klaviyo pricing ↗

Hightouch vs Braze: replace or connect?

Hightouch and Braze can overlap in lifecycle marketing, or work together. Start with the missing job: using warehouse data, creating messages, arranging journey steps or choosing the next message for each person. The answer determines whether to replace a workflow or add a connection.

RequirementHightouch and Braze approach
Use warehouse audiences in BrazeKeep Braze for campaigns and connect Hightouch’s data sync. Map profiles, events, purchases or cohorts according to the Braze connector.
Choose messages individuallyHightouch AI Decisioning can trigger prepared Braze Campaigns or Canvases. Compare it with Braze Decisioning Studio using the same goal, candidate messages and feedback events. Check audience size first: Hightouch recommends at least 500,000 users for AI Decisioning, while Braze recommends at least 20,000 for a Decisioning Studio Go agent, which optimizes email clicks only.
Move journey and delivery workCompare Hightouch Journeys and enabled Native Delivery channels with Braze Canvas and channels. Rebuild and test timing, exits, message templates and delivery configuration for the selected route.

Hightouch integrations: where the data goes

BrazeHightouch → Braze

Reverse ETL in Hightouch CDP, or the free Basic tier, syncs profile attributes, events, purchases and cohorts to Braze. Hightouch AI Decisioning uses a separate connection with its own API permissions to trigger Campaigns or Canvases.

Braze data connector
KlaviyoHightouch → Klaviyo

Hightouch CDP can map customer fields to profiles, insert events and add or remove list members. Match customers by email, phone number or Klaviyo ID.

Klaviyo connector
HubSpotHightouch → HubSpot

Hightouch CDP keeps CRM objects updated with modeled business data. Configure the object, matching key and mapped properties for the intended sync.

HubSpot connector
Meta Custom AudiencesHightouch → Meta Custom Audiences

Hightouch CDP maintains customer audiences for advertising from the selected model. The ad account and chosen matching identifiers determine the destination setup.

Meta Custom Audiences connector
Browse the official integration catalog

Hightouch questions before adoption

What does Hightouch CDP do?

Hightouch CDP organizes customer data and activates it in marketing tools; Customer Studio builds audiences from customer data models. The wider platform adds Lifecycle Studio and Ad Studio for content creation, while Hightouch AI Decisioning chooses prepared messages, channels and timing for individual customers.

Is Hightouch free?

Basic Reverse ETL has a free tier with up to two active syncs, unlimited destinations and unlimited user seats. Composable CDP and Agentic Marketing Platform use separate, usage-based quotes. Ask which modules and usage allowances are included in the proposed contract.

Does Hightouch CDP require a data warehouse?

Hightouch CDP commonly uses warehouses such as Snowflake and BigQuery, but the pricing FAQ also names databases, CSV files, SFTP and BI tools. The chosen workflow determines the data setup: Journeys needs a compatible Lightning source, while AI Decisioning needs prepared customer and event models.

Can Hightouch send email directly?

Yes. The current lifecycle documentation describes Native Delivery for email, SMS and push in enabled workspaces. Teams can also export approved Lifecycle Studio email templates to an existing email service provider. Configure the sending domain, roles and test messages for the chosen route.

Can Hightouch AI Decisioning work with Braze?

Yes. Hightouch documents a specific AI Decisioning connection for Braze Campaigns and Canvases. It is separate from the connector that syncs profile attributes, events and purchases. Braze Campaigns support dynamic variables in this connection; AI Decisioning cannot override message properties inside a Braze Canvas.

How much data does Hightouch AI Decisioning need?

Hightouch recommends audiences of at least 500,000 users, with customer identifiers, profile data and timestamped purchase and message-engagement events. Each agent targets one audience; start it as broad as consent allows and add per-message filters inside the agent. Teams with smaller lists should agree a pilot design with Hightouch before buying.

Hightouch vs Segment: what should a team compare?

Both can collect events and resolve identities; Hightouch sells Events and Identity Resolution as Composable CDP modules. The main difference is where the customer profile lives: Segment builds it inside Segment through Unify, while Hightouch CDP reads models in the team’s warehouse. Price the same event volume, audience and journey scope, including Segment Unify and Engage where needed, and test one shared customer-matching and destination task.

Is Census still an alternative to Hightouch?

Census is now Fivetran Activations. It remains relevant when comparing the warehouse-to-business-tool synchronization task with Hightouch Reverse ETL. Use current Fivetran documentation and usage pricing when evaluating the service.

Sources

User reviews

4.6 / 5425 reviews

Hightouch product profile

Individual reviews cannot be linked here. Open the original platform to read them.

More reviews on G2

Leave a review

Rate every dimension, then share your real experience.

Task effectiveness
Ease of use
Reliability
Workflow and integration fit
Value for money