Zeta

​

Supported syncing

For more information about sync modes, refer to the sync modes docs.

​

Connect to Zeta Global

Go to the Destinations overview page and click the Add destination button. Select Zeta Global and click Continue. You can then authenticate Hightouch to Zeta Global. Enter the following fields into Hightouch:

• Site ID: The site ID of your Zeta Marketing Platform account.
• REST API key: A REST API key generated in Zeta under Settings > Integrations > Keys & Apps. Refer to the Zeta documentation for more information.

​

Sync configuration

Once you’ve set up your Zeta Global destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Zeta Global destination you want to sync to.

​

Syncing contacts

Sync records to people in Zeta using Zeta’s identify endpoint. Hightouch creates the person if they don’t exist yet and updates them if they do.

​

Record matching

To match rows from your model to people in Zeta, you need to select a model column that maps to the person’s User ID. This should be the unique ID you use for the person in your own systems.

​

Field mapping

Hightouch lets you sync person fields via field mapping. You can map data from any of your model columns to the following Zeta fields:

• First name
• Last name
• Full name
• Email
• Phone: Phone numbers must be in E.164 format with a leading ”+” symbol.
• Signed up at
• Subscription status: Either active or inactive. When mapped, the status applies to the synced email and phone contacts.

Email and phone values are synced as entries in the person’s contacts in Zeta. You can also map any of your model columns to custom attributes on the person’s Zeta profile.

​

Syncing unsubscribes

Unsubscribe a person’s email address or phone number in Zeta using Zeta’s unsubscribe endpoint. This lets you manage subscription statuses from an external preference center while Zeta attributes the unsubscribe correctly. Each new row added to your model unsubscribes one of the person’s contacts. Zeta doesn’t have an API to resubscribe a contact, so this sync only processes added rows.

​

Record matching

To match rows from your model to people in Zeta, you need to select a model column that maps to the person’s User ID.

​

Field mapping

You must map the following fields:

• Contact value: The email address or phone number to unsubscribe.
• Contact type: Either email or phone. If all rows target the same channel, you can use a static value instead of a model column.

​

Syncing events

Sync records as events on a person’s Zeta profile using Zeta’s event tracking endpoint. When configuring the sync, you must enter an event name and select a model column that maps to the person’s User ID. You can optionally select a timestamp column; if you don’t, Zeta defaults the event’s timestamp to the time it receives the event. Any other columns you map are synced as the event’s properties.

​

Syncing audience lists

Add and remove people from an existing audience list in Zeta using Zeta’s bulk audience list endpoint. When configuring the sync, select the audience list to sync to. Hightouch lists your Zeta account’s static segments to choose from. To create a new list, use the Zeta Marketing Platform directly.

​

Record matching

To match rows from your model to people in Zeta, you need to select a model column that maps to the person’s User ID or email. Rows added to your model are added to the audience list; Zeta creates people that don’t exist yet on add. When rows leave your model, you can choose whether Hightouch removes them from the audience list or does nothing.

​

Tips and troubleshooting

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, .