--- title: "Export Data from Insider One to Databricks" slug: "export-data-from-insider-one-to-databricks" description: "Covers exporting Insider One data to Databricks via Delta Sharing: requirements, setup steps, accessing shared tables, and a cloud storage alternative." updated: 2026-09-29T10:57:38Z published: 2026-09-29T10:57:38Z canonical: "academy.insiderone.com/export-data-from-insider-one-to-databricks" --- > ## Documentation Index > Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt > Use this file to discover all available pages before exploring further. # Export Data from Insider One to Databricks Integrating Databricks as a destination lets you access Insider One event and user attribute data directly in your Databricks workspace through Delta Sharing. This allows you to analyze campaign engagement alongside your organization's other data. This article explains: - [What are the Databricks use cases?](/v1/docs/export-data-from-insider-one-to-databricks#use-cases) - [What are the requirements?](/v1/docs/export-data-from-insider-one-to-databricks#what-do-i-need-before-i-start) - [How can I configure Databricks as a destination?](/v1/docs/export-data-from-insider-one-to-databricks#how-can-i-configure-databricks-as-a-destination) - [How can I access the shared data in Databricks?](/v1/docs/export-data-from-insider-one-to-databricks#how-can-i-access-the-shared-data-in-databricks) - [FAQ](/v1/docs/export-data-from-insider-one-to-databricks#faq) This guide is intended for Databricks administrators or users responsible for configuring Delta Sharing. It walks you through generating the Databricks OpenSharing ID required by Insider One, configuring the destination integration, and making the shared data available in either a new or an existing Unity Catalog. ## Use Cases - **360-Degree Customer View** Combine Insider One campaign engagement data with your existing business data in Databricks to build a more complete customer view. - **Audience Segmentation** Build more precise audience segments by combining Insider One engagement data from 12+ channels and cross-channel journeys with your existing data in Databricks. - **Contact Data Enrichment** Enrich your existing customer profiles with marketing engagement and campaign interaction data. ## Requirements Insider One uses **Databricks-to-Databricks Delta Sharing (Open Sharing)** to share data with your workspace. Before you begin, review the [Databricks guide on reading shared data](https://docs.databricks.com/aws/en/opensharing/read-data-databricks) and make sure your Databricks account meets the following requirements: - **Unity Catalog privileges.** To accept a share, you must be a Metastore admin or hold the **USE PROVIDER** privilege. If you plan to create a new catalog for the shared data, you must also hold the **CREATE CATALOG** privilege. If you will mount the share to an existing catalog, this privilege is not required. - **Granting USE PROVIDER.** Only a Metastore admin can grant **USE PROVIDER**; no other user can grant it. If you are not a Metastore admin, ask your admin to grant it before you begin. - **Your Databricks OpenSharing ID.** You provide this ID during setup so Insider One can share data with your Databricks workspace. ## Configure Databricks as a destination To configure Databricks as a destination, follow these steps: 1. Navigate to **InOne** > **Components > Integrations > External Integrations**. 2. On the **All Platforms** tab, select **Databricks**. 3. Enter an Integration Name and select **Destination** as the Integration Type. Click **Save**. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-3K7SH99G.png) 4. Copy your Databricks OpenSharing ID. In your Databricks workspace, click your **profile avatar** in the upper-right corner and copy the **OpenSharing ID** (format `cloud:region:uuid`, for example `aws:us-east-2:xxxxxxxx-xxxx-xxxx`). ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-BXJLS0L9.png) 5. Return to Insider One. In the Authentication step, paste the value into the OpenShare ID field and click **Verify Authentication**. When verification succeeds, click **Save and Continue**. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-IUSR6LTQ.png) 6. On the Rules step, select the events you want to export, choose the event parameters to include, and optionally add additional user attributes. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-B0GHG8RA.png) 1. After you select an event, the Event Parameters section becomes available. Use the dropdown to choose which **event parameters** to include in the exported data. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1DDEG5EP.png) 2. You can also include additional **user attributes** with each exported event. For example, when exporting an **Email Open** event, you can include the user's email address to identify which recipient opened the campaign. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-DDZQH8DW.png) 7. On the **Launch** step, set the Launch Status to **Active**, set the **Sync Period** (up to 24 hours), add any notes, and review the **Before You Launch** checks. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-UDRD76M5.png) After the integration is launched, Insider One creates a **Delta Share** for your **OpenSharing ID** and starts syncing data according to the sync period you configured. ## Access the shared data in Databricks Delta Sharing lets you access shared data directly from Databricks without copying it into your workspace. Shared data does not occupy storage in your workspace, and you are billed only for the compute used to query it. After your integration is live, accept the share and mount it to a catalog: 1. In Databricks, open **Catalog**. Use **Share > OpenSharing** (shares you receive also appear under **Shares received** in the Catalog tree). ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-Z79B0YC5.png) 2. On the **OpenSharing** page, open the **Shared with me** tab. Insider One appears in the providers list as **insiderone**. Click it. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-54PUH3Z0.png) 3. Under the **insiderone** provider, find your share and click **Mount to catalog**. The provider details panel confirms information such as Region and Authentication type. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-CL4T9LC9.png) 4. In **Mount a share to a catalog**, choose **Create a new catalog**, enter a **Catalog name**, and click **Create**. (You can also mount to an existing catalog.) ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-CIX65YLC.png) 5. Your shared data appears under **Catalog Explorer > your catalog > schema > Tables**. Open a table to query your Insider One event data. Each shared table is a Delta table and includes columns such as your user identifier (`insider_id`), `timestamp`, `event_name`, and campaign fields such as `e_campaign_id` and `e_campaign_name`. The shared tables are Delta tables. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-J8YKHB26.png) > [!NOTE] > **What happens when you edit an integration?** > > Previously shared data remains available after you edit an integration. Each update creates a new table and view in the shared data. If you rename the integration, the new table and view use the updated name. Otherwise, only the timestamp suffix (YYYYMMDD_HHMMSS) changes. If multiple versions exist, use the table with the most recent timestamp to access the latest configuration. > [!NOTE] > Refer to [Databricks guide](https://docs.databricks.com/aws/en/opensharing/read-data-databricks) for further information on applying governance on shared tables. ## FAQ **Q: I can't see the data shared by Insider One in my Databricks account. What should I do?** **A**: Wait until the first sync completes and contains data. Then, in Databricks, open **Catalog > OpenSharing > Shared with me** and look for the **insiderone** provider. If you cannot find it, verify that you entered the correct **OpenSharing ID** during setup and that your account has the **USE PROVIDER** privilege (or Metastore admin access). If everything is configured correctly, allow a few minutes for the first share to become available. **Q: I get a permission error when accepting the share or creating a catalog.** **A:** Accepting a share requires **USE PROVIDER** (granted only by a metastore admin), and creating a catalog from it requires **CREATE CATALOG**. Ask your Metastore admin to grant the missing privilege. **Q: My Databricks workspace is on Azure or Google Cloud, or in a different region. Does this work?** **A:** Databricks-to-Databricks Delta Sharing works across clouds and regions. ## Related - [Export Data to Amazon S3](/export-data-to-amazon-s3.md) - [Export Data to Google Cloud Storage](/export-data-to-google-cloud-storage.md) - [Export Data from Insider One to Azure Blob Storage](/export-data-from-insider-one-to-azure-blob-storage.md)