Connect CallTrackingMetrics
In the client’s workspace, open Sources, add CallTrackingMetrics and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.
Call tracking integration
Turn call tracking and conversation analytics into 20 governed metrics for dashboards, agent answers, and cross-channel reporting.
What you can do with CallTrackingMetrics in Maven
Maven models CallTrackingMetrics into 20 governed metrics from the semantic layer. Track Answered Interactions, Average Answered Interaction Duration, Avg Session Duration (s), First-Touch Events and Interaction Answer Rate, break results down by Event Type, Event, Touchpoint Source and Channel, and report CallTrackingMetrics alongside Google Analytics 4, Google Ads and Shopify without rebuilding exports or metric logic for every report.
What you can measure
Maven keeps CallTrackingMetrics numbers consistent across dashboards, reports, and answers so the team is not debating which spreadsheet is right.
Source-neutral interactions that were answered
Average duration in seconds among answered interactions
Average session duration in seconds with each session counted once
Touchpoints that opened a session
Share of represented interactions that were answered
Source-neutral interactions represented as attribution touchpoints
Touchpoints that closed a session
Phone interactions that were neither answered nor sent to voicemail
Total interaction duration in seconds
Journey touchpoint events recorded before conversion credit allocation
Source-neutral interactions that reached voicemail
Fractional conversion credit under the first-touch model by conversion touchpoint
Fractional conversion credit under the last-touch model by conversion touchpoint
Fractional conversion credit under the linear model by conversion touchpoint
Fractional conversion credit under the data-driven Markov removal-effect model by conversion touchpoint
Fractional conversion credit under the position-based model by conversion touchpoint
Fractional conversion credit under the data-driven Shapley-value model by conversion touchpoint
Fractional conversion credit under the time-decay model by conversion touchpoint
Canonical conversion/lead events counted through normalized last-touch weights
Questions you can ask
Maven’s agent answers in plain language with the right metric definitions applied automatically. These are real, verified questions it can run today.
Compare linear attribution weights by channel
Show attribution touchpoints by source
Connection and sync
You connect CallTrackingMetrics with API credentials from the CallTrackingMetrics account. Maven stores them encrypted. The first CallTrackingMetrics sync pulls the most recent 30 days so the workspace fills quickly. A follow-up backfill then adds older history, up to 12 months in total. After that, each scheduled sync re-reads the last 30 days, so late changes are picked up.
Normalized call-tracking events with caller identifiers hashed before storage.
Fields: tracking number, caller phone sha256, direction, status, answered, voicemail, duration seconds, qualified, revenue, source, and 6 more
How it works
No SQL or warehouse setup. Connect the source, then build the client’s report by asking Claude or ChatGPT.
In the client’s workspace, open Sources, add CallTrackingMetrics and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.
Maven pulls the client’s CallTrackingMetrics data (1 objects) and models it into documented tables. No SQL, warehouse or pipeline setup.
Build the client’s report or deck by asking Claude or ChatGPT through the MCP, set alerts on what matters, and publish to the client’s portal once you approve it.
Works well with
FAQ
Maven exposes 20 governed CallTrackingMetrics metrics, including Answered Interactions, Average Answered Interaction Duration, Avg Session Duration (s), First-Touch Events, Interaction Answer Rate and Interactions — each defined once so it means the same thing in every report.
You can break CallTrackingMetrics metrics down by Event Type, Event, Touchpoint Source, Channel, Source, Medium, Campaign and Utm Content, and more.
Yes. CallTrackingMetrics sits in the same client workspace as sources like Google Analytics 4, Google Ads, Shopify and HubSpot, so one report or question can use them together.
Maven syncs call tracking events from CallTrackingMetrics.
Maven refreshes CallTrackingMetrics on a schedule after the source is connected, and shows each source’s last sync time in the client’s workspace, so you can check the data is current before a report goes out.
Yes. Maven encrypts integration credentials and tokens, scopes access to the workspace, and uses the connection only to sync the reporting data needed for governed analytics.
Set up your first client, build their report by asking Claude or ChatGPT, and publish it to their portal.
Nothing is charged unless you subscribe.