/ INSIGHT

Protect Revenue With Call Tracking in Google Ads: 4 Step Setup for Agencies

Turn Google Ads call tracking into revenue protection. MMG's checklist covers DNI or forwarding numbers, CRM imports, call scoring, and Smart Bidding.

Specialist verifying call attribution data

Enable account-level call reporting, create a Calls conversion action with a minimum duration threshold, and route every call through a Google forwarding number or a trusted dynamic number insertion (DNI) setup. Then feed only qualified calls, whether scored by Google’s AI or verified in your CRM, into Smart Bidding as conversions. Skip any of these four pieces and you’re optimizing toward noise instead of revenue.

TL;DR:

  • Using only native Google forwarding numbers may cause mismatched local area codes, potentially limiting call volume for local service businesses.
  • Proper call quality filtering relies on setting an appropriate minimum call duration; AI scoring is only available in supported regions like the US and Canada.
  • CRM importing of verified revenue-generating calls requires precise data formatting and validation to avoid rejection and ensure accurate measurement.
  • Smart Bidding benefits from validated, revenue-weighted call conversions; relying solely on call duration can inject noise into bidding signals.
  • Continuous technical validation, including tag firing and number swapping, is essential to maintaining accurate call tracking and maximizing its impact on campaign performance.

Table of Contents

What Do You Need Before Setting Up Call Tracking in Google Ads?

Before you touch a single setting, confirm five things. Skipping this checklist is the single biggest reason call tracking implementations stall halfway through a launch.

  • Admin access and verified billing on the Google Ads account. Call reporting and conversion imports both require account-level permissions, not just campaign editing rights.
  • Call reporting enabled in account settings, with at least one call asset or location asset already attached to a campaign. Google won’t assign a forwarding number without something to attach it to.
  • Website access to add the global site tag (or a Google Tag Manager container) and the phone snippet, ideally with a developer who can deploy in the same day.
  • A clear decision on whether you’re using Google’s native forwarding numbers alone or pairing them with a third-party DNI provider that pushes data into your CRM.

That last decision shapes everything downstream. A business running one location with straightforward call volume rarely needs more than Google Ads Help’s native forwarding number setup. A multi-location business, an agency managing several clients, or a team that needs keyword-level attribution beyond what Google reports usually needs DNI layered on top. Decide this now, because it determines which tag you install in the next section.

How Do Google Forwarding Numbers Actually Work?

Google forwarding numbers work by swapping the phone number on your website with a Google-owned number the moment call reporting is turned on. When someone clicks your ad, lands on your site, and dials that swapped number, Google tracks the call and reports it back to your account.

Google tries to match your area code when a local number is available, but it will fall back to a toll-free number when local inventory runs out. That’s a real limitation worth planning around, especially for local service businesses where a mismatched area code can suppress call volume from cautious callers.

A few operational realities matter here:

  • Forwarding numbers are Google’s property. You can’t repurpose them outside of Google Ads reporting or list them anywhere else.
  • Numbers can change or get reassigned, so never hardcode a forwarding number into print materials or other channels.
  • Call recording and caller-level details are limited by geography and consent rules. Recording generally requires both parties to be in a supported region, and Google’s AI-qualified call leads documentation makes clear this runs under separate supplemental terms.

Pro Tip: If you manage call tracking for more than one location or need persistent visitor-level attribution that survives across sessions, a third-party DNI provider will usually outperform native forwarding. Google’s own reporting explains the trade-off directly: native forwarding is free and simple, but limited compared to a DNI pool built for keyword-level detail.

How Do You Create a Phone Call Conversion Action in Google Ads?

Setting up the conversion action correctly is where most PPC managers either lock in clean data or quietly poison their own bidding signals for months.

  1. Navigate to Tools & Settings > Conversions > New Conversion Action, then select “Phone calls” as the category.
  2. Choose your call source. Google Ads offers three options: calls from ads using call extensions or call-only ads, calls from website visits using the forwarding number and phone snippet, and calls that come in through an uploaded or imported CRM feed.
  3. Set a minimum call duration. This is your single most important quality filter. A common starting point is a minute or so, though service businesses with longer discovery calls often set a higher minimum call duration. Whatever number you land on, this filter stops a 4 second hang up from counting as a conversion.
  4. Toggle “Include in Conversions.” Leave this on if you want the call to influence Smart Bidding. Leave it off (while still tracking it under “All conversions”) if you’re still validating call quality and don’t yet trust the signal.
  5. Save, then place a test call from a device outside your office network to confirm the conversion registers in the Call Details report within a few minutes.

The distinction between “Conversions” and “All conversions” isn’t cosmetic. Google’s own measurement guidance confirms that calls can be scored either through AI analysis of the recording or through simple duration thresholds, and that scoring method should decide whether the call belongs in your primary optimization column.

