Read your site analytics
Understand native traffic, conversion and value reports with the right date range, timezone and missing-data checks.
Chris Luke
3 min read
KrabiClaw has native site analytics. You do not need to connect Google Analytics to read the native record. Use analytics to answer one question at a time, such as which pages attract visits or which campaigns lead to a recorded customer action.
1. Set the business and period
Choose the correct business and state a start and end date. Dates are inclusive in the site's reporting timezone. The assistant summary defaults to the last 30 calendar dates, ending today; ask it to show the resolved dates and timezone rather than assume your device timezone.
Check when data collection began. An empty report for a period before collection started is not evidence that no one visited.
2. Separate visits from outcomes
Pageviews count page activity; sessions and visitors describe different populations. A session may contain several pageviews and outcome events, so those totals are not interchangeable.
For session conversion rate, use converting sessions divided by eligible sessions in the same group and period. Do not divide the number of events by sessions: one session may produce several events. Name the outcome you are measuring and include its denominator.
Try with your connected assistant
Replace the example business, page and details with your own.
Explain a monthly report
For Harbor Studio, summarize native analytics for 1–30 September 2026. Show the reporting timezone, collection start and any missing coverage. Report sessions, pageviews, top pages and recorded conversions. Explain each conversion rate's denominator, and keep quoted booking value separate from verified payment revenue.
3. Check attribution and value
Source, medium, campaign and content can help explain where activity came from. Session attribution and an outcome's own attribution snapshot describe different populations; do not combine them as if they were the same funnel. When comparing reports, keep the attribution basis and filters consistent.
A booking's quoted value is not paid revenue. Purchase revenue requires a verified payment. Read refunds and net amounts alongside collected amounts, and keep currencies separate. Some cash totals include tax while value fields are tax-exclusive; check the measure before comparing totals.
4. Investigate gaps before drawing conclusions
Missing data is different from zero. Older events may not contain dimensions introduced later. Ask for measurement coverage and missing fields before claiming that a channel or location had no activity.
For a deeper question, an assistant can query native events, sessions or grouped breakdowns and continue through every page of results. A page of rows is not necessarily the whole result. Prefer aggregate answers unless individual records are necessary, and avoid sharing visitor identifiers outside the people who need access.
Use Google reports when useful
Connect Google Analytics and Search Console for those services' reporting. Keep the provider, date range, timezone and metric definitions visible when comparing results; different collection and attribution rules can produce different totals.
Next: choose one page or campaign to improve, make a specific change, and compare a later period using the same definitions.