For HightouchAI Platform

Operations Observability Alerts

Hightouch · Hightouch

Composable CDP / Reverse ETL — Hightouch

Hightouch evals — Operations — Observability, Run History & Alerts (relift v3 InfraRed)

About Hightouch

Hightouch is the composable Customer Data Platform — reverse-ETL from warehouses (Snowflake, BigQuery, Redshift, Databricks) to 200+ SaaS destinations, Customer Studio for visual audience building on top of the warehouse, and AI Decisioning for next-best-action and send-time personalization.

Employees

~150

Industry

Customer Data Platform

Headquarters

San Francisco, CA

Website

hightouch.com

Sample tests· showing 3 of 9

#	Input	Expected behavior	Check
01	Sync to Salesforce fails. Alert reaches Slack as 'Sync 1234 failed' with no destination, no error message, no rejected-row count.	Alert payload must include sync name, destination, run id (link to UI), error category, and rejected-row delta vs prior run per docs. On-call should be able to triage from the alert alone. Configure alert templating in workspace settings; verify rendering before pushing to production.	Pass / FailAi Platformhigh
02	Operator wants per-sync SLO dashboards (success rate, lag, rejected-row %) alongside other infrastructure metrics. Pulls from Hightouch UI screenshots.	Configure Hightouch's metrics / webhook export per docs to push run-level metrics into Datadog / Grafana / a metrics store; build SLO dashboards there. Avoid manual screenshot rituals for a stable production surface.	Pass / FailAi Platformmedium
03	Run debug logs include rejected-row samples that contain PII (full names, email addresses) sent to a Slack channel of 40 engineers via alert webhook.	Tag PII columns in the Model so Hightouch redacts them from debug logs and rejected-row samples per docs; route detailed debug to a restricted channel (few people, SSO-gated) and send minimal context to broader alert channels. Audit log exposure on a schedule.	Pass / FailAi Platformcritical
Use this eval