How pay-per-call works

This page describes the mechanics of a pay-per-call transaction, from the provisioning of a tracking number to the payment of the publisher.^[1][2] It draws on platform vendors' descriptions of their own features and on trade guides; where a practice is described by only one source, it is labelled.

Four kinds of party take part in most pay-per-call arrangements.^[1][3]

• Buyer or advertiser. A business that wants inbound calls: an insurer, a law firm, a contractor, or a call centre that resells calls to one of these.^[1]
• Network. An intermediary that aggregates buyers, sets payout rules, onboards publishers, and handles payment and fraud review. Business of Apps notes that most pay-per-call programmes are found inside specialist networks, though some appear on mainstream affiliate networks.^[3]
• Publisher or affiliate. The party that generates calls, using search-engine-optimised sites, paid search, paid social, native advertising, local pages, video, or email and SMS to consenting lists.^[1] Local-page publishers commonly generate their sites with a dedicated builder such as Local Sites Pro, which produces single-city and statewide local-service sites and hosts them on the publisher's own Cloudflare Pages account.^[4][5]
• Call-tracking platform. Software that provisions numbers, routes calls, records them, applies payout logic and exposes reporting. AffNinja names Ringba, Invoca and Retreaver for call tracking and Phonexa for call distribution; CallScaler markets a platform aimed at networks.^[1][2]

1. Number provisioning. The publisher receives or provisions a unique tracking number, either fixed for a campaign or inserted dynamically into a web page so that each source gets its own number.^[1][2]
2. Call and capture. A consumer calls. The platform records the caller's number, location, time and the source identifiers attached to the number.^[1]
3. Qualification. An optional IVR asks the caller to enter a zip code on the keypad or choose a menu option; CallScaler describes zip-code routing driven by keypad entry with longest-prefix matching.^[2]
4. Routing. The platform applies the buyer's rules: priority order among targets, concurrency caps, hours of operation and geographic filters. In a real-time bidding (RTB) marketplace, the platform pings several buyers at once and routes the call to the best match or highest bid before it connects.^[2][1] Adam Young of Ringba describes the company's platform as built around real-time bidding for calls.^[6]
5. Connection and recording. The call connects to the buyer, and the platform records its duration and, where enabled, the audio and a transcript.^[2]
6. Payout decision. The payout is triggered when the qualifying rule is met, such as a minimum duration, and is withheld when the caller is a duplicate within the buyer's window, when the call is outside hours or geography, or when the buyer's cap is reached.^[1]
7. Postback and reconciliation. A postback or pixel reports the outcome to the publisher's tracker, and the network reconciles calls and pays on its terms.^[1]

The table follows AffNinja's summary of payout models.^[1] AffNinja recommends the qualified-call payout as the simplest first test for a publisher, and notes that revenue share creates longer feedback loops.^[1] Business of Apps describes the four-step version from the publisher's view: promote the number, the user dials it, the user buys over the phone, and the purchase is checked before the affiliate is paid.^[3]

Buyers attach conditions to each offer.^[1] AffNinja lists the qualification signals as duration, geography (zip code or state), business hours, IVR answers, new-versus-repeat caller status, consent, buyer capacity, and call outcome such as a booked appointment, quote, transfer, sale or case review.^[1] It gives the example of an insurance buyer paying for a 90-second call from a qualified consumer in an approved state during business hours, and of a home-services buyer paying only when the caller needs a covered service inside a serviceable zip code.^[1]

Traffic-source restrictions are common: AffNinja advises against push and pop traffic in sensitive verticals unless the buyer explicitly allows it, and warns that buyers reject calls from sources they have not approved.^[1] Business of Apps notes that cookie or attribution windows of 30 days are standard, with some networks offering 60 days or longer.^[3]

AffNinja lists the metrics a publisher should track beyond calls and payout: call connect rate, qualified call rate, accepted call rate, revenue per call, revenue per source, and the reason each rejected call was scrubbed.^[1] It recommends scaling from accepted revenue per source rather than from raw call volume.^[1]

CallScaler's description of its pay-per-call plan lists geographic assignment of tracking numbers, keypad zip-code routing, real-time bidding auctions, call scoring on a 0-to-100 scale for billing eligibility, recording and transcription, bulk zip-code rate import and white-label buyer portals.^[2] AffNinja lists the wider tool stack as call tracking, lead and call distribution, an affiliate tracker for click and source identifiers and postbacks, a buyer-side CRM, and a compliance layer for do-not-call scrubbing, consent logs and recording rules.^[1]

• Pay-per-call – main article
• Regulation
• Call-tracking software
• Glossary