Pro Tip: Run the conversion action in “All conversions” mode for the first one to two weeks. Watch actual call quality against your duration threshold before you let Smart Bidding treat it as a primary signal.

How Do You Implement Call Tracking on Your Website?

Website implementation is where the technical handoff between PPC and development either goes smoothly or eats two weeks of back and forth over Slack.

Start with the basics: install the global site tag site wide, then add the phone number snippet to every page that displays a clickable number. The phone number text on your site must match the format Google expects exactly, down to spacing and punctuation, or the swap won’t trigger.

If you’re using Google Tag Manager instead of hardcoding the tag, the setup looks like this:

  • Create a new tag using the built in “Google Ads Conversion Tracking” template, select “Calls from website” as the type.
  • Enter your conversion ID and conversion label from the conversion action you built earlier.
  • Set the trigger to fire on all pages where a phone number appears, typically “All Pages” unless you’re isolating a specific landing page template.
  • Publish the container and confirm the tag fires using Google Tag Assistant before pushing live.

If you’re layering DNI on top of native forwarding, the Twilio glossary on dynamic number insertion frames it well: DNI is essentially the offline equivalent of a web cookie for phone calls. It swaps the visible number per visitor and stores that visitor’s traffic source, so a call three days later still ties back to the exact keyword or campaign that drove the click. Vendors like CallRail describe a similar mechanic, using a pool of tracking numbers to capture click IDs and pass conversions back to Google Ads.

Watch for three recurring pitfalls: international numbers formatted with a plus sign that breaks the matching logic, DNI scripts that time out on slow-loading pages before the swap completes, and templates that only support one phone number per page when your site actually needs several for different departments.

Pro Tip: Always validate with Tag Assistant before calling implementation done. A tag that “looks right” in the GTM preview mode can still fail silently on a live page with a caching layer in front of it.

What’s the Difference Between AI-Qualified Calls and Duration-Based Calls?

Google Ads measures call quality two different ways, and knowing which one is active in your account changes how you should set thresholds.

When call recording is enabled and both parties are located in a supported region, currently the United States and Canada, Google’s AI can analyze the recording itself to judge whether the call represents a genuine lead. When recording isn’t available or isn’t permitted, Google falls back to counting any call that exceeds your set minimum duration. Google’s measurement documentation confirms this fallback behavior directly, and it matters because a business assuming AI scoring is active, when it’s actually running on duration alone, will misjudge what its conversion numbers actually represent.

A few practical rules for keeping this signal clean:

  • Set your duration threshold high enough to filter out wrong numbers and voicemail hangups, but not so high that it excludes short, high-intent calls like “what are your hours.”
  • If recording is enabled, disclose it in your privacy policy and confirm your account-level recording toggle matches what your legal team has approved.
  • Review the Call Details report monthly for calls sitting right at your threshold. That’s usually where quality erodes first.

Account-level call reporting itself provides the call duration and start time data that both scoring methods depend on, as Google’s own call reporting overview lays out. Getting that foundational reporting right is what makes either scoring method trustworthy in the first place.

How Do You Import Call Conversions From a CRM?

Importing conversions from your CRM is how you tell Google Ads to stop guessing and start counting only the calls that actually turned into revenue.

  1. Build your export file with three required fields at minimum: the caller’s phone number in a consistent format, the call’s exact start time including time zone, and the conversion action name that must match character for character what you built in Google Ads.
  2. Choose your upload method. Manual CSV upload works for occasional testing. Scheduled uploads through Google Sheets or an HTTPS/SFTP connection work for ongoing automated feeds. API-based imports fit teams with enough volume to justify direct system integration.
  3. Run a small test batch first, ten to twenty rows, before scheduling a full automated feed. Confirm the conversions appear in the Call Details report with the correct value and timestamp.
  4. Watch for the three failures that cause the most import rejections: a conversion name that doesn’t exactly match the action in your account, a timezone mismatch between your CRM export and Google’s expected format, and duplicate rows from a CRM that re-exports the same call twice.

Google’s import documentation is explicit about formatting requirements, and getting them wrong is the number one reason teams give up on CRM imports after one failed attempt. The payoff for getting it right: you’re now counting only verified sales, not every call that happened to clear your duration threshold. That distinction is what preserves data quality for lead qualification further downstream.

How Do Call Conversions Affect Smart Bidding?

Smart Bidding treats every conversion in your “Conversions” column as a signal to optimize toward, which means a sloppy call conversion setup doesn’t just misreport performance. It actively steers your bids toward the wrong audience.

