Skip to main content
Use Hightouch to create and update contacts in Conversion. Set up an HTTP Request destination, map your contact fields, and choose how often to sync.
To keep audience membership in sync, see Syncing Audiences.

​
Before you begin

Make sure you have:
  • A Conversion API key. Generate one from Settings → Integrations → API. See API.
  • A Hightouch model with one row per contact, a unique primary key, and an email column.
  • Permission to create destinations and syncs in Hightouch.
  • Contact fields in Conversion for any attributes you want to send. Use List Fields to find their writable field keys.

​
Connect Hightouch to Conversion

1

Create the destination

In Hightouch, go to Integrations → Destinations → Add destination, select HTTP Request, and name it Conversion. Choose Basic Auth to configure the base URL and headers below. Conversion authenticates with the X-API-Key header.
Hightouch HTTP Request destination using Basic Auth and https://pub-api.conversion.ai

Select Basic Auth and enter Conversion's API base URL.

To add each header, enter its key and click Add key, then enter its value. For X-API-Key, select Secret before clicking Add key.
HTTP headers with Content-Type application/json and a masked X-API-Key

Add the JSON content type and your API key. Keep the API key secret.

Save the destination. You can reuse it for contact, audience, and event syncs to the same Conversion workspace.
2

Create a contact sync

Create a sync using your contact model and the Conversion destination.Enable Rows added and Rows changed. Configure both triggers with these settings:Leave Rows removed disabled to keep contacts in Conversion when they leave the source model.
3

Map contact fields

Paste the following into the JSON editor, replacing the source column names with your own. The keys inside fields must match Conversion field keys.
Hightouch fills in the values and sends one request per contact. Conversion creates contacts with new emails and updates matching contacts with the fields you send. You can omit fields if you only want to create contacts using their emails.
4

Choose a schedule

Under Rows added → Initial sync behavior, select Yes, backfill all rows to import your current contacts. Complete the rate-limit, concurrency, timeout, and retry settings for each trigger, then save. Choose Manual to test or Interval for a recurring schedule.
Hightouch initial sync behavior set to backfill all rows

Choose whether to import existing contacts on the first run.

On subsequent runs, Hightouch sends new contacts and changes to existing contacts.

​
Test the connection

Run the sync with a small set of contacts. Check for rejected rows in Hightouch and confirm the contacts and fields in Conversion. Change one field in your source and run again to check that the contact is updated.

​
How contacts are updated

Conversion matches contacts by email. Fields you send overwrite existing values by default; omitted fields are left unchanged. To fill only empty fields, set preserveExistingFields to true. To change an existing contact’s email, identify it with its cnvContactId. See Upsert Contact for the full request options.