01
Define the question before adding analytics
For a service website, start with the route from a relevant landing page to a call, WhatsApp conversation or useful enquiry. Decide what should count as an event and what qualifies as a real lead.
Staats describes agent-oriented website analytics and MCP workflows. Its documentation includes tools for context, funnels, annotations and comparisons around changes. These tools help investigate behaviour; they cannot identify revenue that was never recorded.
02
Install from the current documentation
Use the current tracker snippet and site identifier from Staats documentation. Its documented tracker uses the data-staats attribute; do not reuse an old data-track example without checking compatibility.
Verify that a visit to your actual deployed site appears under the right site. Check duplicate tags, blocked requests and events from previews. Document your privacy and consent choices for your actual jurisdiction and setup rather than assuming a vendor label settles them.
03
Build a small, meaningful funnel
Choose a relevant landing page, a service or proof interaction and an enquiry action. State whether a click is only an intent event or whether a completed conversation or submission can also be verified.
Use the documented funnel and site-context workflows to describe page purpose. Exclude staff, bots and repeated tests where possible. If the sample is tiny, report raw counts and the uncertainty instead of declaring a conversion-rate win.
04
Use MCP to compare a deployment
Record an annotation with the date and exact change. The documented record_annotation and compare_around workflows can help a reviewer compare the periods around that event.
Check other explanations: different campaigns, weekdays, seasonality, tracking changes and shifts in visitor intent. A before-and-after comparison is an observation, not a controlled experiment. Do not attribute every increase to the new design.
05
Turn findings into a website decision
If visitors reach the right service but do not enquire, inspect unanswered questions, proof and friction before adding more tracking. If the landing traffic is unrelated, improve targeting and page purpose first.
Review the vendor’s current plans and integration access directly. Keep a measurement log the business can understand and export. Pair the data with actual enquiry quality to decide what to build next.
Sources
Primary and supporting sources
Use the linked documentation to check current pricing, access and product behaviour. The dates above describe this article; they do not guarantee that every vendor claim remains current.