Skip to main content
RetreaverCall tracking

Google Ads counts every Retreaver call. Only the converted ones pay you.

Retreaver marks a call converted only when the buyer's postback arrives with revenue. Google Ads and Meta never see that postback, so a hang-up looks the same to them as a sold insurance or legal call, and your bids chase the noise. We carry the GCLID onto the Retreaver number, send only converted calls back with their revenue, and keep default-number calls out of the count.

Free30 minutesNo obligation

Retreaver · what breaks

What goes wrong with Retreaver and your ads

  1. 01

    Google bids on every dial, not every sale

    If your ad accounts count a call the moment it connects, they can't tell it from the ones Retreaver later marks converted on the buyer's postback. Smart Bidding then buys more short calls nobody paid you for.

  2. 02

    Calls show up with no keyword or click

    When the number pool is full, Retreaver shows your default number instead. The call still routes to a buyer, but the GCLID and keyword that paid for it are gone, so that sale can't be credited to any ad.

  3. 03

    Meta never hears which calls sold

    Retreaver's Facebook guide works through a pixel URL in a converted-call webhook, CSV offline uploads or Zapier. Meta now calls its offline API legacy and recommends the Conversions API, so an old setup may leave Meta learning from calls, not sales.

  4. 04

    Revenue in Retreaver and the ad accounts never agree

    A webhook that sends the publisher payout instead of the buyer's revenue, plus repeat callers inheriting old tags, bends every figure. You can't tell which insurance or legal campaign earns its spend.

Retreaver · the fix

What changes — Retreaver

  • Bidding learns from sold calls

    Google Ads and Meta get the calls a buyer converted inside Retreaver's postback window, with the revenue value attached.

  • Every billable call carries its click

    The pool is sized for click-level tracking and the fallback number is watched, so untracked calls become a measured exception.

  • One revenue figure across tools

    Revenue, not your publisher payout, goes to the ad platforms, and repeat calls stop adding conversions.

Retreaver · architecture

What Retreaver actually lets you hook into

Everything here comes from Retreaver's own guides. Where a guide is dated, we treat it as a check, not a fact.

  1. 1

    Retreaver.js, number pools and parameter mappers

    URL values become tags on the displayed number, and the call inherits them. Retreaver keeps the latest and original visit in separate cookies.

  2. 2

    Buyer postback and conversion timeout

    A buyer posts back the call UUID and revenue; the default timeout is 600 seconds before a call is deemed non-converted.

  3. 3

    Campaign webhooks

    Fire when a call comes in, when it's answered and if it converts, with Facebook and Google Analytics templates in the configurator.

  4. 4

    Google Ads offline conversions

    Retreaver documents CSV or Sheets upload, a Zapier offline conversion step, or the Google Ads API, all keyed on the call's GCLID tag.

  5. 5

    Call data writing and the API

    Disposition tags can be added after the call, and the API returns recent calls for reconciliation. Data writing doesn't trigger conversions itself.

Retreaver · diagnose

Where Retreaver tracking breaks, in diagnostic order

We start at the landing page, because a call that never got its click ID can't be fixed downstream.

  1. 01

    Is the GCLID mapper spelled right?

    Retreaver's Google Analytics guide shows the template as glcid. Copied as written, no click ID ever lands on the call.

  2. 02

    How often does the fallback number show?

    A full pool, or a landing page missing Retreaver.js, drops the click. We count calls on the default-number sub_id in the call log.

  3. 03

    Which visit owns the call?

    Original versus latest visit cookies decide which campaign gets credit on returning callers.

  4. 04

    Is the converted webhook firing once?

    The pixel-fired log on the call flow shows duplicates, misses and webhooks still pointed at retired endpoints.

  5. 05

    Revenue or payout?

    We confirm which value the webhook sends, and whether Repeat Caller Handling is carrying tags onto new calls.

Retreaver · prove

The QA evidence — Retreaver

Run on real calls placed from ad-tagged landing pages, routed to a live buyer, not on the campaign test tools alone.

Source of truth

The Retreaver call log: converted calls by call UUID, with GCLID tag, buyer, revenue and conversion time

  • A test call from a GCLID-tagged URL, with the click ID visible on the call's tags.
  • The buyer postback received inside the timeout and the call marked converted.
  • Exactly one Google Ads offline conversion and one Meta event for that call, sharing its ID.
  • A call answered but not converted, confirmed absent from both platforms.
  • A fallback-number call confirmed excluded from bidding conversions.
  • Converted calls reconciled call by call against both ad accounts over a closed window.
  • The same check repeated 30 days later and after any new publisher landing page goes live.

Retreaver · free audit

What we check in the free audit

  • Is the GCLID mapper spelled right?
  • How often does the fallback number show?
  • Which visit owns the call?
  • Is the converted webhook firing once?
  • Revenue or payout?

Checked against

The Retreaver call log: converted calls by call UUID, with GCLID tag, buyer, revenue and conversion time

Get my free conversion tracking audit

Free30 minutesNo obligation

Retreaver · when not to buy

When you don't need this on Retreaver

Plenty of Retreaver accounts need a settings fix, not a project.

  • If you only buy calls from publishers and run no Google or Meta ads yourself, Retreaver's own reporting already answers the question.
  • If your Google traffic is call-only ads, Retreaver's guide handles those with a static number tagged per keyword, so a pool rebuild adds little.
  • If converted calls in Retreaver already match Google Ads within a few percent, leave it alone.
  • If the only fault is the glcid typo in your tracking template, fix the spelling yourself and retest.

Retreaver · what we deliver

The event map on Retreaver

  • Pool number displayed

    Retreaver.js shows a pool number, and the parameter mappers we set copy the GCLID, fbclid and UTM values from the landing page URL onto it.

  • Call started

    A diagnostic signal only, never a bidding conversion.

  • Buyer answered

    The connected call, kept as a secondary action for reporting.

  • Buyer qualified

    A disposition tag written to the call by call_uuid, for example prequalified or contract signed.

  • Call converted with revenue

    The bidding conversion, fired from Retreaver's converted-call webhook after the buyer's postback, valued at revenue.

  • Excluded on purpose

    Calls on the fallback number, calls that timed out unconverted, and repeat callers whose tags carried over.

Written guarantee

95%+ tracking accuracy

Measured against The Retreaver call log: converted calls by call UUID, with GCLID tag, buyer, revenue and conversion time. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Retreaver questions, answered

Yes, through one of three routes Retreaver documents, all keyed on the call's GCLID tag: a CSV or Sheets upload, a Zapier offline conversion step, or the Google Ads API. We feed a server container from the converted-call webhook instead.

Free · 30 min

Make Retreaver's converted calls drive your ad spend

Free30 minutesNo obligation