# How to Create an Audience in RudderStack


> Create an audience from a warehouse table and connect it to a destination.




**Announcement**

**This Audiences feature leverages the Reverse ETL workflow.**

To build targeted, no-code audience segments from warehouse data and activate them downstream, use [Lookout](https://www.rudderstack.com/docs/activate/lookout/) instead.

RudderStack provides a visual **Audience builder tool** which you can use to build audiences without any prior knowledge of SQL or how to store the data.

1. Log in to your [RudderStack dashboard](https://app.rudderstack.com).
2. From the left navigation bar, go to **Activate** > **Audiences** and click **New audience**.
3. Configure the settings explained in the following sections:

## Select source

Select the warehouse source for which you want to create an audience. RudderStack supports the Audiences feature for the following sources:

- [BigQuery](https://www.rudderstack.com/docs/sources/reverse-etl/google-bigquery/)
- [Databricks](https://www.rudderstack.com/docs/sources/reverse-etl/databricks/)
- [Redshift](https://www.rudderstack.com/docs/sources/reverse-etl/amazon-redshift/)
- [Snowflake](https://www.rudderstack.com/docs/sources/reverse-etl/snowflake/)
- [Trino](https://www.rudderstack.com/docs/sources/reverse-etl/trino/)

## Specify warehouse credentials

Specify the warehouse credentials to authenticate RudderStack. See the **Configure warehouse credentials** section of the [source-specific documentation](https://www.rudderstack.com/docs/sources/reverse-etl/#supported-reverse-etl-sources) (for example, [Redshift](https://www.rudderstack.com/docs/sources/reverse-etl/amazon-redshift/#configuring-the-connection-credentials)) for more details.

## Specify audience name and source

- **Source name**: Assign a name to uniquely identify the source in the RudderStack dashboard.
- Configure your audience source by specifying the below fields:

    - **Schema**: Select the warehouse schema from the dropdown.
    - **Table**: Choose the required table from which RudderStack syncs the data.
    - **Primary key**: Select the column from the above table that uniquely identify your records in the warehouse.

## Set audience conditions

You can set the required filtering conditions, view the corresponding SQL query and preview the resultant data from your data filters:

![Set conditions in audience](/docs/images/warehouse-actions-sources/set-condition-audience.gif)

You can add multiple filters within a condition by clicking **Add condition** or add multiple group filters by clicking **Add group condition**. Select **All** or **Any** to implement the AND or OR operator respectively between different filtering conditions.

![AND/OR conditions in audience](/docs/images/warehouse-actions-sources/and-or-condition-audience.webp)

Click **Preview** to see the results and verify if the audience conditions are correct. Click **Continue** to proceed.

## Review and complete setup

To make any changes to the warehouse credentials or audience configuration, click the edit icon present next to those sections.

![Edit audience configuration](/docs/images/data-pipelines/edit-audience-configuration.webp)

Once you have reviewed your configuration, click **Create source** to complete the setup.

To change the source configuration, description, or filter conditions later, see [How to Update an Audience](https://www.rudderstack.com/docs/activate/audiences/update-audience/).

## Connect audience to destination

To start using the newly-created source, you can connect it to:

- A new [destination](https://www.rudderstack.com/docs/destinations/overview/), or
- An existing destination that is **not already connected** to any other source.

To connect to a destination later, click **Done** on the top right:

![Next steps](/docs/images/retl-sources/created-source.webp)

You will then be redirected to the **Overview** page of the source where you will see the option of connecting it to a new or existing destination.

![Add destination](/docs/images/retl-sources/add-destination.webp)

See [Set up Reverse ETL Connection](https://www.rudderstack.com/docs/data-pipelines/reverse-etl/developer-guides/retl-connection-setup/) section for more information.

See [Supported Destinations](https://www.rudderstack.com/docs/activate/audiences/supported-destinations/) for the destinations you can connect to an audience.

When you set up data mappings, destinations that don't support audiences by default (for example, Salesforce, Customer.io, or HubSpot) require an [Audience Identifier](https://www.rudderstack.com/docs/activate/audiences/audience-identifier/). Facebook Custom Audience and Google Ads Remarketing Lists have audience support by default, so they don't show this setting.

## FAQ

#### Can I create a filter on the JSON columns in my warehouse table?

Yes, you can. Select the **Custom SQL filter** option from the dropdown and enter the corresponding SQL query, which includes the relevant filtering condition for the JSON column:

![Connect audience](/docs/images/warehouse-actions-sources/custom-sql-filter.webp)

#### What do the three validations under Verifying Credentials imply?

Once you proceed after entering the connection credentials, you will see the following validations under the **Verifying Credentials** option:

![Validating credentials](/docs/images/retl-sources/retl-credentials-validate.webp)

These options are explained below:

- **Verifying Connection**: Indicates that RudderStack is trying to connect to the warehouse with the information specified in the connection credentials. 

**Warning:** If this option gives an error, it means that one or more fields specified in the connection credentials are incorrect. Verify your credentials in this case.

- **Able to List Schema**: Checks if RudderStack is able to fetch all schema details using the provided credentials. 
- **Able to Access RudderStack Schema**: Checks if RudderStack has the required access to the `_RUDDERSTACK` / `_rudderstack` schema (depending on your warehouse). To create the schema, run all commands listed in the **Permissions** section of the respective Reverse ETL source documentation:

   - [BigQuery](https://www.rudderstack.com/docs/sources/reverse-etl/google-bigquery/#granting-permissions)
   - [Databricks](https://www.rudderstack.com/docs/sources/reverse-etl/databricks/#granting-permissions)
   - [Redshift](https://www.rudderstack.com/docs/sources/reverse-etl/amazon-redshift/#granting-permissions)
   - [Snowflake](https://www.rudderstack.com/docs/sources/reverse-etl/snowflake/#granting-permissions)
   - [Trino](https://www.rudderstack.com/docs/sources/reverse-etl/trino/#granting-permissions)

**Warning:** If this option gives an error, verify if you have successfully created the `_RUDDERSTACK` / `_rudderstack` schema and given RudderStack the required permissions to access it.

