Retreaver

Name: Retreaver
Brand: Retreaver

Tag-based call routing and tracking for marketers who sell calls

Retreaver is a call tracking and intelligent routing platform built around tags: every caller, campaign, and buyer carries key-value attributes, and routing decisions are made by matching them. It serves pay-per-call marketers, lead generation networks, and agencies that need calls attributed to their source and routed to the right buyer, with recording, reporting, and payout accounting included.

Visit website

Overview

Retreaver's design choice is its tagging model. Rather than configuring routing as a tree of rules per campaign, every entity carries tags: the caller's state, the source publisher, the product enquired about, the buyer's accepted criteria. Routing then becomes a matching problem, which scales more gracefully as the number of buyers and campaigns grows and makes complex logic legible rather than nested.

Everything else follows the pay-per-call template: dynamic number insertion for attributing calls to sources, real-time routing with capacity and schedule constraints, recording and transcription, conversion criteria based on duration or outcome, and per-publisher and per-buyer reporting that reconciles what to pay and what to bill. Data flows back to advertising platforms so bidding can optimize toward calls that qualified rather than calls that connected.

It is generally regarded as the more approachable of the serious pay-per-call platforms, with a lighter interface and simpler configuration than the largest competitor, at the cost of some marketplace-scale bidding depth. Pricing is usage-based, per connected minute plus number fees, which suits a business whose revenue is also per call. Businesses simply wanting to know which campaign made the phone ring will still find general call tracking tools cheaper and simpler.

Best for

Pay-per-call marketers, lead generation networks, and agencies routing calls to multiple buyers who want capable routing without the configuration weight of the largest marketplace platforms.

Not the right fit for

Local businesses wanting simple call attribution, where general call tracking tools cost less.
Organizations needing enterprise conversation intelligence with deep AI outcome detection.
Buyers wanting flat subscription pricing rather than per-minute telephony billing.
Teams needing a full contact center with agent desktops and outbound dialing.
Businesses with no call-based revenue, where the routing capability is irrelevant.

How it works

1
Tracking numbers are provisioned and assigned dynamically to visitors so each call is attributed to the campaign, keyword, publisher, and page that produced it, with URL parameters captured into the call record.
2
Tags are applied to the caller from the source, from data passed on the page, from IVR responses, or from lookups, describing who is calling and what they want in key-value form.
3
Buyers and destinations declare which tag combinations they accept, along with capacity, schedule, and concurrency limits. Routing matches an incoming call's tags to eligible buyers and connects it, falling through to the next match if the first declines or fails to answer.
4
Calls are recorded, conversion criteria are evaluated, and reporting reconciles revenue and payouts by publisher and buyer, with conversion data pushed back to advertising platforms and CRM systems.

Feature breakdown

20 features in 4 modules

Tag-based routing

The distinguishing model, and why complex logic stays manageable.

Key-value tagging: Callers, campaigns, publishers, and buyers all carry attributes, and routing is a matching problem rather than a rule tree.
Real-time tag population: Tags set from URL parameters, page data, API lookups, and IVR responses before the routing decision is made.
Buyer criteria matching: Each buyer declares acceptable tag combinations, so eligibility is explicit and auditable.
Capacity and schedule controls: Concurrency caps, business hours, and daily limits per buyer so calls are not sent where they cannot be handled.
Cascading failover: Unaccepted or unanswered calls flow to the next eligible destination rather than being lost.

Tracking and attribution

Connecting calls to the marketing that generated them.

Dynamic number insertion: Session-level numbers so calls attribute to source, campaign, keyword, and landing page.
Number pool management: Provisioning and rotation with reuse rules that preserve attribution integrity under concurrency.
Publisher tracking: Per-affiliate attribution and reporting, essential where traffic is bought from multiple sources.
Conversion criteria: Billable calls defined by duration, IVR outcome, or buyer confirmation rather than connection alone.
Ad platform feedback: Qualified call conversions returned to Google and Meta so bidding targets calls that converted.

Analytics and quality

Understanding what happened after the connection.

Call recording: Recording with retrieval and retention settings, subject to jurisdictional consent requirements.
Transcription: Speech to text for quality review and searching conversations for outcome indicators.
Real-time reporting: Live volume, conversion, and revenue reporting by publisher, buyer, campaign, and tag.
IVR menus: Pre-routing qualification so unqualified callers do not consume buyer capacity.
Custom reporting dimensions: Reports sliced by any tag, which is where the tagging model pays off analytically as well as operationally.

Operations and integration

Running the business around the calls.

Payout and billing reconciliation: Revenue and cost per call calculated per publisher and buyer, replacing spreadsheet accounting.
API and webhooks: Programmatic control over numbers, tags, routing, and reporting for integration with internal systems.
Ping and post support: Buyer endpoints queried with caller attributes before connection, matching lead-industry conventions.
CRM and platform integrations: Connections to CRM, analytics, and affiliate tracking platforms so call data joins the rest of the stack.
Multi-account structures: Agency and network configurations managing many campaigns and clients under one platform.

Use cases

4 documented

Lead generation network with dozens of buyers

