Retreaver calls,traced back to the ad

ClickFlare ties every converted Retreaver call back to the ad click and lander that brought the caller, with the call payout. You see cost per converted call and ROI per campaign, and can report connected or long calls as their own conversions.

Start for free

Read the setup guide

Retreaver

Call tracking and routing platform

Retreaver integration at a glance

How it connects

Retreaver webhook to ClickFlare's server-to-server postback

What syncs

Converted calls, payout, call IDs and call tags

How fresh the data is

At call end, when your conversion criteria are met

What you can optimize

Ads, landers and sources by converted calls and payout

Works with

Retreaver number pools on your lander

Good to know

Calls to the default number carry no click ID and can't match.

Pay-per-call

Calls per ad

Payout per call

See which ads bring paying Retreaver calls

Calls tied to the click

Each visitor sees a tracked number, and every call to that number carries the ad click with it.

Each converted call counted

Each converted call counts as its own conversion with its own payout, so you see call revenue per ad, call by call.

Every call outcome as a column

Report connected, converted and long calls as separate conversions, so you see more than converted calls.

How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversionautomated actionyour dashboardsclosed revenue

Your ad

Visitor clicks

Ad on Retreaver

ClickFlare

Click recorded

Every click gets its own ID

Your offer

Conversion

Lead, sale or custom event

ClickFlare

Sent back to Retreaver

Through the Conversion API or postback

Cost API

Spend pulled in

Retreaver cost matched to each campaign

Your ad

Retreaver click

Placement, device and country come along

ClickFlare

Click recorded

Zone, site and device data stored

Offer or lander

Visitor converts

On your page or the offer

ClickFlare

Conversion logged

With payout and event type

Postback

Reported to Retreaver

So its optimization sees the result

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

Every click gets its own ID

Your article

Keyword block

Click ID passed to the feed

Results page

Paid click

Conversion fired to ClickFlare

Retreaver API

Revenue matched

Pulled on a schedule and reconciled

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

The click follows the visitor to the offer

Retreaver

Offer or call

The network tracks the action

Retreaver

Conversion

Lead, sale, call or rebill

Postback

Payout in ClickFlare

Matched to the original click

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

Every click gets its own ID

Retreaver

Store or funnel

Click ID kept through checkout

Events

View, cart, checkout

Each step tracked

ClickFlare

Purchase recorded

Order value matched to the ad

Your ad

Visitor clicks

Form, call or landing page

ClickFlare

Click recorded

Every click gets its own ID

Retreaver

Lead or call stored

The ad stays linked to the lead

Retreaver

Qualified or closed

Workflow or call rule fires

ClickFlare

Revenue recorded

Tied to the ad that drove it

ClickFlare

Event happens

Click, conversion or custom event

Webhook or API

Data goes out

Or comes back in

Retreaver

Your workflow

Rules, apps or an AI assistant

Retreaver

Action

Alert, update, pause or scale

ClickFlare

Back in reports

Changes show in your data

ClickFlare

Report data

Campaigns, sources, offers

ClickFlare API

Your numbers go out

Secured with your API key

Your setup

Scheduled refresh

A sheet, script or connector

Retreaver

Data lands

Tables refreshed on schedule

Retreaver

Dashboards

Blended with your other data

Pay-per-call

From ad click to converted call

Your lander shows a Retreaver number tagged with the ClickFlare click ID. When a call meets your conversion criteria, Retreaver reports it to ClickFlare with the payout, against the ad click that brought the caller.

Click ID tagged on the number each visitor sees
Reported when the call ends and converts
Payout or buyer revenue, your choice

Today, one campaign

example

Spend pulled from Retreaver

cost

$412.30

Conversions recorded

today

Sent back to Retreaver

per event

38/38

Profit

campaign

$227.70

Example numbers. Cost and conversions sit in the same report row.

ROI per placement

example

Placement A · mobile

cost

$38.20

Placement A

revenue

$71.40

