Your campaigns drive calls

When a visitor lands on your site, the script replaces the phone numbers on the page with a unique tracking number tied to that visitor's session. The visitor dials it, the call is forwarded to your real number, and your call centre receives it exactly as normal, no PBX changes, no agent retraining, no difference for the caller. Behind the scenes, the call is matched to the session, so the campaign, keyword, and pages that led to it are recorded and forwarded to your ad platforms, analytics, and CRM within seconds.

Because each of those sees only its own half. GA4 sees the session but loses the visitor the moment they dial. Your call centre reporting sees the call, volume, duration, queue, but has no idea which campaign created it. Your CRM sees the customer once an agent logs them, with the marketing origin already gone. Call-Tracking is the join between the halves: it is the only technology that can fully connect a first-time visitor, with no login and no prior identity, to a given call. That connection is what gives your bidding algorithms eyes and ears on call conversions.

No, they operate on different layers and typically become integrations rather than overlaps. Conversation analytics tools like Capturi analyse what was said on the call; Call-Tracking establishes where the call came from, they complement each other. Salesforce native telephony handles the agent-side workflow of the call; Call-Tracking supplies the marketing attribution Salesforce cannot see. Form tracking covers forms; calls remain invisible to it by definition.

No. It is a single JavaScript snippet, deployed via Google Tag Manager, Tealium, Adobe Launch, or directly, loaded asynchronously and page-speed safe. The number replacement activates once the page has loaded, so nothing blocks rendering. Single page applications are supported through a virtual pageview signal. We recommend loading bmetric after your analytics scripts and before third-party advertising tags.

Two legal bases apply. The script's session tracking requires the visitor's cookie consent, delivered through your consent management platform, bmetric documents the cookie category and your CMP loads the script conditionally. The data processing itself happens on your instruction, with bmetric as data processor and your organisation as controller, under a standard DPA that meets Article 28 requirements. Phone number and IP address are personal data and are handled accordingly, numbers are not linked to a name or profile unless you enrich them via your own systems.

Call-Tracking is tracking, so it operates only when consent is given. For visitors who decline, no session tracking runs. Lead capture can continue for those visitors through bmetric's privacy-compliant contact option strategy, just without session-level attribution.

Per call: the tracking number dialled, the session and campaign context, time and duration, and outcome if categorised. Personally identifiable data is retained for 60 days by default and then deleted automatically, with session-level attribution data retained per your instruction as controller.

No. Your published numbers stay yours, the swap happens dynamically in the browser, only for tracked sessions, and only for the numbers you whitelist for forwarding. Offline placements, print, directories, keep working unchanged, and static tracking numbers can be added for offline channels if you want those attributed too.

An ongoing connection, not a one-off configuration. Included means bmetric sets up, configures, and operates the integration so data flows automatically: conversion events to Google Ads and Meta, call events to GA4, Adobe, or Piwik PRO, and records to your CRM. bmetric can also retrieve the outcome of sales and forward outcome events to the same platforms, so the loop closes on what each call was actually worth.