Learn how to set up a Redshift source connection

Requirements for Connection

  1. Access to an AWS account and Amazon Redshift cluster
  2. The user has an admin role to access the Redshift cluster. This user must also have created schema privileges.
  3. Add the IP of GrowthLoop’s NAT in your Redshift Security Groups so that the web app can reach your Redshift instances. Reach out to [email protected] for the IP address.
  4. The redshift cluster must be spun up and connected to a database. Click Connect to the database. If a database is not connected to Redshift, the status will be blank and you need to click Change connection to connect to your database.

If the database is connected to Redshift, you will see the status Connected.

  1. Create schema flywheel_system in the Redshift cluster’s database. In the query editor, paste and run this command: create schema flywheel_system
  2. If you will be using Signal Routing, run this command in the Redshift cluster’s query editor: create schema signal_snapshots See for more information on signal routing with GrowthLoop.
  3. Redshift clusters must be publicly accessible. You can make that change in the Redshift UI. Select the cluster, click Actions, and Modify publicly accessible setting. Select Enable in the popup and Save changes.
Untitled Untitled

How To Connect in the App

  1. Visit the GrowthLoop application. If you were provided with a different application URL, use that.
  2. Sign up using your company credentials.
  3. If necessary, verify your email by clicking the verify link in the email sent to your email address.
  4. Return to the application and enter your Organization name and Industry. Click the checkbox to agree to the terms and then Continue.
  1. Select Redshift as the data warehouse you wish to connect to.
  1. Next, enter the required information to connect to Redshift:
    1. Name: name the connection to your data warehouse. This is somewhat arbitrary.
    2. Description: description of the connection to your data warehouse. This is somewhat arbitrary.
    3. Redshift username: username for the user that allows access to the Redshift cluster where your data is stored. This can be found on the Redshift cluster UI’s Properties tab, or in the Query Editor when it is connected to your database.
    4. Redshift password: admin user password for the user that allows access to the Redshift cluster where your data is stored. You can change the admin user password in the Redshift cluster UI’s Properties tab if necessary
    5. Database: name of the database that you want to connect to the app.
    6. Schema: name of schema for the table you want to connect to the app. For example, If you are looking to connect your user table to the app, select the user schema.
    7. Host: Database endpoint, without the port and database name.
      1. Copy the cluster endpoint. It should look have this format: :/
      2. Remove the port and database name, leaving just the host
        1. Example:
      3. Enter the edited host as the host in the app
    8. Port: Open the port to access the database. The port can be found in the Redshift cluster UI’s Properties tab, or as part of the database endpoint. The format of the endpoint is :/
  1. Select the dataset you wish to connect to the app.
  1. Select a table you want to connect to. You can add more tables later, as well.
  1. Add table alias and description
  1. Select the unique key, which uniquely identifies a database record.
  1. If required, select a device ID. The device ID is often used to target an individual during a marketing campaign, so it will be necessary to define the device ID before sending any data to a marketing destination.
  1. Select fields that you would like to see by default in the app when you create a new audience. Additional fields will be available in the app to manually add to an audience. Default settings can be edited at any time in the app.
  1. You have successfully connected your Redshift database to the app!