In order to set up your BallotReady / Redshift integration, you will need to first allow-list an IP address. In the initial sync table(s) will be created in the specified schema.
If you are a Civis user, contact firstname.lastname@example.org with your static IP. Support at Civis will need to take the following steps to enable your setup of a BallotReady sync:
Allow-list the IP address provided to you by BallotReady in your Redshift cluster.
Create a Redshift user with permissions to read, write, and create tables in the destination schema.
For tighter security, you can use a specific schema for this data and only give permissions to that schema. If you do, make sure to send the schema name along with permissions.
By default the data will be written to the public schema. If you would like the table to be created somewhere else, provide the destination schema to BallotReady.
How often will the data sync?
The data will sync to Redshift hourly.
What should I expect to see in Redshift?
This sync will create two tables, one of user data and one with user actions. Depending on the BallotReady integrations you set up, this sync may include a third table with related IDs.
The events captured from BallotReady depend on the customized flow you have set up. Events will be added as BallotReady releases new features. Check here to see the most up to date list of events included as a part of this integration.
The three tables you will see in Redshift are outlined below: