Can I connect Segment event data to iDBQuery?
The most reliable route is to query the warehouse Segment already loads your events into: connect that database and iDBQuery makes tracks, identifies, and pages a live queryable model. Segment is a pipeline that lands data in your warehouse, so iDBQuery queries the destination rather than the collection API.
Segment is a customer-data pipeline: it collects events and routes them to destinations, most importantly a warehouse (BigQuery, Redshift, Snowflake, Postgres and similar). Because Segment's job is to move data somewhere queryable, the truthful and reliable way to analyse it in iDBQuery is to connect that warehouse as a standard SQL source. iDBQuery then treats your Segment schemas, the tracks, identifies, pages, and per-event tables, as part of one live model you can question in plain language.
With Segment events in the model you can ask:
- What is my signup-to-activation funnel by acquisition source this month?
- How many weekly active users did we have, and how does that trend by cohort?
- Which events precede conversion most often?
Every figure is cited to the underlying event rows. The advantage is joining behavioural events to the rest of your business: connect the Segment warehouse alongside your billing database or CRM and answer questions like revenue by first-touch channel or retention by plan, in one place. iDBQuery is not a Segment destination itself and does not receive the raw event stream; it queries where Segment already delivers the data. If your events are not yet in a warehouse, you can also export a table to CSV and ingest that. Either way the plain-language question stays the same.
Updated 2026-06-22