Local marketing agencies
Show each client the calls their ads, listings and website produced.
Read inbound calls by day and tracking source, calls by tracking number and a call log of calls, texts and forms from CallTrackingMetrics, including every sub-account of an agency. You can allow teammates and AI tools to add or remove call tags, add notes to calls and record sales on calls. Allowed changes apply right away and are recorded in history.
Start free Connect CallTrackingMetrics
Updated November 2026
| Tracking label | Calls | Answered calls |
|---|---|---|
| Google Ads · Emergency | 220 | 153 |
| Website | 136 | 95 |
| Business Profile | 126 | 93 |
Show each client the calls their ads, listings and website produced.
See which campaigns bring calls, and how many are answered.
Line up ad clicks with the calls they led to.
One key stays bound to each data source.
Changes stay off until you allow them. Allowed changes apply to CallTrackingMetrics right away, and history keeps the values before and after.
Dates go back up to 90 days and follow each account’s time zone. Caller names, numbers, locations, recordings and transcripts are never read into reports.
Compare inbound, answered and missed calls and first-time callers for every tracking source, day by day.
Rank every tracking number by calls for the month and spot the listing or campaign that stopped ringing.
A teammate records a sale on yesterday’s call from the Google Ads number, so reports show what that call was worth.
See the problem in your report, then make the fix in Datapipe instead of opening CallTrackingMetrics, finding the record and retyping it.
Teammates and AI tools you allow can make changes without getting edit access to CallTrackingMetrics.
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
TodayOpen each call in CallTrackingMetrics and add the tag.
With DatapipeA teammate tags yesterday’s booked calls from the Call log report, so the client sees booked jobs by source.
TodayFind the call and edit its tags by hand.
With DatapipeRemove the tag from the call in Datapipe; history keeps who changed it.
Adds one tag to a call, text or form, or removes it. Other tags stay as they are. Tag-based triggers and integrations set up in CallTrackingMetrics may run.
Supported fields: Change, Tag.
TodayOpen the call and type a note.
With DatapipeAdd a note that the caller asked for a quote next week, so the client’s team follows up.
TodayMessage the client separately.
With DatapipeClaude adds a note to missed calls during the office closure explaining the gap.
Adds one note to a call, text or form. Existing notes are kept.
Supported fields: Note.
TodayAsk the client and update the call by hand.
With DatapipeRecord a score of 5, converted, and $450 on the call that booked a boiler repair.
TodayListen to calls and score them in CallTrackingMetrics.
With DatapipeA teammate scores the week’s calls from 1 to 5, so reports show which sources bring good leads.
Creates or replaces the sale record on one call with a score, whether it converted, and optionally its value and date. CallTrackingMetrics uses it in its own sales reports.
Supported fields: Score (1 to 5), Converted, Sale value in dollars, Sale date (YYYY-MM-DD).
| Field | Before | After |
|---|---|---|
| Sale | No sale | Score 5 · Converted · $450 |
Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?
Provider permissions still apply, and automations in CallTrackingMetrics may react to changes.
Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.
An API key or token from your CallTrackingMetrics account.
Read access for reports. The 3 change actions need edit access in CallTrackingMetrics and stay off until the owner, an admin or a project manager allows them.
Caller names, numbers, locations, recordings and transcripts are never read into reports. Activity marked as excluded is left out.
Read every account a CallTrackingMetrics key can see, including the sub-accounts of an agency: inbound calls by day and tracking source, calls by tracking number, and a call log of calls, texts and forms with status, talk time and tags. Dates go back up to 90 days and follow each account’s time zone. Caller names, numbers, locations, recordings and transcripts are never read into reports.
Uses a CallTrackingMetrics access key and secret key from API Integration in Account Settings, or in Agency Settings for every sub-account. The same key covers reports and call tags, notes and sales. CallTrackingMetrics includes this access from its Marketing Pro plan.
Dates go back up to 90 days. Days follow each account’s time zone. Activity marked as excluded is left out. Caller names, numbers, locations, recordings and transcripts are not included.
3 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
One row per account, day and tracking source: inbound calls, answered and missed calls, first-time callers, talk and call time, plus outbound calls, texts and form submissions. Days follow the account’s time zone, as each call record gives it. Activity CallTrackingMetrics marks as excluded is left out.
One row per account and tracking number for the selected dates: its label and source, inbound calls, answered and missed calls, first-time callers, and talk and call time. Activity marked as excluded is left out.
One row per call, text or form in the selected dates, with when it happened in the account’s time zone, its direction, tracking source and number, status, talk, ring and hold time, whether the caller was new, and its tags. Caller names, numbers, locations, recordings and transcripts are never included.
42 report fields across 3 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
AI tools can also make allowed CallTrackingMetrics changes. They can never widen their own access.
Which source brought CallTrackingMetrics the most first-time callers in the last 30 days, and how many of their calls were answered?
Google Ads brought the most first-time callers. About seven in ten of its calls were answered.
One row per account, day and tracking source: inbound calls, answered and missed calls, first-time callers, talk and call time, plus outbound calls, texts and form submissions.
Use this template →One row per account and tracking number for the selected dates: its label and source, inbound calls, answered and missed calls, first-time callers, and talk and call time.
Use this template →One row per call, text or form in the selected dates, with when it happened in the account’s time zone, its direction, tracking source and number, status, talk, ring and hold time, whether the caller was new, and its tags.
Use this template →Create a project and choose CallTrackingMetrics in Data sources.
Pick where it goes. This one sends the numbers to BigQuery.
Pick where it goes. Choose calls by day and source or another dataset, the dates and a destination.
Sample tracking-number report for the last 30 days across an agency’s accounts. Calls are inbound phone calls; answered and first-time callers come from each call record.
| Tracking label | Calls | Answered calls | First-time callers | Tracking source |
|---|---|---|---|---|
| Google Ads · Emergency | 220 | 153 | 142 | Google Ads |
| Website | 136 | 95 | 75 | Google Organic |
| Business Profile | 126 | 93 | 67 | Google Business Profile |
Sample numbers, so you can see the shape. Your report uses your accounts.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.
No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected CallTrackingMetrics account. Nobody else gets a CallTrackingMetrics login from this.
Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.
Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.
Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that CallTrackingMetrics received it, the request is marked Uncertain and is never retried automatically, so you can check CallTrackingMetrics first.
Yes. Datapipe reads the reports on this page and can make 3 kinds of change: add or remove a call tag; add a note to a call; record a sale on a call. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.
This page lists 42 report fields across 3 datasets. You pick the columns when you build the report.
Read every account a CallTrackingMetrics key can see, including the sub-accounts of an agency: inbound calls by day and tracking source, calls by tracking number, and a call log of calls, texts and forms with status, talk time and tags. Dates go back up to 90 days and follow each account’s time zone. Caller names, numbers, locations, recordings and transcripts are never read into reports. Account permissions and the records available from the provider determine which rows can be read.
One for each CallTrackingMetrics account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Build the report first, then add CallTrackingMetrics when you are ready.