Phone Taps

The SG-Admin Phone Taps module — call-tracking signals, attribution, event surfacing.

The Phone Taps module in the admin is the per-site surface for call-tracking. When visitors tap a phone link on the public site, the platform records the tap event with attribution context. Operators use this to understand call-driven conversion alongside form submissions and other capture channels. This page is the Reference definition.

What is this for?

Read this page when you want the structural definition of phone-tap tracking — what gets captured, what attribution attaches, and where the data surfaces.

Good use cases

• You are scoping call-driven conversion tracking.
• You are explaining to a stakeholder how SGEN handles phone-link analytics.
• You hit a "did our phone CTA drive any taps?" question.

What NOT to use this for

• Step-by-step procedures — open the relevant Guide.
• Per-release shipped change — open What's New or Changelog.

How this connects to other features

• SG-Admin Overview — parent surface.
• Analytics — broader analytics surface that surfaces tap signals.
• Lead and Tracking Workflow — workflow Phone Taps participates in.

Where to find it

Open SG-Admin for the active site. Phone Taps is in the sidebar under the analytics or reporting group. The tap log and per-number summary are accessible to Editor and Admin users.

Definition

Phone Taps tracks call-link interactions on the public site. When a visitor taps a phone link (typically a tel: link rendered via a button or text), the platform records a tap event. Each tap carries the phone number tapped, the source page, the visitor session, and any campaign attribution.

Purpose

Define the Phone Taps module as a Reference layer.

Scope

Covers tap event tracking, attribution, surfacing. Does not cover voice-call recording (out of scope) or per-step setup (Guides).

Tap event model

Phone number

The number tapped. Multiple numbers can be tracked per site.

Source page

The page the visitor was on when the tap fired.

Session

The visitor session identifier for cross-event attribution.

Campaign attribution

UTM-style campaign tags propagated through the visitor's session.

Timestamp

When the tap fired.

Surfacing

Tap events surface inside the Phone Taps module's event log + summary view, and roll up into the Analytics module's broader conversion view.

Constraints and boundaries

Phone Taps is a Reference area for call-link tracking.

Do not use for: voice-call recording (out of scope), per-step setup (Guides).

Public boundary

This page is intentionally public-safe.

Examples

Example 1 — Operator scopes call CTAs for a campaign

Operator confirms tap-tracked numbers are wired into the campaign landing page CTAs. After the campaign, opens Phone Taps to count tap-driven conversions per page and per UTM tag.

Example 2 — Operator compares tap volume across pages

Operator reviews the per-page tap distribution to understand which pages drive the most call interest. The data informs page placement of phone CTAs.

Example 3 — Stakeholder asks "are calls tracked?"

Operator opens this Reference + the Phone Taps module surface, shows the tap log + summary view.

Documentation guidance

Use this page as the structural definition for the Phone Taps module.

Reading order

Open this page when scoping call-driven conversion. Pair with Analytics for the broader conversion view.

Related reading

• SG-Admin Overview — parent surface.
• Analytics — broader analytics surface.
• Lead and Tracking Workflow — workflow context.

Vocabulary cross-reference

• Tap is one phone-link interaction.
• Tracked number is a phone number Phone Taps records taps for.
• Attribution is the campaign / referrer / session context attached to each tap.

Maintenance discipline

When Phone Taps changes across releases (new attribution field, new tracking surface), update this Reference.

Related reading