Skip to main content
Send events such as trial_started or plan_upgraded from your warehouse to Conversion. Each event is recorded on a matching contact and can be used in audiences and event-based workflows. On each scheduled sync, Hightouch sends new event rows to the Conversion Track Event endpoint, with one HTTP request per event.
To send live events from Hightouch to Conversion, contact our team for setup guidance.

​
Before you begin

Make sure you have:
  • A Conversion HTTP destination. Follow the connection steps in Syncing Contacts.
  • A Hightouch model with one row per event, including a unique event ID, contact email, event name, and occurrence time.
Use the event ID as the model’s primary key. Each occurrence needs its own ID, even when the same contact performs the same action again.

​
Configure the event sync

1

Create a sync

Create a sync using your event model and the Conversion destination.
2

Configure the request

Enable Rows added only. Leave Rows changed and Rows removed disabled.
3

Map event fields

Map your model’s columns to these Conversion fields:For example, your mappings could produce:
Hightouch fills in the values automatically for each row. Map data from an object column, or build it from separate columns using Hightouch’s inline mapper, if enabled.
To create a contact when its email is not found, map the boolean constant true to createContact. Otherwise, make sure your contacts have synced successfully before sending their events.
4

Choose the initial history and schedule

Choose whether the first run should send existing event rows or skip them and send future additions. Historical events can also trigger workflows.Set the sync schedule and enable retries for failed rows. Keep event rows available in your source until they have been delivered successfully.

​
Test the connection

Send one test event and confirm its name, timestamp, and properties on the matching contact in Conversion. Send it again with the same eventId to check that Conversion reports duplicate: true without recording it twice.

​
Event IDs and timestamps

Keep each eventId unique across your workspace, and reuse it when retrying that event. Conversion ignores duplicate IDs. Without an ID, each request creates another event. Send the original timestamp to preserve when the event happened. If omitted, Conversion uses the time it receives the event. Workflows can react once the event arrives in Conversion.

​
How events are matched to contacts

This setup matches contacts by email. You can also identify a contact with userId; if both are sent, Conversion tries userId first, then email. Events for unknown contacts are rejected unless createContact is enabled and an email is provided. Event properties do not update contact profile fields. Use a contact sync for those updates. See Track Event for the full request options.