Connectors overview

Converise is warehouse-first: instead of copying event data into another tool, you point a connector at a table in your warehouse. When an experiment is bound to that connector, Converise generates the aggregation query, runs it in the warehouse, and imports only the per-variant summary rows it needs for the review — KPI effects, quality checks, and the recommendation. Every import keeps source lineage (which connector, which query, when).

One connector serves many experiments. It carries the whole mapping contract — a data source (the table, view or SQL that holds outcomes, which column plays which role, an optional separate assignments table, the subject unit and the segment columns) and a KPI list (what counts as an outcome and how it is reduced per subject). Experiments then only pick an experiment key, tick KPIs and segments — and decide, per binding, whether evidence refreshes automatically once a day (off by default; each run bills warehouse queries) and at which UTC hour.

• Google BigQuery — service-account JSON key with read-only roles.
• Databricks SQL — OAuth service principal against a SQL warehouse.
• Snowflake — key-pair user with a read-only role.

GA4, Adobe Analytics, Adobe Target, Optimizely, Google Ads, Notion, and Confluence appear in the in-app catalog as coming soon. Their data usually reaches a warehouse export first, so the three warehouse connectors cover them today.

Presetsfill a connector's data source and KPIs for tools whose warehouse schema is known — today the GA4 BigQuery export (sharded events_* tables, variant from a user property, purchase revenue). A preset only produces a draft you can edit; the SQL it fills is visible on the SQL tab.

• Creating, editing, deleting, and refreshing connectors requires the admin or owner role. Members can upload evidence and bind experiments to existing connectors.
• Credentials are encrypted at rest and never returned to the browser. Always use read-only, least-privilege credentials — Converise only ever runs SELECT queries.
• The Check connection button in the connect form runs a trivial probe query against your warehouse before saving, so a typo in credentials fails fast instead of at the first refresh.