Each buyer accepts different states, products, and hours, and rule-based routing has become unmanageable.

Tag matching expresses every buyer's criteria declaratively, and adding a buyer becomes a configuration entry rather than a routing redesign.

Agency running call campaigns for clients

Clients want proof of which channels produced qualified calls, not just call counts.

Tag-based reporting attributes qualified calls by source and campaign, and recordings substantiate the quality claim.

Pay-per-call affiliate managing publisher payouts

Reconciling what each traffic source earned against what each buyer paid consumes days each month.

Automatic reconciliation by publisher and buyer produces payout reporting without manual spreadsheets.

Home services marketer routing by geography

Contractors cover overlapping regions with different capacity, and misrouted calls generate complaints.

Geographic tags plus concurrency limits route correctly, and failover ensures a declined call reaches the next provider.

Pricing

from Usage-based, commonly a small monthly minimum plus per-minute and per-number charges

Usage-based: per connected minute plus monthly per-number fees, with additional metering for recording, transcription, and some advanced features. No seat licensing; volume discounts at scale.

Plan	Price	Includes
Standard usage	Per minute and per number monthly usage	Tag-based routing and dynamic number insertion Recording and reporting No per-seat charges
Volume	Reduced per-minute rates monthly usage	Discounted minutes at higher volumes Larger number pools Advanced routing and integration features
Enterprise	Quoted annual	Network-scale configurations Dedicated support Custom integrations and reporting

Billing notes

Per-minute billing aligns cost with call length, which suits pay-per-call economics but is harder to forecast than a subscription.
Number pools carry a fixed monthly cost regardless of volume, and under-provisioning degrades attribution accuracy.
Recording and transcription are metered separately from connected minutes.
No seat fees means agencies and networks can grant access broadly without cost implications.
Rates as of August 2026 are quoted per account and vary by destination and volume.

Value assessment: For a call-based business the platform is a cost of goods rather than software overhead, and the comparison is against margin lost to misrouted or under-monetized calls. Retreaver's specific value is capable routing without the configuration burden of the largest platforms, which matters most for operations with substantial buyer complexity but limited engineering support. For non-call businesses the model is simply the wrong shape.

Strengths & limitations

Strengths

Tag-based routing scales more gracefully than nested rules as buyer counts grow.
Reporting can be sliced by any tag, making analysis as flexible as the routing.
Generally more approachable than the largest pay-per-call platforms.
Publisher and buyer reconciliation built in rather than assembled in spreadsheets.
Usage-based pricing with no seat charges suits agencies and networks.
Strong API for integrating call routing into existing lead systems.

Limitations

Overkill and mispriced for businesses that only need basic call attribution.
Less marketplace bidding depth than the largest competitor at very high scale.
Per-minute billing is harder to budget than a flat subscription.
Conversation analysis is lighter than enterprise conversation intelligence platforms.
Call recording consent obligations vary by jurisdiction and remain the operator's responsibility.
Requires understanding of the pay-per-call model to configure sensibly.

Head-to-head comparisons

4 alternatives

Retreaver vs Ringba

from Usage-based with no seat fees; commonly a low monthly minimum plus per-minute and per-number charges

The direct comparison in pay-per-call. Ringba offers deeper real-time bidding and marketplace functionality for operations monetizing calls at scale; Retreaver offers a cleaner tagging model and a gentler configuration experience. Networks with complex buyer auctions tend toward Ringba, while operations valuing maintainability and speed of setup often prefer Retreaver.

Full Retreaver vs Ringba comparison

Retreaver vs CallRail

from $50 per month (Lead Tracking); conversation intelligence starts at $150 per month (Lead Conversion)

Different problems. CallRail attributes calls for businesses and agencies with a simple subscription and an approachable interface. Retreaver routes and monetizes calls across multiple buyers with capacity rules and payout reconciliation. If nobody is buying your calls, you want CallRail.

Full Retreaver vs CallRail comparison

Retreaver vs Invoca

from Quoted; enterprise contracts typically starting in the low thousands of dollars per month

Invoca is the enterprise conversation intelligence platform, analyzing what was said on calls for large brands and feeding outcomes into marketing and contact center systems. Retreaver is routing and monetization infrastructure for marketers who sell calls. The buyer profiles barely overlap: one receives calls as a brand, the other brokers them.

Full Retreaver vs Invoca comparison

Retreaver vs Phonexa

from Quoted; typically a meaningful monthly commitment reflecting the full-suite license

Both support ping and post distribution to multiple buyers, but the scope differs sharply. Retreaver is call routing alone, priced per connected minute plus number fees, and a working configuration is usually live within one to three weeks. Phonexa is a quoted suite license that adds form lead distribution, publisher and buyer management, email and SMS follow-up, suppression lists, and payout accounting, at the cost of a longer implementation and paying for modules you may not use. Choose Retreaver if calls are the whole business and you value fast, maintainable setup; choose Phonexa if reconciling calls and form leads across publishers is the actual pain.

Full Retreaver vs Phonexa comparison

Implementation & onboarding

