Call tracking that reveals what makes the phone ring.

A visitor arrives from an identifiable source and sees a number selected from a controlled pool. The call forwards to the existing business number while source, campaign, page and duration are recorded.

The event can then reach GA4 and Google Ads. Qualified sales feedback is stronger than raw call volume, and the number pool must reflect concurrent traffic and session length.

Size the number pool for concurrent active sessions. If it runs out, two visitors can share a tracking number and attribution becomes unreliable. Keep number assignment long enough for reading and calling without reserving capacity indefinitely. Test clickable telephone links, visible numbers and mobile menus. Never replace the fixed business number in structured data or external directories.

Calls from ad assets and calls from a website after an ad click need separate conversion actions. A click on a telephone link is not necessarily a completed conversation.

Minimum duration can remove obvious noise, but sales status is the stronger signal. Assign only defensible values and optimise towards actions the sales team wants.

Create separate actions for calls from ads and qualified website calls. For lead generation, the Count setting is often One so repeat calls after one ad interaction do not inflate demand. Set call length from real conversations, not guesswork. If CRM qualification is imported, keep the early call secondary and use the qualified outcome for bidding.

Law firms, trades, clinics, B2B companies, motor retailers and travel businesses often receive valuable enquiries by phone.

Call tracking matters most where several campaigns compete for budget and qualified calls carry commercial value. Map volume and decisions before implementing.

A clinic can compare treatment pages, a trades business can separate emergencies from quotations, and a B2B team can connect a campaign call with a later CRM qualification. Travel companies can identify destinations that prompt advice. In every case, the call data must support a real decision about media, staffing or page content rather than merely adding another dashboard metric.

Apply purpose limitation, data minimisation, controlled access and appropriate retention. Document the provider's processing and deletion terms.

Recording is optional and needs a clear legal basis and caller information. V7 implements the technology, while your legal adviser should assess the legal position.

List exactly what the provider stores. Telephone numbers, IP addresses, source, duration, recordings and notes carry different privacy implications. Set retention for the measurement purpose and restrict exports. If an event is sufficient, a recording or full caller number may be unnecessary. Explain the supplier and purpose in your privacy information and ask legal counsel to assess the basis.

Define a qualified call, map channels and numbers, and select a provider based on integrations, processing and number portability.

Implement through GTM, test forwarding, preserve NAP consistency, connect GA4 and Google Ads, and review sales feedback after launch.

Run an acceptance test from each important channel. Confirm number replacement, forwarding destination and source in the call log, then verify the event in GA4 DebugView and its Google Ads status. Also test direct traffic, declined consent and navigation across several pages. Do not include the conversion in automated bidding until the complete route has passed.