Destinations

Operator configures a Salesforce destination sync to push customer LTV into the Account object. Salesforce records have an existing External_Customer_Id__c field but the operator selects 'Salesforce Id' as the match key.

Use External_Customer_Id__c (an external-id field marked unique in Salesforce) as the match key so Hightouch upserts cleanly without needing the Salesforce-side Id. Per docs, match-key fields must be marked External Id + Unique in Salesforce. Verify the field type matches the model column type.

Operator wants to push 'subscription_renewed' events from the warehouse to HubSpot for trigger workflows. They configure a Contact-mode sync writing a boolean property instead of a Custom Behavioral Event.

Use HubSpot Custom Behavioral Events destination mode (event mode) — each row becomes a discrete event with timestamp and properties, suitable for trigger workflows. Contact-mode is for slowly-changing attributes; using a boolean for events loses event timestamps and replay history.

Operator reuses one Segment Source write key across three Hightouch syncs to save setup time. Segment's downstream warehouse loaders cannot distinguish the streams.

Configure a distinct Segment Source (and write key) per Hightouch sync or per logical event stream. Per Segment + Hightouch docs, separating sources preserves provenance, simplifies downstream debugging, and isolates rate-limit / outage blast radius.