Syncs

Operator sets sync mode to 'upsert' on a Salesforce destination. They expect rows removed from the warehouse to disappear from Salesforce.

upsert mode inserts new rows and updates existing rows by match key — it does NOT delete destination rows that vanished from the Model. To propagate deletes, use mirror mode (or upsert + delete sync, per destination support). Document the chosen mode in the sync description so operators know the li…

A real-time personalization use case is scheduled with a 1-hour interval; downstream Braze sends emails with stale state.

Pick schedule per use case: cron/interval for batch attributes, triggered (dbt Cloud / API trigger) for chained workflows, streaming for low-latency personalization (where destination supports it). Document the freshness requirement and pick the cheapest schedule that meets it.

Operator enables Hightouch streaming sync to Iterable, expecting <1s latency. Iterable's API tier rate-limits and the sync queues batches under the hood, delivering at 30s latency.

Streaming sync end-to-end latency is bounded by the destination's API tier and rate limits, not by Hightouch alone. Document the expected destination latency floor; if sub-second is required, upgrade the destination tier or switch destinations. [REQUIRES-VERIFICATION] on Hightouch's documented stre…