Placement A

ROI

+87%

Placement B · desktop

ROI

−42%

Example numbers. Keep the placements that pay and cut the ones that lose money.

Revenue for one click

example

Paid click

day 0

$0.00

First revenue pull

+1h

$0.41

Scheduled updates

next days

$0.58

Final pull

last sync

$0.62

Example amounts. Sync timing for Retreaver is in the facts above.

Events for one click

example

Lead

day 0

$0.00

Sale

day 0

+$40.00

Upsell

day 1

+$15.00

Refund

day 9

−$15.00

Example events. Each one arrives by postback and is matched to the click.

One visitor's path

example

Product view

step 1

—

Add to cart

step 2

—

Checkout

step 3

—

Purchase

step 4

$68.00

Example order. Each event is tied to the ad that brought the visitor.

One lead, followed to revenue

example

Lead created

day 0

$0.00

Qualified

day 2

+$25.00

Deal closed

day 14

+$480.00

Renewal

day 45

+$120.00

Example values. Each stage can be its own event type in ClickFlare.

A scheduled report refresh

example

Campaigns

in the report

1,240 rows

Cost, revenue, profit

per campaign

included

Refresh

your schedule

done

Dashboards fed

Retreaver

Example numbers. You choose the breakdowns, date range and schedule.

One event, end to end

example

Conversion recorded

event

sent

Event delivered

Retreaver

received

Workflow ran

Retreaver

done

Team notified

your apps

done

Example run. What happens after the event is up to your workflow.

End-of-call triggers

2.3B

Events tracked

Setup

Connected in three steps

You need a ClickFlare account with your own tracking domain, and a Retreaver campaign with buyers, conversion criteria, a number pool and Retreaver.js on your lander.

Add your lander to a campaign Create a conversion for converted calls and add the page that shows your Retreaver number as the offer in a redirect campaign.
Tag calls with the click ID In your Retreaver campaign, map the ClickFlare click ID from the lander link to a tag on the number.
Report converted calls Add a Retreaver webhook on conversion that reports to ClickFlare. Converted calls then land on the ad with their payout.

app.clickflare.com/integrations

Retreaver

Pay-per-call

Connected

Retreaver account connected

Signed in from ClickFlare

Cost syncing

Spend matched to campaigns

Conversions sent back

Your chosen events

Retreaver template selected

Macros pre-filled

Tracking URL in Retreaver

Click ID captured

Conversions reported

Payout included where supported

Retreaver connected

Credentials saved in ClickFlare

Conversion event set

Click ID passed to the feed

Revenue syncing

On the feed's schedule

Retreaver added

Offer URL carries the click ID

Postback set in Retreaver

Payout and event included

Conversions arriving

Matched to the click

Retreaver connected

Click ID kept to checkout

Events mapped

View, cart, checkout, purchase

Purchases tracked

Order value in reports

Click ID stored in Retreaver

Hidden field or call data

Workflow or rule set

Fires on the stage you choose

Conversions arriving

With payout and event type

API key created

Settings, then Security

Report pull scheduled

Dimensions and date range set

Retreaver dashboards live

Refreshed on schedule

Connection set up

Webhook, API key or MCP

Events chosen

Only what the workflow needs

Workflow running

Tested end to end

Ready to track

Own the Retreaver campaign and sell calls to buyers? Report the buyer revenue instead of the payout, since that's your income.

Retreaver setup guide

Open the guide

In your reports

What you see once it's connected

Converted calls per campaign
Call payout by traffic source
Calls per ad and lander
Connected vs. converted calls
Cost per converted call
Call details from tags

Use cases

How media buyers run it

Ad → lander with a Retreaver number

Ad → lander → call

Each converted call ties back to the ad that brought it.

Publisher or campaign owner

Sending calls into someone else's campaign? Report the payout. Selling calls to buyers from your own campaign? Report the revenue.

Connected, converted, long calls

Report connected, converted and long calls, each as its own conversion type, to see every call outcome per ad.