Setup time: Basic tracking within a day. A complete configuration with tags, buyers, routing, and payout reporting typically takes one to three weeks depending on buyer complexity.
Learning curve: Moderate. The tagging model is simpler than nested rules once understood, but requires deciding on a tag taxonomy early, since inconsistent tags undermine both routing and reporting.
Onboarding: Support-assisted setup with documentation aimed at practitioners already familiar with pay-per-call concepts.
Migration notes: Number porting takes time and should be scheduled first. Design the tag taxonomy before migrating campaigns, because retagging historical calls is impractical and inconsistent taxonomies make reporting unreliable from the start.

Platform, API & security

Platforms: Web applicationTelephony infrastructureREST API and webhooks
API: Full API for numbers, tags, routing, buyers, and reporting, with webhooks and ping-and-post endpoints for real-time buyer integration.
Compliance: TCPA considerationsGDPRCCPAJurisdictional call recording consent
Data residency: North American infrastructure with international number support.
SSO: Available on enterprise arrangements.
Security notes: Recordings are sensitive personal data with consent obligations varying by jurisdiction; announcement and consent configuration is the operator's responsibility rather than a platform default.

Support & resources

Channels: Email and ticket supportAccount management on larger accountsDocumentation
Documentation: Practical documentation covering tagging, routing, and integration, written for pay-per-call practitioners.
Community: Presence within the affiliate and performance marketing community, with an ecosystem of consultants configuring campaigns on the platform.

Company

Founded: 2013
Headquarters: Toronto, Canada
Ownership: Private, independent
Employees: Small team (not disclosed)
Funding: Bootstrapped with limited disclosed outside investment.

Timeline

2013Founded in Toronto with a tag-based approach to call routing and attribution.
2017Establishes itself among pay-per-call networks as an approachable alternative to heavier platforms.
2020Expands API and integration coverage for lead systems and affiliate tracking platforms.
2023Adds transcription and richer conversion criteria for qualified-call reporting.
2026Continues as a leading mid-scale pay-per-call routing and tracking platform.

Integrations

Google Ads
Meta Ads
HubSpot
Salesforce
Zapier
Everflow
Twilio

Frequently asked questions

10 questions

What is Retreaver?

Retreaver is a call tracking and intelligent routing platform for pay-per-call marketing. It attributes inbound calls to their source, applies key-value tags describing the caller, routes calls to buyers whose criteria match those tags, records conversations, and reconciles payouts between publishers and buyers.

What does tag-based routing mean?

Instead of writing nested rules per campaign, every caller, campaign, publisher, and buyer carries attributes as key-value tags. Routing matches a call's tags against each buyer's accepted combinations. As buyer counts grow, matching stays readable where rule trees become unmaintainable, and the same tags then power flexible reporting.

How does Retreaver pricing work?

Usage-based: per connected minute plus monthly fees per tracking number, with recording and transcription metered separately. There are no seat charges, and volume discounts apply at scale. Rates are quoted per account and vary by destination.

Retreaver vs Ringba: which is better?

Ringba goes deeper on real-time bidding and marketplace functionality, which matters most for large call auctions. Retreaver is usually described as simpler to configure and maintain, with a cleaner conceptual model. Operations with complex buyer auctions lean Ringba; those prioritizing maintainability often prefer Retreaver.

Can I use Retreaver for basic call tracking?

You can, but it is not the economical choice. If the requirement is knowing which campaigns produce phone calls for a single business, general call tracking tools offer simpler interfaces and flat pricing. Retreaver earns its keep when calls are routed to multiple buyers with differing criteria.

Does Retreaver support ping and post?

Yes. Buyer endpoints can be queried with the caller's attributes before connection, following the conventions the lead buying industry already uses, so existing buyer integrations translate without redesigning their side of the process.

How does it handle call recording consent?

It provides announcement and recording controls, but the legal obligation is jurisdictional and yours. Some US states require all-party consent, and European rules generally require clear notice and a lawful basis, so configuration must reflect where callers actually are.

Can it send qualified calls back to Google Ads as conversions?

Yes, and this is one of the more valuable configurations. Defining conversions by call duration or outcome rather than by connection means Google optimizes bidding toward keywords producing real conversations rather than immediate hang-ups.

How many tracking numbers will I need?

Enough for concurrent visitor sessions, not total visits. Under-provisioning causes numbers to recycle too quickly and misattributes calls, which is the most common reason call tracking data looks inconsistent with ad platform reporting.

Does Retreaver handle publisher payouts?

It reconciles revenue and cost per call by publisher and buyer, producing the reporting payouts are calculated from. Actual payment is handled outside the platform, but the accounting that usually consumes days each month is automated.

Editorial verdict

Retreaver's tagging model is a genuinely good idea. Expressing routing as attribute matching rather than nested rules keeps complex buyer logic legible as a network grows, and the same tags make reporting flexible without custom work. That, plus a lighter configuration experience than the largest pay-per-call platform, makes it the sensible middle choice for operations with real buyer complexity and limited engineering support. It gives up some marketplace bidding depth at the top end and offers less conversation analysis than enterprise platforms. And as with everything in this corner of the category, it is the wrong purchase for a business that simply wants to know which advertisement made the phone ring.

Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.