4 DNI Metrics That Prove Ads Drove Calls for Local Marketers

Local Lead Growth Team

Digital marketing for local service businesses

Yes, when you implement dynamic number insertion with ad-level identifiers and CRM import, you can prove which ads drove phone leads. The mechanism ties a specific call back to a specific click, so a phone lead stops being a mystery and becomes a line item in your ad reporting. The catch: it only works if your tagging is correct, your conversion rules match how your business actually qualifies a lead, and your call recording setup follows the law.


TL;DR:

  • Correct implementation of DNI requires precise session tagging, proper placement of scripts, and strict adherence to legal call recording rules.
  • Accurate call attribution depends on correct session storage of click identifiers, forwarding number management, and thorough end-to-end testing.
  • Reports linking calls to ad clicks and CRM data are essential to prove revenue-generating phone leads; skip uploading offline conversions for full ROI insight.
  • Common issues include missing URL parameters, reused forwarding numbers, and misaligned tracking thresholds, which can cause attribution errors or data gaps.
  • Regular manual checks and compliance with regional call recording laws are vital to maintain data integrity and legal legality.

Localleadgrowth
Make Every Call Count
Local Lead Growth helps local businesses generate leads, increase reviews, and turn more customer conversations into growth.

Table of Contents

How dynamic number insertion actually works

Dynamic number insertion, or DNI, swaps the phone number shown on your website with a different number depending on where the visitor came from. Instead of one static number for every visitor, the page pulls a number from a pool of forwarding numbers and assigns one to that specific session. When someone clicks a Google ad, lands on your site, and sees a phone number, that number is not your real business line. It is a forwarding number tied to that visit.

Illustration of dynamic number assignment

The reason this works for attribution is that ad click identifiers get captured and stored before the number swap happens. Google Ads supports dynamically generated forwarding numbers through a phone snippet and a Google tag installed on your site. The tag reads the click identifier from the URL, usually a GCLID, and holds onto it in the browser session so it can be matched later.

A few pieces have to work together for this to hold up:

  • The Google tag or Google Tag Manager container fires on every page that shows a phone number.
  • The phone snippet swaps the visible number and passes session data to the telephony provider.
  • A stored click identifier (GCLID, UTM parameters, or ValueTrack tags) rides along with the session in a cookie or localStorage.
  • The telephony provider logs the call and attempts to match it back to the session identifier the moment the forwarding number rings.

That final matching step is crucial, as it links calls to specific ad clicks rather than just campaigns, allowing precise attribution rather than general campaign-level data.

The reports that prove your ads produced phone leads

Once DNI is capturing sessions correctly, the proof lives in a handful of reports. Pull these in order:

  1. Phone-through rate (PTR), phone calls, and call conversions, filtered by a call-duration threshold you set yourself (a short duration threshold is commonly used) so a hang-up does not count the same as a real inquiry.
  2. The call details report, which links each logged call to its GCLID or session identifier so you can trace a call to the exact ad and keyword that produced it.
  3. CRM-imported offline conversions, showing revenue per call once your sales team closes the deal, uploaded back into Google Ads so the platform sees the dollar value, not just the click.

Google’s call reporting separates phone calls, which are reported on the date they occurred, from call conversions, which are reported on the date of the original ad click. That distinction trips up a lot of marketing managers building monthly reports. If a click happens on the 28th and the call comes in on the 2nd of the next month, the conversion gets credited to the earlier month while the raw call count shows up in the later one. Present both dates side by side in your dashboard so nobody accuses you of moving numbers around.

A stat worth building your report around: importing offline call conversions closes the loop between a phone call and the revenue it produced, because Google Ads lets you upload CRM-confirmed outcomes via CSV or scheduled feed and attribute that value back to the original click. Without this step, you can prove a call happened. With it, you can prove what the call was worth.

A one-page report for a CFO or business owner needs four things: total call conversions for the period, phone-through rate against total ad clicks, revenue per call from CRM import, and a short note on the duration threshold used. Skip the dashboard screenshots. Stakeholders want the number, the dollar value, and confirmation the counting method was consistent with last month.

Implementation checklist: setting up DNI so it actually holds up

Getting DNI running correctly is mostly about sequencing. Skip a step and the whole chain breaks quietly, meaning you will not find out until someone asks why call conversions dropped to zero.

  1. Turn on auto-tagging in your Google Ads account so GCLID gets appended to every ad click automatically, then confirm your site captures it in session storage on landing.
  2. Install the Google tag site-wide, either directly or through Google Tag Manager, so every page carries the tracking logic instead of just a handful of landing pages.
  3. Add the phone snippet to every page displaying a phone number, and set an appropriate timeout and cache duration so returning visitors within the same session still see their assigned forwarding number.
  4. Reserve your forwarding numbers for ad sessions only. Never print a Google forwarding number on a business card, invoice, or directory listing. Google forwarding numbers can be reassigned to a different advertiser or session, so publishing one permanently guarantees bad data down the line.
  5. Set your conversion action’s duration threshold a short duration threshold is often used as a starting point and mark it as a primary conversion if you want Smart Bidding to optimize toward phone leads specifically.
  6. Test end to end before declaring it live. Search for your own ad, click it, confirm the displayed number changed to a forwarding number, place a test call, then check that the call appears in both your telephony call logs and your Google Ads or CRM report with the matching session data attached.

Pro Tip: Run the end-to-end test from a phone on a different network than office Wi-Fi, not office Wi-Fi. A lot of DNI failures only show up on mobile because the session storage behaves differently across browsers.

