Sign In
← Back to Docs
Call Tracking · Platform Guide

Call Tracking & Attribution

Tie every inbound phone call back to the Google Ads click that drove it — and push the calls that book to Google as offline conversions — without paying for a separate call-tracking vendor. PPC TNT includes its own dynamic-number-insertion (DNI) tracking with pluggable call sources, and it still plays nicely with CallRail if you already use it.

Two ways to track calls

PPC TNT supports two call-tracking paths. You can use either or both, and both feed the same Dashboard call and revenue columns.

☎️

Built-in Call Tracking (DNI)

PPC TNT's own tracking — set up under Vendors → Call Tracking.
📞

CallRail

Third-party call tracking you already use.

How built-in attribution works

  1. Insert a number. The DNI snippet on your landing page swaps the displayed phone number for one from your tracking pool and remembers the visitor's gclid.
  2. Capture the call. When someone calls that number, your call source reports the call outcome back to PPC TNT.
  3. Match & evaluate. PPC TNT matches the call to the session that held the number, and the pool's rule decides whether it counts as a conversion.
  4. Upload to Google. Qualifying conversions are uploaded to Google Ads keyed by the gclid, so Smart Bidding optimizes toward calls that actually book.

Call sources

A call source is how a call's outcome is reported. Each tracking pool uses one:

⏱️

Duration

The default — no extra integration.

A call counts as a conversion once it runs past a minimum length you set (e.g. 60 seconds), filtering out hang-ups and wrong numbers.

🎧

Five9

Pull dispositioned calls from your contact center.

PPC TNT automatically pulls dispositioned calls from your Five9 reporting engine, so the disposition your agents set (booked, not-a-lead, etc.) decides which calls convert.

📄

Manual (CSV)

Upload outcomes yourself.

Upload a CSV of call outcomes when you'd rather curate conversions by hand or import from a system PPC TNT doesn't pull from directly.

Google Ads conversion sync & bad-lead retraction

Sending qualified calls back to Google Ads as offline conversions is what makes Smart Bidding chase the right leads. PPC TNT keys each conversion to the gclid captured at call time.

Bad-lead retraction: if a call or lead is later marked bad (spam, wrong service, an archived or lost job), PPC TNT can upload a retraction so Google stops optimizing toward lookalikes of junk leads — a negative-feedback loop most setups never close.

How it fits with the rest of PPC TNT

Call tracking is the bridge between clicks and revenue. Once calls are attributed, the rest of the platform builds on them:

FAQ

Do I still need CallRail?

No. The built-in DNI tracking is a complete alternative that avoids a separate vendor bill. CallRail still works if you prefer it — its calls flow into the Dashboard and matched job values are pushed back to CallRail automatically.

What is a call source?

How a call's outcome is reported: Duration (converts past a minimum length), Five9 (auto-pulled from your contact center), or Manual (CSV upload). You pick one per tracking pool.

How do calls get pushed to Google Ads?

Qualifying calls are uploaded as offline conversions keyed by the Google click ID captured at call time, so Smart Bidding can optimize toward calls that book. Bad leads can be retracted so Google stops chasing lookalikes of them.

Where do I set this up?

Under Vendors → Call Tracking in the app. Create a pool, choose a call source, add your Google Ads customer and conversion-action IDs, and paste the DNI snippet onto your site.

Ready to try it? Sign In and open Vendors → Call Tracking to create your first tracking pool.