Pay Per Call by Adam Young

How to read call analytics like a pro marketer

Simple. Most affiliates look at total calls and think that number tells them something. It doesn't. Not on its own, anyway.

I made this mistake for months when I first started running pay [per call campaigns](/call-tracking-software/how-to-set-up-call-tracking-for-pay/). I'd see 200 calls come in for the day and pat myself on the back. Meanwhile my payout was garbage because half those calls lasted 40 seconds and never converted. Let's fix that. Call analytics only mean something when you know what to look at and why.

Why call duration matters more than call count

A high call count with short average duration usually means low intent traffic or misdials, not a strong campaign. Duration tells you whether someone actually had a conversation. That's the real signal buyers care about.

Industry benchmarks put the cutoff around 60 to 90 seconds. Calls shorter than that are often junk: wrong numbers, people who hung up during the IVR, folks who realized they dialed the wrong business. Calls that run 3 to 8 minutes or longer, especially in insurance and home services, are the ones that usually turn into sales.

This is why networks like Aragon Advertising, Digital Media Solutions, and Century Interactive set minimum call duration requirements, often that same 60 to 90 second window, before a call even counts as billable. If you're sending traffic without checking average handle time against that threshold, you're flying blind. You could be paying for clicks that generate calls that never had a shot at converting.

Here's where it gets interesting, though. Duration alone isn't the full story. A 6 minute call where the caller says "not interested" three times isn't a win just because it's long. You need duration paired with outcome data. That combo is what separates people who guess at optimization from people who actually know what's working.

The metric everyone skips: duration versus conversion correlation

Raw call volume without duration and outcome data will mislead you every time. Cross-reference how long calls last against whether they actually convert. Otherwise you're optimizing for the wrong thing.

I learned this the hard way on an early home services campaign. I was running three traffic sources into the same buyer. Source A generated 150 calls a week. Source B generated 60. On paper, Source A looked like the winner. But when I pulled duration data, Source A's average call length was 45 seconds. Source B's was almost 5 minutes. Once I checked conversion rates, Source B was outperforming Source A by almost 4 to 1 on revenue per call, even with a third of the volume.

That's the trap. Volume feels good. It looks good in a screenshot. But if you're not layering in duration and actual outcomes, you'll keep pouring budget into the wrong source and wonder why your margins are shrinking.

I go into more detail on this in my book, The Pay Per Call Revolution, if you want a deeper walkthrough of building a reporting habit instead of just eyeballing dashboards.

Setting up tracking that actually tells you something

You don't need a fancy setup to get useful data. You need the right pieces in place before traffic starts flowing, not after.

Platforms like Invoca, CallRail, Retreaver, and Ringba are the usual suspects. Pricing runs $0.03 to $0.10 per minute for tracking numbers, plus a monthly platform fee anywhere from $100 for smaller operations up to $1,500 or more for serious volume. Not pocket change. But skipping it costs more in wasted spend than the platform fee ever will.

A few things worth setting up from day one. Dynamic Number Insertion, or DNI, so you know exactly which keyword, ad, or referral source generated each call, is considered standard by pretty much every network in 2024. If a platform you're using doesn't offer it, that's a red flag worth asking about. IVR and call whisper features filter unqualified leads before they ever connect to a buyer, which can cut wasted spend a lot since you're not paying to connect calls that were never going to convert anyway. And call recording needs proper metadata. This isn't optional flavor text, it's a compliance requirement. FTC and TCPA rules require documented consent for recorded calls in most states, so your metadata needs to show consent was captured, not just that a recording exists. Skip this and you're not just risking a bad campaign. You're risking legal exposure.

Reading the dashboard without getting lost in vanity numbers

So you've got calls coming in and data flowing. Now what? Here's how I actually read a dashboard when I'm evaluating a source.

First, I check average call duration against that 60 to 90 second threshold. Anything clustering below that gets flagged immediately.

Second, I look at duration distribution, not just the average. An average of 3 minutes can hide a source where half the calls are 20 seconds and half are 6 minutes. Two very different problems. Two very different fixes.

Third, I check for repeat callers or suspiciously identical durations, which can signal bot traffic or a publisher gaming the system.

Fourth, and this is where speech analytics comes in, I look at flagged keywords. Tools built into platforms like Invoca and Marchex use AI based call scoring to flag words like "cancel" or "not interested" during the call automatically. Huge time saver. Instead of manually listening to hundreds of calls, the flagged ones get pushed to the top. I've caught underperforming traffic sources this way days before I would have noticed from conversion reports alone.

Fifth, cost per qualified call. Not cost per call. Take your total spend on that source and divide by calls that hit both the duration threshold and a real conversion. That number actually tells you if a source is profitable.

None of this takes long once it's part of your routine. The mistake is treating call analytics as a once-a-week check-in instead of a daily habit. Sources shift fast in [pay per call](/pay-per-call-networks/in-house-offers-vs-networks-for-pay-per/). A traffic source solid on Monday can be full of junk by Thursday if a publisher changes targeting or swaps a landing page.

On to the FAQ, since a few questions come up constantly on this topic.

FAQ

How long should a "good" call actually be? Depends on the vertical, but 3 to 8 minutes is a solid benchmark for insurance and home services. Anything under 60 to 90 seconds is usually low intent or a misdial and rarely converts.

Do I need DNI if I'm only running a small campaign? Yes. DNI is standard now, and without it you have no idea which keyword or ad actually generated a call. Even small campaigns need this to optimize spend correctly.

Is call recording legally required? In most U.S. states, yes. If you're recording calls, you need documented consent under FTC and TCPA rules. Check state-specific requirements since some require two-party consent.

What's the fastest way to spot a bad traffic source? Pull duration distribution and flagged keyword data together. A source with clustered short calls or a high rate of "cancel" and "not interested" flags is underperforming, usually before your conversion report even shows it.

Are speech analytics tools worth the extra cost? If you're running any real volume, yes. Manually reviewing hundreds of calls a week isn't realistic, and catching a bad source two or three days earlier can save real budget.

Frequently asked questions

How long should a "good" call actually be?

It depends on the vertical, but 3 to 8 minutes is a solid benchmark for insurance and home services. Anything under 60 to 90 seconds is usually low intent or a misdial and rarely converts.

Do I need DNI if I'm only running a small campaign?

Yes. DNI is standard now, and without it you have no idea which keyword or ad actually generated a call. Even small campaigns need this to optimize spend correctly.

Is call recording legally required?

In most U.S. states, yes. If you're recording calls, you need documented consent under FTC and TCPA rules. Check state-specific requirements since some require two-party consent.

What's the fastest way to spot a bad traffic source?

Pull duration distribution and flagged keyword data together. A source with clustered short calls or a high rate of "cancel" and "not interested" flags is underperforming, usually before your conversion report even shows it.

Are speech analytics tools worth the extra cost?

If you're running any real volume, yes. Manually reviewing hundreds of calls a week isn't realistic, and catching a bad source two or three days earlier can save real budget.