> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create and Implement a Databricks Source

> Connect a Databricks table to Zeotap CDP as a data source using either the JDBC or Job-based connector.

This page is the complete reference for the Databricks source — components, prerequisites, and full setup. For a shorter setup-only walkthrough that skips the reference material, see [Set Up a Databricks Source](https://docs.zeotap.com/articles/integrate-customer/set-up-a-databricks-source.md).

## What this is

A Databricks source lets Zeotap CDP ingest data from a table in your Databricks workspace on a defined refresh schedule. Two connection mechanisms are supported — **JDBC**, which reads through a Databricks SQL warehouse, and **Job Based**, which runs a Databricks job to move the data. The Job-based approach is the recommended path for tables above 1 million records, since JDBC may encounter issues at that data volume. Data ingested from Databricks lands in either the **Customer Data** or **Non Customer Data** entity in Zeotap CDP.

## Prerequisites

> [!NOTE]
>
> Setting up a Databricks source requires access to your Databricks workspace with permission to create a service principal, generate the credentials for your chosen mechanism (OAuth Client ID and Client Secret, or a personal access token), and read the target table. You also need access to the Sources application in the Zeotap CDP App.

### Required permissions in Databricks

The user or service principal used for authentication must have:

* **Unrestricted Cluster Access**, or a cluster policy that permits creating the required node-type clusters.
* **SELECT** permission on the required tables.
* **USE SCHEMA** permission on the relevant schema.

### Components needed for every Databricks source

Obtain these four values from your Databricks account before you create the source in Zeotap CDP.

#### Databricks Host

The Databricks Host is the unique URL assigned to your Databricks workspace. You can find it in the URL for the Databricks account.

![The Databricks workspace URL in the browser address bar, which is the Databricks Host value](https://mintcdn.com/zeotap/5K-Zf-MYwWXwJWp5/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2025-09-02.png?fit=max\&auto=format\&n=5K-Zf-MYwWXwJWp5\&q=85\&s=8efd20803e181ac98cae733b8adb0b55)

#### Catalog Name

In Databricks, a catalog acts like a folder system. It organises schemas and databases into a hierarchy, allowing users to group tables and views logically.

![Catalog listing in the Databricks workspace](https://mintcdn.com/zeotap/ROPrHg77hrORMuiL/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2024-11-05-3.png?fit=max\&auto=format\&n=ROPrHg77hrORMuiL\&q=85\&s=b764ec431dd016bfa865230407675fd8)

#### Schema Name

In Databricks, a schema is essentially a database that contains tables. It serves as a container for organising and managing related tables, providing a structured way to store and retrieve data.

![Schema listed under a catalog in the Databricks workspace](https://mintcdn.com/zeotap/ROPrHg77hrORMuiL/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2024-11-05-4.png?fit=max\&auto=format\&n=ROPrHg77hrORMuiL\&q=85\&s=57c5bcaae32421ca4f5a510527224980)

#### Table Name

This is the name of the table within the schema that you want to ingest.

![Table listed under a schema in the Databricks workspace](https://mintcdn.com/zeotap/ROPrHg77hrORMuiL/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2024-11-05-5.png?fit=max\&auto=format\&n=ROPrHg77hrORMuiL\&q=85\&s=4dd2d856e9a3717341714e24f3dccdb8)

### Additional components for the JDBC mechanism

* **HTTP Path** of a Databricks SQL warehouse.
* **Client ID** and **Client Secret** from an OAuth service principal.
* **Partition Column** or **Unique Column** (see [Partition Column and Unique Column](#partition-column-and-unique-column)).

Before entering JDBC credentials in Zeotap CDP, complete the OAuth setup in Databricks by following the [Databricks OAuth M2M documentation](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html#authenticate-access-to-databricks-with-a-service-principal-using-oauth-oauth-m2m):

> [card] [1. Create a Service Principal](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html#step-1-create-a-service-principal)

> [card] [2. Assign Workspace-Level Permissions to the Service Principal](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html#step-2-assign-workspace-level-permissions-to-the-databricks-service-principal)

> [card] [3. Create an OAuth Secret for the Service Principal](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html#step-3-create-an-oauth-secret-for-a-service-principal)

#### Databricks Client ID and Client Secret

Before you can use OAuth to authenticate to Databricks, you must first create an OAuth Client Secret, which is used to generate OAuth access tokens. A service principal can hold up to five OAuth secrets. Account admins and workspace admins can create an OAuth secret for a service principal. For the specific procedure to generate the Client ID and Client Secret, see [step 3 of the Databricks OAuth documentation](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html#step-3-create-an-oauth-secret-for-a-service-principal).

To create a service principal and generate its **Client ID** and **Client Secret**, go to **Identity and Access → Service Principals → Add Service Principal → Generate Secret** in your Databricks workspace:

**1. Open Service Principals**

Go to **Identity and Access → Service Principals** and click **Add service principal**.

![Identity and Access settings in Databricks with the Add service principal action](https://mintcdn.com/zeotap/Ns0gcOUUBi0QRyu3/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-serviceprincipal-1.png?fit=max\&auto=format\&n=Ns0gcOUUBi0QRyu3\&q=85\&s=bb1b78309eb39a72c809ed383b466417)

**2. Add the service principal**

Select an existing service principal from your account, or create a new one, then click **Add service principal**.

![Selecting an existing service principal or creating a new one before clicking Add service principal](https://mintcdn.com/zeotap/Ns0gcOUUBi0QRyu3/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-serviceprincipal-2.png?fit=max\&auto=format\&n=Ns0gcOUUBi0QRyu3\&q=85\&s=833f29775fa7255983134649e292d6eb)

**3. Generate the secret**

Open the service principal, go to the **Secrets** tab, and click **Generate secret**. Copy the generated **Client ID** and **Client Secret** — the secret value is shown only once.

![Secrets tab of a Databricks service principal with the Generate secret action](https://mintcdn.com/zeotap/Ns0gcOUUBi0QRyu3/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-serviceprincipal-3.png?fit=max\&auto=format\&n=Ns0gcOUUBi0QRyu3\&q=85\&s=33d5635b191feb8c71761e23b0d21948)

#### HTTP Path

To locate the HTTP Path in Databricks, perform the following steps:

**1. Open SQL Warehouses**

Log in to your Databricks instance and, under **SQL**, click **SQL Warehouses**.

![SQL Warehouses entry under SQL in the Databricks navigation](https://mintcdn.com/zeotap/ROPrHg77hrORMuiL/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2024-11-05-2.png?fit=max\&auto=format\&n=ROPrHg77hrORMuiL\&q=85\&s=786342b8ffc6f9d8fe88409aa56afb66)

**2. Select the SQL warehouse**

Click the desired SQL warehouse. If no SQL warehouse exists, create one by clicking **Create SQL Warehouse**.

![SQL warehouse list in Databricks with the Create SQL Warehouse option](https://mintcdn.com/zeotap/ROPrHg77hrORMuiL/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2024-11-05.png?fit=max\&auto=format\&n=ROPrHg77hrORMuiL\&q=85\&s=6fd4fa7e86d85d85756e99fa0440e795)

**3. Open Connection details**

On the SQL warehouse summary page, go to the **Connection details** tab.

![Connection details tab on the Databricks SQL warehouse summary page](https://mintcdn.com/zeotap/ROPrHg77hrORMuiL/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2024-11-05-1.png?fit=max\&auto=format\&n=ROPrHg77hrORMuiL\&q=85\&s=af6894b0175c82e1ad94cbdc0cebbad2)

**4. Copy the HTTP Path**

Copy the **HTTP Path** value from the displayed information.

#### Partition Column and Unique Column

A **Partition Column** is a key used to organise large tables into smaller, logical groups. For example, data can be partitioned by date or region, so queries targeting a specific time range or location run much faster.

If no Partition Column exists on the source table, use any **Unique Column** instead — a column whose values are different in every row. When only a Unique Column is available, Zeotap CDP:

1. Creates a temporary view and runs the read queries over that view.
2. Drops the view once all the data has been fetched.

### Additional components for the Job-based mechanism

For the Job Based approach, select an **Auth Type** and provide the corresponding credentials. The supported auth types are **PAT Token** and **Service Principal**.

#### PAT Token

A Personal Access Token (PAT) can be generated in Databricks under **Settings → User setting → Developer → Generate new token**.

![Generate new token under Developer in the Databricks user settings](https://mintcdn.com/zeotap/5K-Zf-MYwWXwJWp5/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2025-09-02-1.png?fit=max\&auto=format\&n=5K-Zf-MYwWXwJWp5\&q=85\&s=f04fc7a25f5dca5e73352dd404159fc0)

**Required PAT scopes.** When using PAT authentication, the token must carry the following scopes:

* **jobs**
* **secrets**
* **sql**
* **unity-catalog**
* **workspace**

These scopes are required for:

* Creating and running jobs
* Managing secret scopes
* Accessing tables via SQL and Unity Catalog
* Creating notebooks and workspace artefacts

#### Service Principal

Provide the **Client ID** and **Client Secret** of your Databricks service principal. These are the same credentials used for the JDBC approach — see [Databricks Client ID and Client Secret](#databricks-client-id-and-client-secret) for how to create the service principal and generate the OAuth secret.

## Choose a connection mechanism

> [!TIP]
>
> Use **Job Based** for tables above 1 million records. Use **JDBC** for smaller tables and ad-hoc use cases where a SQL warehouse is already provisioned.

| Mechanism | Best for | Credentials required |
| :- | :- | :- |
| **JDBC** | Tables under 1M records | Client ID, Client Secret, HTTP Path, Partition or Unique Column |
| **Job Based** (recommended) | Tables above 1M records | An **Auth Type** — either **PAT Token** (Access Token) or **Service Principal** (Client ID and Client Secret) |

## Configure the source in Zeotap CDP

Once you have gathered the Databricks components, create the source in the Zeotap CDP App.

**1. Open the Sources application**

In the Zeotap CDP App, open the **Sources** application under **Integrate**, then click **CREATE SOURCE**.

**2. Select Data Warehouse as the category**

Under **Category**, choose **Data Warehouse**.

![Choosing Data Warehouse as the source category](https://mintcdn.com/zeotap/ROPrHg77hrORMuiL/articles/integrate-customer/Storage/integrate-customer/create-an-amazon-s3-source/sf_1_\(1\).png?fit=max\&auto=format\&n=ROPrHg77hrORMuiL\&q=85\&s=146e94f6110f76970d52baf2ab1e964b)

**3. Select Databricks as the data source**

Click **Databricks** as the Data Source.

![Selecting Databricks as the data source](https://mintcdn.com/zeotap/ROPrHg77hrORMuiL/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2024-10-21-5.png?fit=max\&auto=format\&n=ROPrHg77hrORMuiL\&q=85\&s=37be59c74bd04bf3496f418430749c73)

**4. Name the source and pick the region**

Enter a short, descriptive **Source Name** and choose the **Region** of upload.

**5. Set the Refresh Frequency**

Choose the **Refresh Frequency** from the drop-down. The first sync runs when the source is created; subsequent syncs follow the frequency you select. Supported frequencies:

* Sync once
* Every hour
* Every 3 hours
* Every 6 hours
* Every 12 hours
* Daily
* Weekly
* Monthly

For Daily, Weekly, and Monthly, set **Sync Time** (the exact time for the sync to occur), **Sync Period** (whether the Sync Time is AM or PM), and — for Monthly — the **Monthly Sync date** (the day of the month on which the sync should run).

**6. Enter host, catalog, schema, and table**

Enter your Databricks workspace URL in the **Databricks Host** field, followed by **Catalog Name**, **Schema Name**, and **Table Name**.

![Databricks Host, Catalog Name, Schema Name, and Table Name fields](https://mintcdn.com/zeotap/5K-Zf-MYwWXwJWp5/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2025-09-02-4.png?fit=max\&auto=format\&n=5K-Zf-MYwWXwJWp5\&q=85\&s=c6c91942a14f124511ef6abea3710a23)

**7. Choose the data entity**

Under **Data Entity**, select **Customer Data** or **Non Customer Data** depending on the type of data you are ingesting. For the distinction, see [Supported Data Entities](https://docs.zeotap.com/articles/unify-customer/supported-data-entities).

**8. Configure Delta Queries Selection**

Under **Delta Queries Selection**, decide whether to consider deltas (data additions and changes) in the table based on a timestamp column. Choose **true** or **false**:

![Delta Queries Selection with true and false options](https://mintcdn.com/zeotap/xcJBv790xp5wo6aA/articles/integrate-customer/Storage/integrate-customer/create-a-bigquery-source/create-a-bigquery-source-2023-05-22-9.png?fit=max\&auto=format\&n=xcJBv790xp5wo6aA\&q=85\&s=3a41aecd8ce7a3ca7b8f03b03280b736)

* **true** — only new and updated values, based on the timestamp in the delta column, are fetched. **Delta Column Name** and **Delta Column Data Type** become active: enter the name of the column to fetch data from, and choose the time increment for fetching the data from that column.
* **false** — no additional selections are needed. Zeotap CDP fetches all existing data from the table on every run.

![Delta Column Name and Delta Column Data Type fields shown when Delta Queries Selection is true](https://mintcdn.com/zeotap/xcJBv790xp5wo6aA/articles/integrate-customer/Storage/integrate-customer/create-a-bigquery-source/create-a-bigquery-source-2023-05-22-10.png?fit=max\&auto=format\&n=xcJBv790xp5wo6aA\&q=85\&s=5ef77403530a5665787eb96ce739fe03)

**9. Select the connection mechanism**

Select the mechanism used to pull the data. The currently supported options are **JDBC** and **Job Based**.

![Connection mechanism selection showing JDBC and Job Based options](https://mintcdn.com/zeotap/5K-Zf-MYwWXwJWp5/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2025-09-02-5.png?fit=max\&auto=format\&n=5K-Zf-MYwWXwJWp5\&q=85\&s=90edfec0123599c3d6bcaeeda1f6a399)

**10. Enter the credentials for the chosen mechanism**

**If you selected JDBC**, enter the following values (see [Additional components for the JDBC mechanism](#additional-components-for-the-jdbc-mechanism) for how to obtain them):

* Client ID
* Client Secret
* HTTP Path
* Partition Table Details (Partition Column Name, Partition Column Type)
* Unique Column Name

![JDBC credential fields for the Databricks source](https://mintcdn.com/zeotap/5K-Zf-MYwWXwJWp5/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2025-09-02-6.png?fit=max\&auto=format\&n=5K-Zf-MYwWXwJWp5\&q=85\&s=ae2a87fad3f52e8713dc654755e3ea57)

![Remaining JDBC credential fields on the Databricks source configuration screen](https://mintcdn.com/zeotap/5K-Zf-MYwWXwJWp5/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2025-09-15-1.png?fit=max\&auto=format\&n=5K-Zf-MYwWXwJWp5\&q=85\&s=58654c09340cad0db341df6ec4e2a1a6)

**If you selected Job Based**, choose the **Auth Type** and enter the corresponding credentials (see [Additional components for the Job-based mechanism](#additional-components-for-the-job-based-mechanism)).

If the Auth Type is **PAT Token**, enter the **Access Token**:

![Job Based mechanism with Auth Type set to PAT Token and the Access Token field](https://mintcdn.com/zeotap/Ns0gcOUUBi0QRyu3/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-jobbased-pat-token.png?fit=max\&auto=format\&n=Ns0gcOUUBi0QRyu3\&q=85\&s=f954325b8676c2dc6db56a863ca33b4e)

If the Auth Type is **Service Principal**, enter the **Client ID** and **Client Secret**:

![Job Based mechanism with Auth Type set to Service Principal and the Client ID and Client Secret fields](https://mintcdn.com/zeotap/Ns0gcOUUBi0QRyu3/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-jobbased-service-principal.png?fit=max\&auto=format\&n=Ns0gcOUUBi0QRyu3\&q=85\&s=c9bf3eea81751d43c3f275074d9eb6ff)

**11. Select the fields to ingest**

Click **Next** to proceed to field selection. A list of fields is displayed: tick the columns you want to ingest, use **Select All** to pick every column available in your Databricks account, or search by name if you already know the field names.

**12. Create the source**

Click **CREATE SOURCE**. The source appears on the Sources listing page.

### Field-level requirements

The fields a Databricks source configuration collects:

| Field | Required | Value |
| :- | :- | :- |
| **Source Name** | Always | A short, descriptive name for the source |
| **Region** | Always | The region of upload |
| **Refresh Frequency** | Always | Sync once, Every hour, Every 3 hours, Every 6 hours, Every 12 hours, Daily, Weekly, or Monthly |
| **Sync Time** | Daily, Weekly, Monthly | The exact time for the sync to occur |
| **Sync Period** | Daily, Weekly, Monthly | AM or PM |
| **Monthly Sync date** | Monthly only | The day of the month on which the sync should run |
| **Databricks Host** | Always | Your Databricks workspace URL |
| **Catalog Name** | Always | The catalog that holds the schema |
| **Schema Name** | Always | The schema within the catalog |
| **Table Name** | Always | The table within the schema |
| **Data Entity** | Always | Customer Data or Non Customer Data |
| **Delta Queries Selection** | Always | true or false |
| **Delta Column Name** | Delta Queries Selection = true | The timestamp column to fetch data from |
| **Delta Column Data Type** | Delta Queries Selection = true | The time increment for fetching the data |

Connection fields, by mechanism:

| Mechanism | Field | Required | Value |
| :- | :- | :- | :- |
| JDBC | **Client ID** | Always | OAuth client ID of the service principal |
| JDBC | **Client Secret** | Always | OAuth client secret of the service principal |
| JDBC | **HTTP Path** | Always | HTTP Path of the Databricks SQL warehouse |
| JDBC | **Partition Column Name** / **Partition Column Type** | When the table has a partition column | The partition key and its type |
| JDBC | **Unique Column Name** | When no partition column exists | A column whose value differs in every row |
| Job Based | **Auth Type** | Always | PAT Token or Service Principal |
| Job Based | **Access Token** | Auth Type = PAT Token | The Databricks personal access token, with the scopes listed above |
| Job Based | **Client ID** and **Client Secret** | Auth Type = Service Principal | The service principal's OAuth credentials |

## Verify the source is integrated

Open the source from the Sources listing and go to the **IMPLEMENTATION DETAILS** tab. A successfully created source shows all the relevant information about the created source on this tab and appears on the Sources listing with the **Integrated** status.

![IMPLEMENTATION DETAILS tab of a created Databricks source](https://mintcdn.com/zeotap/ROPrHg77hrORMuiL/articles/integrate-customer/Storage/integrate-customer/create-and-implement-a-databricks-source/create-and-implement-a-databricks-source-2024-10-21-8.png?fit=max\&auto=format\&n=ROPrHg77hrORMuiL\&q=85\&s=c46d108cec47e0fca57503d3d1dcdfac)

The first data transfer starts when the source is created; its duration depends on the volume of data in the source table.

## Troubleshooting

If the source does not reach **Integrated**, or the first sync does not produce data, check the conditions below.

| Condition | What it means | Where to look |
| :- | :- | :- |
| Authentication rejected during source creation | The Client ID or Client Secret does not have workspace-level permissions on the Databricks side | Re-run [step 2 of the Databricks OAuth setup](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html#step-2-assign-workspace-level-permissions-to-the-databricks-service-principal) to assign workspace-level permissions to the service principal |
| The Job Based mechanism cannot start its job | The authenticating user or service principal does not have **Unrestricted Cluster Access**, or the cluster policy does not permit creating the required node-type clusters | Databricks workspace → cluster access and cluster policies for the user or service principal |
| The table cannot be read even though authentication succeeds | The **SELECT** permission on the table or the **USE SCHEMA** permission on the schema is missing | Databricks → the target catalog, schema, and table permissions |
| A PAT-authenticated Job Based source fails | The personal access token is missing one of the required scopes (**jobs**, **secrets**, **sql**, **unity-catalog**, **workspace**) | Databricks → **Settings → User setting → Developer**; regenerate the token with all required scopes |
| First sync runs long for a large table | The JDBC mechanism was selected on a table above 1M records | Use the **Job Based** mechanism for tables above 1M records |
| No rows arrive after a delta-enabled sync | The **Delta Column Name** does not point at a timestamp that advances between runs | Zeotap CDP → source → **IMPLEMENTATION DETAILS** tab; re-check the Delta Column configuration against the source table |
| HTTP Path field rejected | The HTTP Path was copied from a different warehouse | Databricks → **SQL Warehouses → \<warehouse> → Connection details → HTTP Path** |

If the source configuration passes every check but no data arrives after the first refresh, contact the Zeotap support team at [support@zeotap.com](mailto:support@zeotap.com). Include:

* The source name and connection mechanism (JDBC or Job Based), and for Job Based the Auth Type.
* The refresh frequency.
* The timestamp of the last completed sync (if any).
* The Databricks catalog, schema, and table names.

## FAQ

> [accordion] Which connection mechanism should I pick — JDBC or Job Based?
>
> Pick **Job Based** for any table above 1 million records; JDBC may encounter issues at that data volume. For smaller tables, either mechanism works — JDBC reuses an existing SQL warehouse and needs the Client ID, Client Secret, HTTP Path, and either a Partition Column or a Unique Column.

> [accordion] Which Auth Type should I use for the Job Based mechanism?
>
> Both are supported. **PAT Token** needs a single Databricks personal access token carrying the **jobs**, **secrets**, **sql**, **unity-catalog**, and **workspace** scopes. **Service Principal** reuses the same **Client ID** and **Client Secret** you would generate for the JDBC mechanism, so it is the simpler choice if that service principal already exists.

> [accordion] What if the source table has no partition column?
>
> Provide a **Unique Column** instead — a column whose values are different in every row. Zeotap CDP creates a temporary view over the table to run the read queries and drops the view after all the data is fetched.

> [accordion] How long does the first sync take?
>
> The initial data transfer from Databricks to Zeotap CDP starts when the source is created and may take time depending on the data volume. Subsequent runs follow the Refresh Frequency and, when Delta Queries Selection is set to **true**, pull only the delta since the last successful sync.

## Next steps

* [Explore the shorter Databricks setup walkthrough →](https://docs.zeotap.com/articles/integrate-customer/set-up-a-databricks-source.md)
* [Explore the BigQuery source setup →](https://docs.zeotap.com/articles/integrate-customer/create-a-bigquery-source.md)
* [Explore the Amazon S3 source setup →](https://docs.zeotap.com/articles/integrate-customer/create-and-implement-an-amazon-s3-source.md)
* [Explore how to map ingested data in the Catalogue →](https://docs.zeotap.com/articles/unify-customer/map-the-catalogue-for-customer-data.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.