How Conversion works with Redshift
Conversion connects to Amazon Redshift as a dedicated database user and runs the SQL queries you write on a schedule you pick. Query results can create and update contacts, fill custom objects tied to contacts, or record events that start workflows. The connection is read-only and supports Redshift Serverless as well as private clusters reached through an SSH tunnel.
What syncs
| Data | Direction | Details |
|---|---|---|
| Contacts | Into Conversion | Matched by userId when the query returns one, otherwise by email. Creating a contact requires an email. |
| Custom objects | Into Conversion | Records of any custom object type, related to contacts through relationshipFields built with JSON_BUILD_OBJECT and cast to text. |
| Events | Into Conversion | Timestamped events on contacts. Supply an eventId and rows that sync twice are ignored. |
How to connect Redshift
- 1 Create a dedicated Redshift user for Conversion with USAGE on each schema and SELECT on the tables you want to sync.
- 2 Allow Conversion's IP addresses in the cluster's security group or firewall on your Redshift port, 5439 by default.
- 3 Add a Redshift connection in Conversion settings with the host, port, database, user, and password. Enable SSL, and SSH tunneling if the cluster isn't publicly accessible.
- 4 Create a sync for each destination with its SQL query and schedule.