Before you begin
- Set up the Conversion HTTP Request destination using the contact sync guide.
- Create a static audience in Conversion and copy its audience ID from the URL.
- Choose a Hightouch audience, or a model containing its members, with one row per contact and a stable, unique primary key. Hightouch uses this key to detect who joins or leaves.
- If sending fields, create them in Conversion first and use their writable keys from List Fields.
- Your API key needs contact create and edit permissions and edit access to the audience.
Create the sync
Open your Hightouch audience, click Add sync, and select the Conversion destination. If using a model, create the sync from that model instead. Use one sync per Conversion audience. Enable Rows added, Rows changed, and Rows removed.
Each trigger has its own endpoint and payload settings.
Add members and update contacts
Configure Rows added and Rows changed with the same settings:
Use Batch Upsert Contacts for added and changed rows.
AUDIENCE_ID with the ID from your Conversion audience URL, and replace the source column names with your own.

Map your source columns in the JSON editor. Use your own Conversion audience ID.
See Batch Upsert Contacts for all options. The standalone Add Contact to Audience endpoint is also available for adding existing contacts one at a time.
Remove members
Configure Rows removed separately:
Replace
AUDIENCE_ID with the same Conversion audience ID used above, and use this payload:

Send removed rows to the audience membership removal endpoint.
cnvContactId available in your source for both additions and removals.
Save and schedule
Complete the rate-limit, concurrency, timeout, and error-handling settings for each trigger. You can start with 1 concurrent request, a 30-second timeout, and Retry later for HTTP errors. Set a rate limit if required for your API usage. Under Rows added → Initial sync behavior, select Yes, backfill all rows to import existing members on the first run.
Backfill existing members when the sync first runs.

Choose when Hightouch checks for changes and sends them to Conversion.
Handling errors
Batch requests return HTTP200 with per-contact outcomes in data.results and a failure count in data.failed. An audience_add_failed result means the contact was saved but its membership could not be confirmed. These failures need response-aware retry handling; Hightouch’s HTTP-error retries do not catch errors inside a 200 response.