Router analytics server-side · RevOps view

Synthetic demo data to illustrate the operating model.

Routing flow →0 live test rowsno real HubSpot writes

Median time to routed lead–from email to routing decision

Demo cohort0live handoff rows

Stored session trails0all rows in storage

Server handoffs0submitted after route calculation

Enrichment hit rate0%company resolved from domain

Session funnel

Router started

0100%

Email entered

0100%

Qualified input

0100%

Route calculated

0100%

Handoff persisted

0100%

Meeting/trial started

0100%

step conversion vs. previous stage · seeded demo cohort shown when present · handoff means server_handoff_submitted after route_calculated

self-serve

00%

hybrid

00%

sales-led

00%

share of 0 routed sessions · 0 sessions dropped before route calculation

CTA	intent	sessions	route rate	calendar rate

each CTA emits its own click event; entry intent is the grouped signal used by the router

received	lead	motion	score	intent	firmographics	skipped	time-to-route	outcome	CRM sync

Event data dictionary — the tracking plan behind every number above

event	consent	what it tells us
cta_clicked	analytics	Which CTA opened the router — the first routing signal
router_started / _with_intent	necessary	Flow start; intent carried from the clicked CTA
email_entered	necessary	The one field everyone types
company_domain_extracted	necessary	Domain derived client-side for enrichment + company matching
enrichment_resolved / _failed	analytics	Provider lookup outcome incl. source and resolved fields
step_skipped	analytics	A question the visitor never had to answer — friction removed
field_confirmed / _corrected	analytics	Trust in enriched data vs. manual override
employee_range/office_count_selected	necessary	Answers given when enrichment could not resolve them
complexity_flags_selected	necessary	Enterprise requirements incl. 'none' and 'not_sure'
route_calculated	necessary	Motion decision + complexity score
hubspot_payload_prepared	necessary	CRM payload assembled, consent-aware
calendar_loaded / slot_selected / meeting_booked	mixed	Sales-led conversion steps
trial_started	necessary	Self-serve / hybrid activation entry
server_handoff_submitted	necessary	Trail + payload persisted server-side

Downstream join — where this connects in production

lead	meeting attended	opportunity	pipeline value
captured here ✓	awaiting CRM data	awaiting CRM data	awaiting CRM data

in production these columns join via the HubSpot contact — website changes become measurable in pipeline, not clicks