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

# ClickHouse

## Overview

Stigg's integration with ClickHouse allows you to export your product catalog, customer, and subscription data to ClickHouse for high-performance analytical queries.

<Note>
  Stigg's native data export integrations are included in the Scale plan, and are also available as an optional add-on to the Growth plan. See Stigg's pricing for more details.
</Note>

## Exported entities

When connecting ClickHouse, you can choose which Stigg entity groups to include in the sync. All groups are selected by default.

See [Exported entities](./overview#exported-entities) for the full list of entity groups and the tables within each.

<Card title="Entity schema" icon="sitemap" href="./schema" horizontal />

## Setting up the integration

### Prerequisites

You'll need a ClickHouse instance (self-hosted or ClickHouse Cloud) with a user that has permission to create tables and write data in the target database. ClickHouse connections also require a staging bucket (S3 or GCS) that Stigg uses to stage data before loading it into ClickHouse.

<Steps>
  <Step title="Connect Stigg with ClickHouse">
    In [Stigg](https://app.stigg.io/), navigate to **Integrations > Apps > ClickHouse**.

    Enter the following information in the connection form:

    | Field               | Description                                                                                                       |
    | ------------------- | ----------------------------------------------------------------------------------------------------------------- |
    | Host                | The hostname of your ClickHouse server                                                                            |
    | Port                | The port ClickHouse listens on. Defaults to `9000` for native TCP protocol.                                       |
    | Cluster             | The ClickHouse cluster name (if using a clustered deployment)                                                     |
    | Database            | The connection database                                                                                           |
    | Schema              | The database where Stigg will write tables. Can be the same as **Database**.                                      |
    | Username            | The ClickHouse user Stigg will authenticate as                                                                    |
    | Password            | The password for the ClickHouse user                                                                              |
    | Staging bucket type | The object storage used to stage data before loading it into ClickHouse. Select **S3**, **GCS**, or **Implicit**. |
    | Staging bucket      | The bucket name, region, and credentials used for staging. Not required if **Implicit** is selected.              |

    Click **Test & connect**.
  </Step>

  <Step title="Select entities to export">
    After entering your connection details, expand the **Entities to export** section to choose which entity groups to include in the sync. All groups are selected by default.

    See [Exported entities](./overview#exported-entities) for a description of each group.
  </Step>
</Steps>

## Sync process and schedule

After setup, Stigg performs a full sync of all selected entities. Subsequent syncs are incremental, transferring only changes since the last run.

Stigg syncs data on a configurable schedule — daily at 12:00 AM UTC by default. You can adjust the sync frequency from the integration settings at any time.

## Manual sync

To trigger an immediate sync, open the ClickHouse integration in [Stigg](https://app.stigg.io/) and click **Sync now**.

## Sync history

The integration page shows a log of all past and in-progress syncs. The dashboard updates automatically as syncs complete.

Each row shows the sync status and timestamps. Expand a row to see rows synced per entity, sync duration, trigger source, and who initiated it.

Use the status and date filters to find a specific sync run.

## Removing the integration

To remove the integration, click on the dotted menu icon and select the **Remove** action.

Confirm the action by clicking on the **Remove** button in the opened modal.