This is the implementation guide: by the end, calls from your ads and your landing pages will register as conversions in Google Ads, verified with test calls. Budget 45–60 minutes for a standard single-domain setup, plus a few days of patience while conversion data starts flowing.
If you’re still deciding whether and how deep to track, read the Google Ads call tracking playbook first — it explains the three tiers of tracking. This guide implements them.
Before you start: what you need
- Admin access to Google Ads (conversion actions require it).
- Edit access to your website — directly or via your tag manager.
- A call tracking platform account, if you’re implementing Route B below (recommended). Have its Google Ads integration page open.
- A decision on what counts as a conversion. Minimum viable answer: calls over a duration threshold (60–90 seconds is a common starting point). Better answer, later: qualified calls via call scoring.
- Your real business number handy for forwarding verification.
Route A: Google’s native call reporting
The free tier. It covers calls made from ad units — the call button beside your ad and call-only ads — but not calls from people who click through to your website first. Even if you’re implementing full tracking, do this part; it takes ten minutes.
Step A1 — Create a call conversion action. In Google Ads, open the conversions section (under the goals/measurement area of your account). Create a new conversion action of type Phone calls, and choose “calls from ads using call assets or call-only ads.” Name it clearly — Ad Unit Calls — because you’ll have several call conversions eventually and vague names breed reporting errors.
Step A2 — Set the counting rules. Set a minimum call length (start at 60 seconds; you’re filtering misdials, not judging lead quality yet), counting to “one” (a caller who phones twice is one lead), and an attribution window consistent with your other conversions (window guidance here).
Step A3 — Enable call assets with forwarding. In your campaign or account assets, add (or edit) the call asset, enter your business number, and enable call reporting — this is what makes Google display a forwarding number instead of your raw number, which is the mechanism that lets it count and measure calls. Without call reporting enabled, the asset still shows a number but you get no data.
Step A4 — Verify. From a mobile search where your ad appears (or via Ad Preview), confirm the call button works and rings through to your line. Conversions will begin appearing after real calls exceed your duration threshold — expect a reporting delay of up to a day or so.
That’s Route A complete. Its blind spot is large: most callers don’t call from the ad — they click, land on your site, look around, and dial the number on your page. Route B captures them.
Route B: third-party platform with DNI
This is where campaign- and keyword-level attribution for website calls comes from. Concepts first, then steps; your platform’s docs supply the exact clicks.
Step B1 — Enable auto-tagging in Google Ads. In account settings, confirm auto-tagging is on. This appends the GCLID (Google Click ID) to your landing page URLs — the identifier that lets a later call be matched back to the exact click. Without it, nothing downstream works properly.
Step B2 — Install the DNI script. Your platform provides a JavaScript snippet; install it on every page of the site — not just landing pages — directly in the site template or via your tag manager. Partial installation is the classic self-inflicted wound: visitors who navigate from the landing page to your contact page and call from there fall out of tracking. (New to how DNI works? The non-developer explainer takes ten minutes.)
Step B3 — Configure the number pool and swap targets. In your platform: create a pool for Google Ads traffic (the platform will recommend a size from your traffic volume — undersizing degrades attribution, as explained in how number pools work), set the swap to trigger for paid Google traffic (GCLID/UTM detection), and confirm the swap targets catch your number everywhere it appears: header, footer, contact page, and the tel: links behind mobile call buttons.
Step B4 — Connect the platform to Google Ads. In your platform’s integrations area, authorize the Google Ads connection and enable call conversion sending. This creates (or maps to) a conversion action in Google Ads — name it Website Calls. Decide what the platform sends: all calls above a threshold to start, upgrading to qualified-only later. The three import methods and their trade-offs are covered in How to Import Call Conversions Into Google Ads.
Step B5 — Set conversion action roles. In Google Ads, review which conversion actions are primary (used for bidding) vs. secondary (observation only). A sane starting configuration: your form/purchase conversions and Website Calls as primary; Ad Unit Calls primary if call volume there is meaningful; everything experimental as secondary until proven. Revisit this when you graduate to qualified-call conversions — that’s the moment to make qualified calls primary and demote raw calls, per the Smart Bidding guide.
QA: test calls and verification
Do not skip this section. Most “call tracking doesn’t work” complaints are unverified setups.
- The swap test. Click your own ad (or simulate paid traffic per your platform’s testing instructions), and confirm the number on the landing page differs from your real number. Navigate to two more pages — the swapped number should persist.
- The call test. Dial the displayed number. Confirm it rings your business line, and then confirm the call appears in your platform dashboard within minutes, attributed to Google Ads with your test session’s details (campaign, keyword if available, landing page).
- The conversion test. Stay on the test call past your duration threshold. Over the following days, confirm the conversion appears in Google Ads under the right conversion action. (Import lag is normal — hours to a couple of days depending on method.)
- The mobile test. Repeat the swap-and-call test on a phone, using the tap-to-call button. Mobile
tel:links are the most commonly missed swap target and the majority of your real call volume. - The leak audit. Search your site for any hardcoded appearances of your raw number that didn’t swap — image-based numbers and footer widgets are the usual suspects.
Pre-launch checklist
- [ ] Auto-tagging enabled
- [ ] Route A: call asset with call reporting on;
Ad Unit Callsconversion created with duration threshold - [ ] Route B: DNI sitewide; pool sized to traffic; paid-source swap trigger confirmed
- [ ]
Website Callsconversion connected and mapped - [ ] Primary/secondary conversion roles set deliberately
- [ ] Spam/short-call filtering in place (threshold now, scoring later)
- [ ] All five QA tests passed, including mobile tap-to-call
- [ ] Calendar note in two weeks: review call conversion volume and first transcripts
Frequently asked questions
How long until call conversions appear?
Real user calls typically surface in your platform within minutes, and in Google Ads reporting within hours to a couple of days depending on the import method. Give a new setup two weeks before judging volume — and remember imported conversions land on the click date, so recent days always look artificially light.
Why aren’t my call conversions recording?
Work the QA list in order: auto-tagging off, DNI script missing from some pages, pool misconfigured for paid traffic, the platform-to-Google connection unauthorized, or calls falling under the duration threshold. The swap test isolates website-side problems; the conversion test isolates the import.
Do I need a Google forwarding number?
For Route A (ad-unit calls), yes — enabling call reporting is what activates Google’s forwarding and measurement. For Route B, your platform’s numbers do the forwarding. The routes coexist happily; most complete setups run both.
Setup done? The next hour of value is in the weekly optimization loop — and when you’re ready to make bidding smarter rather than just reporting fuller, Smart Bidding With Call Conversions is the graduation course.