Frequently asked questions

Retreaver integration FAQ

Does ClickFlare integrate with Retreaver?

Yes, through ClickFlare's server-to-server postback, fired by a Retreaver webhook. There's no native integration and nothing to install on the ClickFlare side.

How does Retreaver know which ad a call came from?

Retreaver tags the number on your lander with the ClickFlare click ID, and every call to that number inherits it.

Can I report calls that don't convert?

Yes. Add Retreaver webhooks for connected calls, non-converted calls or calls past a set length, each as its own conversion.

How big should my number pool be?

Each visitor gets a unique number, so the pool must cover your visitors at the same time within the lease time. When it runs out, visitors see the default number.

Can I stop repeat callers counting twice?

Yes. Use Retreaver's de-dupe setting. Without it, each converted call counts as its own conversion.

Can I use direct tracking instead of a redirect?

Only with custom code. Without a redirect, the click ID isn't in the lander link, so a developer must add it to the Retreaver number on the page.

No items found.

Related integrations

More templates that plug into the same ClickFlare account.

CallRail

Call tracking and analytics

CRM and marketing automation

CRM

gohighlevel

HubSpot

CRM and marketing platform

CRM

hubspot

Konnektive

CRM for offers, now Checkout Champ

Sales CRM

CRM platform

Browse all integrations ->

Setup guides

Retreaver setup guide

Custom webhook integration

{"@context": "https://schema.org", "@graph": [{"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Retreaver?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, through ClickFlare's server-to-server postback, fired by a Retreaver webhook. There's no native integration and nothing to install on the ClickFlare side."}}, {"@type": "Question", "name": "How does Retreaver know which ad a call came from?", "acceptedAnswer": {"@type": "Answer", "text": "Retreaver tags the number on your lander with the ClickFlare click ID, and every call to that number inherits it."}}, {"@type": "Question", "name": "Can I report calls that don't convert?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Add Retreaver webhooks for connected calls, non-converted calls or calls past a set length, each as its own conversion."}}, {"@type": "Question", "name": "How big should my number pool be?", "acceptedAnswer": {"@type": "Answer", "text": "Each visitor gets a unique number, so the pool must cover your visitors at the same time within the lease time. When it runs out, visitors see the default number."}}, {"@type": "Question", "name": "Can I stop repeat callers counting twice?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Use Retreaver's de-dupe setting. Without it, each converted call counts as its own conversion."}}, {"@type": "Question", "name": "Can I use direct tracking instead of a redirect?", "acceptedAnswer": {"@type": "Answer", "text": "Only with custom code. Without a redirect, the click ID isn't in the lander link, so a developer must add it to the Retreaver number on the page."}}], "dateModified": "2026-11-12"}, {"@type": "BreadcrumbList", "itemListElement": [{"@type": "ListItem", "position": 1, "name": "Integrations", "item": "https://www.clickflare.com/integrations"}, {"@type": "ListItem", "position": 2, "name": "CRMs & Call Tracking", "item": "https://www.clickflare.com/integrations/crms-call-tracking"}, {"@type": "ListItem", "position": 3, "name": "Retreaver"}]}]}

Retreaver calls,traced back to the ad

Retreaver integration at a glance

See which ads bring paying Retreaver calls

Calls tied to the click

Each converted call counted

Every call outcome as a column

From ad click to profit per campaignattributed revenueattributed salesa matched conversionautomated actionyour dashboardsclosed revenue

From ad click to converted call

Connected in three steps

What you see once it's connected

How media buyers run it

Ad → lander → call

Publisher or campaign owner

Connected, converted, long calls

Retreaver integration FAQ

Does ClickFlare integrate with Retreaver?

How does Retreaver know which ad a call came from?

Can I report calls that don't convert?

How big should my number pool be?

Can I stop repeat callers counting twice?

Can I use direct tracking instead of a redirect?

Related integrations

See which ads bring paying calls.