​

CDP BI-tool connectors

​

1. Pull into BI vs push via reverse ETL

• Reverse-ETL destinations (push) — Orbit writes your CDP entities into a destination (a warehouse, a martech endpoint, a webhook). Wire these when you fan data outward on a schedule.
• BI-tool connectors (pull) — your BI tool connects natively to the warehouse the reverse-ETL export already loads (BigQuery, Snowflake, Redshift, Postgres, or Databricks) and reads the curated datasets from there. No new pipeline, no new export — the warehouse export hub is the substrate, and the connector catalog is metadata over it.

​

2. Catalog listing

curl https://api.orbit.devotel.io/api/v1/cdp/bi-connectors \
  -H "X-API-Key: dv_live_sk_your_key_here"

• ?status= — ga, beta, or coming_soon.
• ?warehouse= — restrict to tools that connect to one warehouse (bigquery, snowflake, redshift, postgres, databricks).
• ?search= — a case-insensitive substring over the tool name, vendor, or description (≤100 characters).

• statuses — per-status facet counts over the full catalog (the filter sidebar).
• warehouses — the live warehouse list with each warehouse’s driver name.
• datasets — the curated analytics datasets (contacts, events, audiences, and campaigns) with their labels.

​

3. Per-tool metadata

curl https://api.orbit.devotel.io/api/v1/cdp/bi-connectors/tableau \
  -H "X-API-Key: dv_live_sk_your_key_here"

​

4. Connection-profile generation

curl -X POST https://api.orbit.devotel.io/api/v1/cdp/bi-connectors/tableau/connection-profile \
  -H "X-API-Key: dv_live_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "warehouse": "snowflake",
    "schema": "orbit_cdp",
    "dataset_keys": ["contacts", "events"]
  }'

• warehouse (required) — a live Orbit warehouse: bigquery, snowflake, redshift, postgres, or databricks.
• schema (optional) — the schema the export writes to; defaults to orbit_cdp.
• dataset_keys (optional) — restrict the profile to a subset of the curated datasets (≤20 keys); omit to include all four.

{
  "data": {
    "tool_id": "tableau",
    "status": "ga",
    "connection_available": true,
    "profile": {
      "tool": { "id": "tableau", "name": "Tableau" },
      "warehouse": {
        "id": "snowflake",
        "name": "Snowflake",
        "driver": "Snowflake (native connector / ODBC)"
      },
      "schema": "orbit_cdp",
      "connectionFields": [
        { "key": "account", "label": "Account identifier", "help": "e.g. xy12345.eu-west-1." },
        { "key": "warehouse", "label": "Virtual warehouse", "help": "Compute warehouse used to run BI queries." },
        { "key": "database", "label": "Database", "help": "The database Orbit reverse-ETL writes to." },
        { "key": "schema", "label": "Schema", "help": "The schema holding the Orbit tables." }
      ],
      "datasets": [
        { "key": "contacts", "label": "Contacts", "qualifiedTable": "orbit_cdp.orbit_profiles", "description": "..." },
        { "key": "events", "label": "Events", "qualifiedTable": "orbit_cdp.orbit_events", "description": "..." }
      ],
      "steps": [
        "In Tableau, add a new data source using the Snowflake connector (Snowflake (native connector / ODBC)).",
        "Point it at the Snowflake where Orbit's reverse-ETL export runs and select the 'orbit_cdp' schema.",
        "Add the Orbit tables you need: orbit_cdp.orbit_profiles, orbit_cdp.orbit_events.",
        "Use your own warehouse credentials — Orbit does not proxy warehouse access.",
        "Build dashboards directly on the tables; the reverse-ETL export keeps them up to date on its schedule."
      ],
      "notes": [
        "These tables are populated by Orbit's reverse-ETL warehouse export — enable that warehouse destination first.",
        "Refresh cadence in your BI tool should match the reverse-ETL export schedule to avoid stale rows."
      ]
    }
  }
}

• datasets are schema-qualified. Each entry names the fully qualified table (orbit_cdp.orbit_profiles for contacts, orbit_cdp.orbit_events for events, orbit_cdp.orbit_audiences for audiences). Campaign engagement reads from the events table filtered on the campaign_id property — it is a view over the event stream, not a separately loaded table, so the catalog describes it as such.
• No secrets, ever. connectionFields are labelled placeholders (account, host, database, schema — whatever the warehouse’s driver asks for), and the setup steps remind the analyst to authenticate with their own credentials. Orbit never proxies warehouse access, so the profile is safe to paste into a ticket or a runbook.
• Honest maturity. Every response echoes tool_id, status, and connection_available. A coming_soon connector still returns a profile for discovery, but the dashboard renders a request-access action rather than a connect button.

​

5. Auth and roles

​

6. Supported tools

​

Related guides

• Reverse-ETL warehouse exports — set up the BigQuery, Snowflake, or Redshift destination that populates the tables your BI tool reads.
• CDP reverse ETL operator walkthrough — the destinations panel, warehouse editor, and sync-run history behind the export.
• Destination and connector catalogs — the outbound (push) mirror of this catalog.
• CDP source and destinations console — the integrations page where warehouses are configured.
• Insights hub orientation — the dashboard’s native analytics surfaces when you do not need an external BI tool.