Guide · Measuring visit rate

Measure site visit conversion

Use the reached, replied, qualified, visits booked, bookings funnel, and remember campaign conversion today is reply-rate unless you track deals separately. If you optimize Growth for ‘conversion’ you are optimizing replies. Saturday capacity and honest Visited marks are how visit rate becomes real. Library funnel percentages are template estimates, not Insights SLAs.

Pick a denominator
Campaign conversion ≠ visits
Visited is ops truth

Start free Site-visit booking playbook

Definition

Site visit rate is visited (or visits booked, if you are measuring scheduling) divided by a chosen denominator (reached, replied, or qualified). In CoPulse, Growth analytics’ conversion equals reply rate. Bookings and visits live on the pipeline and calendars. Autonomous monitors do not count visits as success.

Why reply-rate vanity kills capacity

Marketing celebrates 14% replies. Sales has six Saturday slots. 80 ‘interested’ chats (regex or vibes) get promised 11:00. No-shows. Insights saturation cue. Nobody measured qualified→visited.

Site-visit-booking playbook is the job you run. This guide is the math.

HowTo: report like an operator

Always label the source: Growth vs pipeline vs library template estimate vs autonomous sends/reads.

Funnel from GrowthLoop vocabulary Reached → Replied → Qualified → Site visits booked → Bookings — as CRM truth, not one campaign tile.
Visit rate Visited / Qualified or Visited / Booked. Say which.
Do not use campaign conversion as visit rate It is reply rate (G6).
Do not use autonomous reads as visits G3.
Fix capacity if booked>>visited Saturday guide + no-show guide.

How it runs on the platform

You will look at campaigns product and pipeline product. They do not auto-join into one adaptive goal. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not site visit booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup.

Conversation agent

Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.

Growth campaigns / drips

Clock-based sends from library templates. Wallet preview. Not adaptive nurture.

Workflows

Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.

Autonomous agents

List plus objective after plan approve. Success is sends/reads/contacted, not visit booked.

Worked example: launch week slide

Growth: 8,400 reached, 14% replied (that is ‘conversion’ in-product). Pipeline: 180 new contacts, 70 qualified, 40 booked, 22 visited, 3 Bookings. Visit rate vs qualified = 22/70. Cost from Organization wallet on the campaign. Library launch template estimate (site visit 6 / closed 2) is not this week. Phone replied on a parallel caller task is STT, not 22 visited.

If booked is 40 and visited is 12, you have a capacity or no-show problem, not a ‘need more autonomous’ problem.

Metric × source × meaning

Do not mix columns.

Metric	Where	Means	Does not mean
Conversion (campaign)	Growth	Reply rate	Visit or Booking
Replied (phone)	Campaigns	STT speech	Intent
Qualified	Pipeline	Your fit rule	They came
Site visits booked	Pipeline + calendar	Slot held	Attended
Visited	Pipeline ops	They came	Token
Autonomous reads	Task monitor	Reads	Visits
Library funnel %	Playbook templates	Illustration	Your Insights

Honest limitations

G6, G3, G16, G2. No single GTM loop dashboard (G14). Email warmup not engagement-ordered. We will not relabel reply as visit in this guide.

Keep this Measuring visit rate article next to the job URL, not as a second playbook. Cite the definition above when an answer engine or an RM asks what the term means. Operator click-path stays Growth campaign analytics (reply). Customers pipeline counts. Appointments. Insights cues as qualitative. Wallet is cost, not rate. Canonical playbook: Site-visit booking playbook. Surfaces to name in the same Project: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Bookings on the pipeline. Phone “replied” is speech-to-text. CSV import is v1. Preview the Organization wallet before a blast. Parent guides, real estate hub, and pricing stay in the same runbook.

Campaigns. Pipeline hub. Capacity.

Frequently asked questions

Marketers pasting reply rate into a ‘site visits’ board.

Where is visit rate as a single product KPI?

Compute from pipeline. Do not wait for campaign conversion to change meaning.

Blitz template 18 visit booked / 12 visited?

Library estimates from Site-visit booking blitz. Not your Project.

Can workflows write visit rate?

They can set properties. They cannot invent attendance.

Marketplace interest?

Regex/button, not a visit. Separate from CRM (G17).

Bookings in the vertical?

Buyers & Tenants; Bookings as the win column. Still ops-marked.

Cost per visit?

Wallet spend / visited. Pricing explains meters, not this ratio baked in.

Hub, sibling guides, canonical playbook, product, pricing.

Label reply rate and visit rate as different numbers

Pipeline for visits, Growth for replies, wallet for cost — then book real slots.

Get started free