Whatagraph supports both.
They appear as separate sources in the source picker, and you can connect either depending on your account setup.
The core difference is how each connector handles data.
V1 relies on server-side aggregation: CTM's API returns pre-grouped, pre-computed data using a fixed schema, so you get a limited set of metrics (totals, averages, conversion rates) with no raw record access.
V2 fetches raw call-level records directly and computes all metrics in Whatagraph, giving you a far richer field set, a dedicated text message stream, and timezone-aware date handling.
Here's a table breaking down the key differences:
V1 | V2 | |
| Report types | Aggregations (deprecated), Groups, Series | Calls + Text Messages |
| Aggregation model | Server-side — CTM returns pre-grouped data | Client-side — raw records fetched, all metrics computed by Whatagraph |
| Text messages | Mixed into call streams | Separate dedicated stream |
| Metrics | Fixed schema: totals, unique counts, conversion rate, duration avg, talk/ring time avg, score min/max/avg | Computed from raw fields: call count, answered, missed, voicemail, abandoned, first call, duration, talk time, ring time, hold time, wait time, billed amount |
| Date handling | Basic date range | Timezone-aware, uses your account's stored timezone |
| Caching | None | 6-hour cache per source, date range, and page |
| Schema | Hardcoded | Dynamic field mapping |






