For the two “Track” event types, Hightouch allows you to choose whether to:
Send the initial set of results as track events
Or, only send the changes between the results in the subsequent syncs as track events
Checking the “Send events for initial result set” checkbox will result in a large amount of events being sent in the first sync.Hightouch will always send the initial set of results as identify calls when in the “Identify” event type.
For the generic track mode, there are further settings that are needed to determine which event name Hightouch will send to RudderStack for each added, changed, and removed record.In this example, Hightouch will send RudderStack:
A user signed up event when a record is added to the query results
A user changed subscription event when a record is changed in the query results
A user deleted account event when a record is removed in the query results
Hightouch allows you to send a timestamp that the event occurred for generic track events. This is useful for backfilling historical events.Hightouch also allows you to send a message ID for each record to ensure that the event is deduplicated within RudderStack in the case that the same event erroneously gets sent twice.
To see the exact API requests and responses from each sync run, use the live debugger. To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up sync alerts. If you run into an issue this page doesn’t cover, .