Keep “All conversions” as your measurement view while you’re still validating call quality, and only flip qualified calls into the primary “Conversions” column once you trust the signal. Google’s algorithm needs enough volume to learn from, and generally accepted guidance is to have a healthy number of qualifying conversions per month per campaign before Smart Bidding has enough data to optimize reliably. Give it two to three weeks after any threshold change before judging results.

  • Exclude short or low-scored calls from your Conversions column entirely; let them show up in All conversions for visibility only.
  • Use call scoring, whether AI-based or CRM-verified, to separate real leads from tire kickers before they touch your bidding data.
  • Tie call value back to actual revenue where possible. Passing dollar values instead of a flat conversion count lets Smart Bidding optimize toward cost per lead and lifetime value rather than raw call count, which vendors report improving CPL and ROAS at the portfolio level.

Pro Tip: If you manage several campaigns, set up portfolio bidding once call values are flowing in cleanly. It lets Smart Bidding allocate budget toward the highest-value call sources rather than treating every campaign in isolation. MMG’s PPC management team builds this exact feedback loop for clients moving from flat conversion counts to revenue-weighted bidding.

How Do You Validate That Call Tracking Is Working?

Run this sequence before you trust a single number in your reports.

  1. Click your own ad from a device outside your office IP, land on the site, and confirm the phone number displayed has swapped to a Google forwarding number or your DNI provider’s tracking number.
  2. Place a test call that clears your minimum duration threshold, then check the Call Details report for that call within roughly 15 minutes.
  3. If nothing shows up, check the four usual suspects: an inactive tag, a phone number format mismatch between your site text and what the snippet expects, a forwarding number that failed to generate for that ad group, or a conversion label typo.
  4. Use Google Tag Assistant to confirm the tag actually fires on page load, not just that it exists in the container.
  5. If problems persist past one round of fixes, that’s your signal to bring in developer support or migrate to a third-party DNI platform with better debugging tools.

How Should Agencies Operationalize Call Tracking as Infrastructure?

Treating call tracking as a one-time setup task is how conversion data quietly degrades over a quarter. MMG’s implementation model runs it as infrastructure instead: DNI paired with Google forwarding where native tracking falls short, CRM import for revenue-verified conversions, ongoing call scoring, and a feedback loop back into Smart Bidding.

The handoff typically splits three ways. Development deploys the tag and phone snippet. The PPC lead builds and tests the conversion actions. Sales confirms the CRM field mapping matches what Google Ads expects for import. Most implementations run one to two weeks from kickoff to validated data. For teams tracking broader account health alongside call data, MMG’s industry updates cover how these signals interact with organic and paid visibility over time.

Why Most Call Tracking Setups Fail Before They Ever Reach Smart Bidding

Most guides on this topic treat call tracking as a checkbox: turn on call reporting, done. That framing misses the actual failure point. The setup itself is rarely the problem. What breaks is the assumption that every call that clears a duration threshold represents real revenue.

Conventional advice treats duration as a proxy for quality and stops there. It isn’t. A 90 second call can be a wrong number that rambled, and a 45 second call can be a closed sale. Duration is a filter, not a verdict, and treating it as gospel is how businesses end up training Smart Bidding on noise while believing they’ve built a clean data pipeline.

The teams getting real value out of this are the ones pairing duration thresholds with CRM verification and actual call scoring, then feeding revenue value, not just a binary conversion flag, back into bidding. That’s a bigger operational lift than flipping on call reporting, and it’s exactly why so few advertisers do it. Prioritize CRM import and call scoring over chasing more call volume. Volume without verification just gives Smart Bidding more bad data to optimize toward.

- Vector

How MMG Turns Call Tracking Into a Revenue Protection System

Most agencies stop at “turn on call reporting and hope the numbers look good.” Monstrousmediagroup builds the entire pipeline, DNI implementation, CRM import mapping, call scoring, and Smart Bidding feedback, as one connected system instead of a checkbox you configure once and forget.

Monstrousmediagroup

That matters because clean conversion signals compound. A campaign feeding verified, revenue-weighted calls into Smart Bidding for three months outperforms one still optimizing toward raw call counts, and the gap widens every week the bad data keeps flowing. MMG’s team handles the full buildout: forwarding number configuration, GTM deployment, CRM field mapping, and the ongoing call scoring that keeps your Conversions column trustworthy instead of noisy.

If your current setup counts every call over 60 seconds as a win without checking whether any of them actually became customers, that’s a revenue leak worth closing. Request a paid search audit and MMG will map exactly where your call tracking data is helping Smart Bidding and where it’s quietly working against you.

Where to Verify the Technical Details

For the exact mechanics covered above, consult Google’s forwarding number setup guide, the call import specifications, and CallBack CRM’s guide to ad campaign tracking for a systems view of attribution.

Sources