Call tracking that shows which marketing makes the phone ring.

Call tracking connects an observable marketing source to an inbound phone call. A dedicated tracked number or dynamic number insertion provides the source signal. The call record can then retain agreed facts such as time, answer status and duration.

Dynamic number insertion, often shortened to DNI, changes the phone number shown on a website when the visitor session contains usable source information. The number pool and attribution window must be sized and configured for the traffic and reporting requirement.

Depending on the source and agreed configuration, Call Tracking can report marketing channel, source and medium, campaign, ad group, ad, keyword, landing page, page called from, call status and duration. CRM integration can add an agreed lead, booking, sale or revenue outcome when reliable matching fields exist.

Yes, when the Google Ads account and required click or mapping data are connected. Campaign, ad group, ad and keyword availability depends on the ad type and integration. Keyword data may be delayed or unavailable, so Gibson confirms the exact reporting fields during setup rather than promising every field for every call.

A direct call from a Google call ad, print piece, directory listing or remembered phone number may not create a website session. Privacy controls, missing click IDs, an expired match window or an incomplete Ads or DNI configuration can also limit the evidence. The report should mark that boundary instead of inventing an attribution source.

Only when there is observable evidence. A visit from an AI assistant may carry referral or landing-session information that a configured website journey can retain. If someone reads an AI answer and dials a general number without visiting or using a dedicated number, that AI source cannot be reliably inferred.

No. A call record proves that a call occurred against the configured source. Lead quality, booking, sale and revenue require an agreed outcome definition and a reliable outcome source, usually the CRM or another operating system.

The number routes to the destination agreed in the setup. Recording notices, whisper messages and routing behaviour are separate configuration choices and are confirmed in writing before launch.

Yes, where routing is included in scope. Gibson can document business-hours, after-hours, overflow and failover destinations. The final routing plan depends on the numbers, teams and operating hours supplied by the customer.

It can when the platform, credentials, fields and write-back rules are supported and included in scope. Gibson confirms the source fields, destination fields, failure path and implementation responsibility before the integration is built.

Recording and notice obligations depend on the call flow, purpose and applicable law. Gibson confirms the technical configuration and data-handling scope, but customers should obtain legal advice for their specific recording and consent obligations.

Timing depends on number provisioning, website access, DNI, routing, recording and integration scope. Gibson confirms the setup responsibilities and target timing in writing after reviewing the brief.

Gibson's currently published starting point is $99 AUD per month plus call usage. Number volume, usage, DNI, routing, recording, Speech Analytics, integrations and reporting can change the final scope. The written quote shows the applicable inclusions and usage charges before commitment.

Yes, subject to the required number plan, routing and reporting design. Gibson has supported an automotive service network of more than 350 stores and approximately 150,000 calls per month. The appropriate design depends on the locations, teams and decisions the reporting must support.

Gibson provides a managed implementation around the tracking platform. The written scope identifies number provisioning, attribution rules, routing, reporting, integrations and the responsibilities retained by the customer.