Hand the testing checklist to whoever is nontechnical on your team too. If the office manager can run the click-to-call test and confirm the number swap without help, you know the setup is stable enough to survive a browser update or a site redesign without silently breaking.

Common pitfalls, misreads, and a compliance note

The most common failure is a missing or broken GCLID. If your tag isn’t firing before the number swap, or if a redirect strips the URL parameter, the call logs in without any ad-level link. You can catch this by spot-checking call records weekly for sessions with no click identifier attached. A sudden spike in “unattributed” calls almost always means a tagging break, not a drop in ad performance.

A second pitfall is reusing or publishing forwarding numbers outside their intended session. This corrupts the mapping and can misattribute one advertiser’s calls to another’s.

Other issues to watch for:

  • Manual dials and offline touchpoints (someone who saw your ad last week and later Googles your business name directly) will never show a click identifier, so reconcile these gaps against CRM entries rather than assuming DNI missed something.
  • Attribution timing confuses stakeholders when call-date and click-date reports disagree; present both explicitly instead of picking one.
  • Duration threshold mismatches between what marketing counts as a conversion and what sales considers a real lead create reporting disputes that have nothing to do with the technology.

One statement worth building your compliance checklist around: state-level call-recording rules vary, and a meaningful share of states require all-party consent before a call can be recorded, which is why a pre-call disclosure and logged consent are standard practice, not optional. If your callers span multiple states, default to the strictest applicable rule rather than guessing case by case, and configure your telephony system so recording only begins after the disclosure has played.

How Local Lead Growth implements DNI and proves ad-driven calls

Our workflow follows the same chain outlined above, applied consistently across client accounts: ads fire, the Google tag captures the click identifier, DNI assigns a forwarding number, the telephony platform logs the call, and that call data gets imported into both the CRM and Google Ads as an offline conversion.

Before we call any setup “live,” it goes through a fixed testing sequence:

  • Confirm the number swap triggers correctly on desktop and mobile.
  • Verify the call log captures session identifiers on a live test call.
  • Check that the CRM correctly maps the call to the matching ad campaign.
  • Confirm the offline conversion upload reflects in Google Ads reporting within the expected window.

That verification step is what separates a DNI setup that looks correct from one that actually holds up when a client asks which ad paid for a specific job.

Why DNI belongs in every local marketing measurement toolkit

The real value of DNI isn’t the technology, it’s what it prevents: a good campaign getting cut because nobody could prove the phone leads it generated. Phone calls have always been the blind spot in digital ad reporting, and misattributed revenue has killed more good campaigns than bad targeting ever has.

Once DNI is running cleanly, the next step isn’t more tracking, it’s better use of what you already have: scoring call quality, cleaning up CRM data entry habits, and feeding real conversion values back into bidding so the platform optimizes toward calls that actually turned into paying customers.

— Rich

How Local Lead Growth can set this up for you

If you have read this far and realized your own call tracking has gaps, you are not alone. Most small businesses running ads never get past a static tracking number, which means every phone lead looks the same on paper whether it came from a $2 click or a $40 one.

Localleadgrowth

Local Lead Growth handles the full chain: Call Tracking & Reporting built on the DNI setup described above, Google Ads management with conversion actions configured correctly from day one, and reporting dashboards that show phone-through rate and revenue per call without you having to build a spreadsheet yourself. A few things worth knowing about how we work:

  • Clients work directly with senior team members on setup and troubleshooting, rather than through an intermediary account manager.
  • Engagements typically start with a review of your current tracking, ad accounts, and CRM to find where the attribution gaps already exist.
  • Reporting is built to answer the exact question this article covers: which ad produced which call, and what that call was worth.

If your phone leads are still a mystery, view our full service list or reach out for a setup audit.

FAQ

What are dynamic ads?

Dynamic ads are ad formats that automatically adjust their content, such as product images or text, based on data feeds or a viewer’s browsing behavior. This differs from dynamic number insertion, which swaps the displayed phone number rather than the ad content itself.

Are dynamic search ads still available?

Dynamic Search Ads remain a distinct Google Ads campaign format that generates headlines and lands visitors on pages based on your site’s content rather than manually chosen keywords. They are separate from dynamic number insertion, which is a call-tracking technique applied to phone numbers on your website.

What does the advertiser provide in dynamic search ads?

In Dynamic Search Ads, the advertiser provides the website itself along with a description line for the ad, while Google generates the headline and landing page match from the site’s content. This is unrelated to call tracking setups like DNI, which instead require the advertiser to install a phone snippet and Google tag.

How do I know if my DNI setup is actually working?

Run a live test: search for your ad, click it, confirm the phone number on your site changes to a forwarding number, then place a call and check that it appears in both your call logs and Google Ads or CRM report. If the call shows up without a matching session identifier, your tagging has a gap that needs fixing before you trust the data.

Does dynamic number insertion slow down my website?

A correctly installed phone snippet loads asynchronously and swaps the number after the page renders, so it typically has minimal effect on page speed. Poorly configured scripts or excessive caching settings are the more common cause of any noticeable delay.

Share this article 𝕏 f in
Local Lead Growth
More Leads.More Reviews.More Profits.

Lead generation and AI Lead Capture for local businesses across New England. Work directly with the owners.

Google PartnerMeta Business Partner

Services

Company

Get in touch

  • (508) 715-3004
  • info@localleadgrowth.com
  • 11 Robert F Toner Blvd #5-328
    North Attleborough, MA 02763
  • Monday – Saturday, 8am – 6pm
  • Serving all of New England: Massachusetts, Rhode Island, New Hampshire, Connecticut, Maine & Vermont
© 2026 Local Lead Growth LLC. All rights reserved.
Scroll to Top