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

# Use Databricks as destination

> Stream Kameleoon experiment exposure events into Databricks to enable centralized analysis and reporting of campaign results.

Once you have [enabled the Databricks integration for your project](./setting-up-databricks), you can activate **Use Databricks as a destination** to seamlessly send events to your Databricks account whenever visitors are exposed to one of your Kameleoon experiments.

<Frame>
  ![](https://storage.googleapis.com/kameleoon-storage-documentation/user-manual/images/integrations/data-warehouses/databricks/use-databricks-as-a-destination/Capture-décran-2025-07-07-à-16.33.12.png)
</Frame>

## Activate Databricks as a destination

To activate Databricks as a destination:

1. Click **Use Databricks as a destination**.
2. **Databricks catalog**: name of the Databricks "catalog" that will contain Kameleoon schema to write to (the top level folder).
3. **Schema**: Schema containing the tables this ingestion task will query from.

<Frame>
  ![](https://storage.googleapis.com/kameleoon-storage-documentation/user-manual/images/integrations/data-warehouses/databricks/use-databricks-as-a-destination/Capture-décran-2025-07-07-à-16.26.52.png)
</Frame>

## What "Databricks as a destination" does

Enabling **Use Databricks as a destination** will stream all Kameleoon experiment exposure events into Databricks.

Events will be stored in the `kameleoon_events` schema of your Databricks catalog — containing the tables this ingestion task will query from. This is the Databricks catalog you set up during [setup](./setting-up-databricks), with write access granted to the Kameleoon user. The data will be saved in a table named `kameleoon_experiment_event`.

The SQL schema of this table is the following:

```sql theme={null}
CREATE TABLE  kameleoon_experiment_event (
     nonce  BIGINT  PRIMARY KEY, -- unique identifier of the event
     timestamp  BIGINT, -- timestamp in millis of the event
     visitor_code  VARCHAR(255), -- Kameleoon visitor identifier
     custom_visitor_id  VARCHAR(255), -- Visitor identifier used by your company
     experiment_id  BIGINT, -- Kameleoon id of the experiment
     variation_id  BIGINT -- Kameleoon id of the variation
 );
```

The `custom_visitor_id` is read from the [Cross Device Reconciliation custom data](../../../../developer-docs/cross-device-experimentation), if it has been set.

With campaign data stored in Databricks, you gain the ability to perform in-depth analysis and reporting. You can leverage Databricks’s querying capabilities to extract valuable insights from the collected data, helping you make data-driven decisions to optimize your campaigns and user experience.

By centralizing Kameleoon campaign results in Databricks, you contribute to the enrichment of your Databricks database, making it a comprehensive repository of user data that can be used for a variety of analytical and business intelligence purposes.