Skip to content
⌘K
InboxAsk a human

ClickHouse Integration

Updated by Vaishnavi

Connect ClickHouse to sync user and account attributes into Enterpret. Link those records to feedback to analyze it by plan, industry, region, or account.

Before you begin

You’ll need:

  • A publicly reachable ClickHouse HTTPS endpoint that Enterpret can access.

  • The database and table or view you want to sync.

  • A dedicated read-only ClickHouse user with SELECT access to that table or view.

  • One current row for each user or account, including the required columns below.

Required columns

Column names are case-sensitive.

Column

Requirement

ERC_ID

A non-null String containing a stable, non-empty identifier for the user or account.

ERC_CREATED_AT

A non-null DateTime or DateTime64 containing the original creation time.

ERC_ROW_CREATED_AT

A non-null DateTime64 with precision from 3 to 9. This should contain the time the current row version was written.

Other supported columns in the table or view become attributes in Enterpret. For example, you can include fields such as name, plan, industry, or account_id.

Keep one current row per ERC_ID. If your table stores multiple versions, connect a view that returns only the current row for each identifier.

ClickHouse SQL console showing two synthetic user rows with ERC_ID, ERC_CREATED_AT, ERC_ROW_CREATED_AT, name, account_id, and plan.

Example query results from a synthetic users source. Each user has one current row with the required columns and optional attributes.

Connect ClickHouse

1. Choose the integration type

  1. In Enterpret, go to Settings → Integrations.

  2. Select New Integration, choose ClickHouse, and select Continue. If ClickHouse is missing from the list, ask your Enterpret team to check availability for your workspace.

  3. Choose User Integration to sync people or Account Integration to sync companies.

Each connection points to one ClickHouse table or view. If you sync both people and companies, set up one User Integration and one Account Integration.

ClickHouse integration options showing User Integration and Account Integration.

Choose User Integration for people or Account Integration for companies.

2. Enter the connection details

Field

What to enter

ClickHouse Integration Name

A clear name, such as ClickHouse - Users or ClickHouse - Accounts.

Host

Your HTTPS hostname without https://, a port, or a path.

HTTPS Port

Your ClickHouse HTTPS port. ClickHouse Cloud commonly uses 8443.

Database

The database containing the table or view.

Table or View

The table or view containing the current user or account rows.

Username

The dedicated read-only ClickHouse user.

Password

The password for that user.

3. Choose the initial import

  • Enable Import all history to import all current rows.

  • Disable it and select a start date to limit the initial read by ERC_ROW_CREATED_AT, the current row version’s timestamp. This is not a filter on the original ERC_CREATED_AT time.

  • Set the Late-arrival Overlap window. Enterpret re-reads this period to capture delayed updates. The default is 60 minutes, and the maximum is 1440 minutes.

4. Validate and connect

Select Validate and Integrate. Enterpret checks the connection and required columns before creating the integration.

After the integration is created, review its sync status and the attributes discovered from your table or view.

A ClickHouse - Users integration with Active status, source details, import settings, and discovered metadata.

Example of an Active ClickHouse - Users integration connected to a synthetic source.

After the first sync completes, use the integration’s linking section to match identifiers between your user, account, and feedback sources. The matching fields must contain the same identifier format.

Adding a field such as account_id makes it available as an attribute, but does not configure the link automatically.

Discovered user attributes and the Link with Feedback and Account integrations section.

Review discovered attributes, then use the linking section below them to choose matching fields. The example does not show a configured link.

Keep changes syncing

  • Keep ERC_ID stable for each user or account.

  • Preserve the original value of ERC_CREATED_AT.

  • Whenever an attribute changes, update ERC_ROW_CREATED_AT to a later timestamp.

Enterpret uses ERC_ROW_CREATED_AT together with the overlap window to identify new and updated rows.

Troubleshooting

The connection cannot be validated

Check the hostname, HTTPS port, network access, credentials, and that the read-only user has SELECT access to the selected table or view.

The required columns are rejected

Confirm that the column names match exactly, use supported non-null types, and that ERC_ROW_CREATED_AT is DateTime64 with precision from 3 to 9.

Attributes are missing

Wait for the initial sync to complete and then check the discovered attributes again. If the sync is complete and attributes are still missing, contact Enterpret Support and include the integration name and any error shown.

User or account context is not linked to feedback

Review the matching fields in the linking section and confirm that both sources use the same identifier format.