Hightouch

Sync status and lag for reverse-ETL destinations.

The problem

Reverse-ETL syncs stall without showing up on the data platform NOC.

The outcome

Connector-level sync metadata joins pipeline observability — no row reads.

Ready

Connect UI

Syncs

Status + lag

Dest

SaaS targets

What you get

Last success, row counts from metadata API.

Cursor lag on stream → warehouse path.

Downstream BI when sync fails.

Hightouch partner API.

Integration · Warehouse

Google BigQuery

Freshness and cost from INFORMATION_SCHEMA and JOBS — never result rows.

Integration · Transform

dbt Core

Upload run_results.json or wire a webhook for calm failure triage.

Integration · Transform

dbt Cloud

Same triage path for Cloud runs — artifact-first, rows never exported.

Open workspace, or book a Data Stack Health Audit credited toward Managed.