usdigitalmarketingindex.com SEO
How can phone calls from organic search be attributed to their entry landing pages?
Updated November 15, 2026
By recording, at the moment a visitor arrives, which page they entered on and that they came from organic search, and then tying that record to the call. There are two ways to make the tie. The lighter one counts taps on the phone link as an event in analytics, which carries the session’s landing page and source with it. The fuller one shows each visitor a tracking phone number assigned to their session, so that when the number is dialed the call system knows which session, and therefore which landing page, it belongs to. Both produce an attribution, and neither is complete. Calls dialed by hand from a number seen earlier, calls made days later, and calls from visitors who declined tracking fall outside. The setup should be documented with those limits stated.
Call event design
Decide what counts as a call and where it is recorded.
| Method | What is recorded | Captures | Misses |
|---|---|---|---|
| Click-to-call event | A tap or click on a <!–INLINECODE0–> link | Intent to call, with session source and landing page | Whether a call connected; calls dialed manually; desktop visitors reading the number |
| Call tracking with a static number per channel | Calls to a number shown only to organic visitors | Connected calls from the channel | The landing page |
| Dynamic number insertion | Calls to a number assigned to a session | Connected calls with session data: source, landing page | Calls to the main number remembered or seen elsewhere |
| Asking the caller | Staff record how the caller found the business | Calls no system tracked | Detail; depends on the caller's memory |
For landing-page attribution, the choice is between the click-to-call event and dynamic number insertion.
Define the event precisely.
| Field | Definition |
|---|---|
| Event name | One name used everywhere, for example <!–INLINECODE1–> |
| Trigger | Click on any link whose <!–INLINECODE2–> begins with <!–INLINECODE3–> |
| Parameters | Page where the click happened; link position |
| Session data attached | Source and medium; landing page of the session |
| Qualified call | A connected call above a minimum duration, set by the business, recorded by the call system |
A click is not a call. Report click events as clicks, and connected calls as calls.
Where a consent banner applies, call events recorded in analytics depend on the visitor’s consent like any other event. Estimating what goes unmeasured is covered in the guide to how organic conversions can be estimated when consent settings limit tracking.
Landing-page attribution windows
The landing page is the first page of the session in which the visitor arrived from organic search. The page where the number was tapped may be a different one. Record both.
A measurement flow diagram:
Organic search click
|
v
Landing page loads ---> session starts: source = organic,
| landing page = /boiler-repair/
| (stored with the session)
v
Visitor browses ---> /pricing/ ---> /contact/
|
v
Visitor taps the phone number on /contact/
|
+--> Path A, click event:
| event phone_call_click
| page = /contact/, landing page = /boiler-repair/,
| source = organic
|
+--> Path B, dynamic number:
number shown was assigned to this session
call arrives at the tracking number
call system looks up the session:
landing page = /boiler-repair/, source = organic
call record: start time, duration, answered or not
|
v
Report: calls by landing page, for sessions with organic source
Windows to define:
| Window | Question | Decision to record |
|---|---|---|
| Session window | Does the call belong to the visit in which the number was shown? | Yes by default |
| Number hold time | How long is a dynamic number kept for one visitor before reuse? | Long enough that late calls are not credited to the next visitor |
| Return visits | If the visitor returns directly a day later and calls, which source gets the call? | State the rule: first touch, last non-direct touch, or the session of the call |
| Lookback | How far back is a prior organic visit credited? | A fixed number of days |
The return-visit rule matters. A caller who found the business through organic search on Monday and came back by typing the address on Wednesday is an organic-originated call under a first-touch or last-non-direct rule, and a direct call under a same-session rule. Neither is wrong. The report must say which was used.
Counting calls says nothing about whether they were worth receiving. Judging a campaign when the volume of leads rises and their quality falls is covered in the guide to how an SEO campaign should be evaluated when lead volume grows but lead quality deteriorates.
Dynamic number insertion considerations
Dynamic number insertion replaces the phone number on the page with one from a pool, by script, per session.
| Consideration | Detail |
|---|---|
| Pool size | Enough numbers for concurrent visitors; too few, and calls are credited to the wrong session |
| Script dependence | The swap happens in the browser; if the script is blocked or slow, the visitor sees the default number |
| Consent | Assigning a number to a session is a form of tracking; apply the site's consent rules, and show the default number to visitors who decline |
| Number consistency elsewhere | The business's real number stays in the HTML source, in structured data, and on its Business Profile and directory listings |
| What crawlers see | The default number in the served HTML, unchanged |
| Number format | Local numbers that look like the business's own, where possible |
| Printed and remembered numbers | Calls to those bypass the system |
| Recording and privacy | Call recording, if used, has its own legal requirements |
The consistency point is where call tracking and local search meet. The number published in the page’s HTML and markup should be the business’s real number, the same one on its listings. The tracking number appears only through the script, to visitors, in place of it. Do not publish tracking numbers in directories or in structured data.
Limits to document:
- visitors who decline consent are not attributed;
- a call made from another device than the one that browsed is attributed only if the number shown was dialed;
- shared numbers between sessions can cross-credit calls when pools are small;
- calls made after the hold time are unattributed or misattributed;
- repeat callers who saved a tracking number will be credited to their original session indefinitely.
Data integrity tests
A validation checklist:
| Test | Method | Pass condition |
|---|---|---|
| Event fires | Tap the phone link on several templates, on a phone | One event per tap, with page and link position |
| Landing page recorded | Arrive from an organic result on one page, navigate to another, tap | Event or call record shows the entry page, not only the tap page |
| Source recorded | Repeat arriving from a paid link and by direct entry | Each labeled correctly |
| Number swap | Load as a new visitor from organic search | Tracking number displayed; default number in page source |
| No swap without consent | Decline consent, reload | Default number displayed |
| Call record | Place a test call to the displayed number | Call logged with the right session, landing page, and duration |
| Pool exhaustion | Open more sessions than the pool size | Behavior as designed: default number shown, not a reused one |
| Hold time | Call after the hold period | Not credited to a later session |
| Markup unchanged | Run the page through a structured data test | Real number in markup |
| Duplicates | Compare event count with call count over a week | Ratio stable; no double firing |
| Reconciliation | Compare tracked calls with the phone system's total inbound calls | Tracked share known and recorded |
The last test gives the coverage figure: of all inbound calls, the share the system attributed. Report it next to every call attribution table. If 55 of every 100 calls are attributed, the landing-page breakdown describes those 55.
A report layout:
| Landing page | Organic sessions | Call clicks | Connected calls | Qualified calls |
|---|---|---|---|---|
| [page] | ||||
| Unattributed | [count] | [count] |
Keep the unattributed row. It shows how much is not known.
Document the setup in one page: the event definition, the attribution rule and windows, the pool size, the consent behavior, the minimum duration for a qualified call, and the last validation date.
What a call is worth, and how to turn calls into a revenue estimate for a keyword, is a separate modeling task, covered in the guide to how to estimate a service keyword’s revenue potential before building its landing page.
The rule: store the entry page with the session, tie the call to the session by event or by assigned number, state the attribution window, and report the share of calls the method could not attribute.
Add your comment to this answer