CONNECT CALLTRACKINGMETRICS TO MUSE
Set up CallTrackingMetrics reporting in Muse
Adzviser retrieves the source data through its MCP reporting tools. Muse uses those results to answer your questions. Connect the source in Adzviser, then authorize Muse to use that connection.
Connect CallTrackingMetrics in Adzviser
Connect CallTrackingMetrics using your API access key and secret key. Add the source to the workspace you want to use in Muse.
Open Adzviser setup →Authorize Adzviser in Muse
Open Muse.ai and send: “Can you connect to custom Adzviser MCP at https://mcp.adzviser.com/http?” Select Connect on the Adzviser card, sign in to Adzviser, and select Complete Authorization via MCP. Return to Muse.
https://mcp.adzviser.com/httpVerify the first result
Ask Muse to list your Adzviser workspaces and their sources. Choose the workspace and confirm the account. Request a small report for a known period before expanding the analysis.
The Adzviser reporting connection is read-only. It can retrieve data for analysis; it cannot edit source records or campaigns.
A USEFUL FIRST CALLTRACKINGMETRICS REPORT
Review call handling before interpreting lead performance
Build a report you can check
For the last seven complete days and the preceding week, request calls, answered calls, missed calls, abandoned calls and average talk time using compatible tracking-source breakdowns. Keep inbound and outbound calls separate. Identify sources with a rising share or count of unanswered activity and show the underlying call volumes.
Use duration as context, not a quality verdict
A long conversation can be valuable, but duration alone does not prove a qualified lead or sale. A short call can also be successful. Keep any configured outcome or sale measure separate from call handling, and use the team’s actual qualification definition if you ask Muse to evaluate lead quality.
Identify the next operational question
Ask Muse for available date or time detail for the source with the largest missed or abandoned-call increase. Prepare a review of routing, coverage or follow-up, with the reported figures and the evidence still needed before assigning a cause.
Metrics for this report: Calls; Answered calls; Missed calls; Abandoned calls; Avg. talk time (sec).
Relevant breakdowns: Tracking source; Call direction.
These are starting fields, not a promise that every combination belongs in one report. Use separate requests for different reporting levels and check the full field catalog for additional coverage.
COPY INTO MUSE
Run your first CallTrackingMetrics analysis
Paste this after connecting. Change the period or research subject to match your question, and let Muse confirm the selection before retrieving results.
Use Adzviser to analyze CallTrackingMetrics. List my workspaces and ask which connected account to use. For the last seven complete days and the preceding week, request calls, answered calls, missed calls, abandoned calls and average talk time using compatible tracking-source breakdowns. Keep inbound and outbound calls separate. Identify sources with a rising share or count of unanswered activity and show the underlying call volumes. Use these metrics in compatible reports: Calls, Answered calls, Missed calls, Abandoned calls, Avg. talk time (sec). Relevant breakdowns: Tracking source, Call direction. Check field compatibility and use separate tables for different reporting levels. State the actual reporting dates or observation window. Show the supporting rows, then give a short conclusion and one next investigation. Label missing data and separate observed changes from possible explanations.
