Skip to content
Proofbell

Installation · about ten minutes

Three steps, then it runs itself.

Installing takes about ten minutes. After that the only ongoing work is telling us what a call was worth — and if your CRM is connected, not even that.

Create a free account Read the install guide
ONE PAGE VIEW · SAMPLE NUMBERS · THE TAG LOADS ASYNCHRONOUSLY 01242 555 123 01 · YOUR PAGE, AS WRITTEN one line of script in the head (01242) 555123 +441242555123 LAST 9 DIGITS MATCH 02 · MATCHED, ANY FORMAT your formatting is preserved VISITOR A · 01242 ··· 914 VISITOR B · 01242 ··· 915 one number each, from the pool 03 · SWAPPED, PER VISITOR held 30 minutes by default BLOCKED · SLOW · SCRIPT ERROR 01242 555 123 your real number stays 04 · IF ANYTHING FAILS you lose the attribution, never the call
Fig. 00 · the tag, end to end · sample numbers

Fig. 01 · Step 1

one line of script

Add one line of script

The tag swaps the phone number on your site for a tracked one, per visitor, and records how they arrived — referrer, campaign, landing page, and the click id the ad platform attached.

It matches your number by its last nine digits, so it works whether your page writes 01242 555 123, +441242555123 or (01242) 555123, and it preserves whichever format you used. If anything fails — a blocked request, a slow response, a syntax error elsewhere on the page — your real number stays exactly where it is. A tracking script must never cost you a call.

YOUR PAGE · THREE FORMATS · SAMPLE NUMBERS 01242 555 123 +441242555123 (01242) 555123 LAST 9 DIGITS MATCH SWAPPED PER VISITOR IF ANYTHING FAILS YOUR REAL NUMBER STAYS YOUR FORMATTING IS PRESERVED
Fig. 01 · one number, three formats · sample numbers

Fig. 02 · Step 2

nothing changes

Calls arrive with their history attached

The call rings your normal phone. Nothing about how you answer changes. In the dashboard it carries the channel, campaign, landing page and — where the platform reports it — the keyword.

Routing, opening hours, an IVR menu, a whisper before you pick up, voicemail: all of it configurable as a call flow, one live per website. Spam is scored and excluded from both your bill and your reports, which matters more under per-answered-call pricing than per-minute. Your team can also be told the moment a call needs attention — by email on every plan, or in Slack from Growth — and on every paid plan the recording is transcribed with its sentiment, topics, caller intent and a short summary attached, so the shape of the call is on the screen before anyone listens to it.

ONE CALL, AS IT ARRIVES · SAMPLE RINGS YOUR NORMAL PHONE NOTHING ABOUT HOW YOU ANSWER CHANGES IN THE DASHBOARD CHANNEL PAID SEARCH CAMPAIGN ROOF REPAIRS LANDING PAGE /ROOF-REPAIRS/ KEYWORD ROOF REPAIR WHERE THE PLATFORM REPORTS IT
Fig. 02 · one call, as it arrives · sample values

Fig. 03 · Step 3

csv or crm

Send the outcome back

When a call becomes a quote and then a sale, the value comes in from your CRM or a CSV. Proofbell pushes it to Google Ads, Microsoft Advertising and Meta so bidding optimises on revenue rather than call volume.

This is the half that changes what your budget does rather than just what your reports say. Every push is logged with what was sent, when, and whether it was accepted — and when a £2,000 deal becomes £8,000, the platforms are corrected rather than left stale. GA4 and LinkedIn Ads can take the same push, partially: GA4 only within 72 hours of the call and only for a visitor its own cookie can still identify, and LinkedIn only when the visitor arrived by clicking a LinkedIn ad, since LinkedIn has no phone identifier at all. HubSpot reads deal values straight from your CRM as the revenue itself; a Xero connection for revenue from invoices is built but has no connect flow behind it yet, so it is not usable today.

FROM YOUR CRM OR A CSV · SAMPLE VALUES DEAL · £2,000 DEAL · £8,000 DEAL · £640 MATCHED TO THE CALL GOOGLE ADS OFFLINE CONVERSION ACCEPTED UNMATCHED · EXPLAINED SHOWN IN THE REPORT
Fig. 03 · the outcome going back · sample values

Before the awkward questions

A tracking product that only works in the demo is not a tracking product. These are the ways it degrades, and what we do about each one.

Fig. 04 · Where it degrades

The questions worth asking first

What if a visitor calls a week later?

By default the number stays assigned for 30 minutes after their last page view, the same starting point most tools use. What is different is that it is a setting, not a fixed ceiling: our B2B template holds a number for 24 hours precisely because a considered purchase gets read on Tuesday and rung on Friday, and any account can be configured further out than that once its own lag is measured.

What if you run out of numbers?

Sessions fall back to a static number for that source, and every call that happened on the fallback is flagged in reporting so you know attribution was coarse for those. We also size the pool from your measured concurrency and tell you before it happens.

Will your numbers match Google Ads exactly?

No, and nor will anyone’s. Different attribution windows, different models, different definitions of a conversion. Every report carries a reconciliation line, and we show which conversions were matched and which could not be.

What about consent?

Tracking is gated on consent state, and so is activation: an identifier is never pushed to an ad platform for someone whose consent does not permit it. That is enforced in the pipeline rather than left to configuration discipline.

Fig. 05 · Start

Ready to see it?

Install the tag on a free account and watch your web traffic attribute itself. Add a plan when you want a tracking number, and the calls start arriving with the campaign that produced them attached.

Create a free account Read the install guide