Site statistics are not just a visit counter in hosting. After installing Insytix tracking (embed code or WordPress plugin), data flows into events storage and appears in the dashboard for the date range you pick. This article answers plainly: what you will see on screen, what each metric means, and what is not counted automatically.
We will not show sample numbers — no invented “industry averages.” Every value in your dashboard depends on real traffic and tracking setup. If numbers stay at zero, the issue is usually embed or tag blocking, not a mysterious platform bug.
The dashboard splits between KPI cards at the top, charts over time, traffic source breakdown, a leads list, and additional panels depending on site type (services versus store). Filtering by period (today, week, month, or custom range) shifts all numbers together.
What happens once tracking is installed
The tracking script (tf.js) loads in the visitor browser and sends events to the Insytix API with your site ID. A page_view fires on page load; further events fire only when the system detects an action — for example a tel: link click, a form submit, or store events on WooCommerce when integration is active.
The dashboard shows connection status: whether the tag was seen recently on the site, and sometimes hints if endpoint or ID is missing. Until events arrive, cards show a dash or zero with context that nothing is measured yet — so zero does not look like real quiet traffic.
Visitors and page views
The unique visitors card (uniqueVisitors) summarizes how many distinct visitors appeared in the range — not how many times they came back. The page views card (pageViews) counts all page loads, including one visitor hitting several pages or the same page again.
The distinction matters: a campaign bringing repeat visitors can raise page views without much growth in new visitors. Time charts show both trends, and you can open source breakdown to see which channel drove them.
Leads: phone, WhatsApp, and forms
On service sites the focus is contact actions. Phone clicks (phoneClicks) count when the link is tel: format or marked for tracking — not every number-looking text on the page. WhatsApp clicks (whatsappClicks) count on wa.me links or similar patterns the script recognizes. Form submissions (formSubmissions) count as form_submit after a successful send.
The leads list in the dashboard centralizes inquiries saved with fields the visitor left. That is business data, not just a tally. Combined with push alerts you can get a mobile ping when a new inquiry arrives — useful when nobody sits at the desk all day.
Online store statistics
When the site is marked as e-commerce, KPI cards change: beyond traffic and leads you see cart adds (cartAdds), completed purchases (purchases), abandoned checkouts (abandonedCheckouts), revenue (revenue), and total events (totalEvents) in the range. These tie to on-site events or the WooCommerce plugin when configured.
Remember: revenue in the dashboard depends on order data the tag captures. If checkout lacks the tag or orders do not emit an event, purchases will not show even if sales happened. Stores should validate checkout and thank-you pages like the home page.
Traffic sources and integrations
Source breakdown shows where visitors came from: search, ads, social, referrals, direct. When integrations are connected (Google Analytics, Search Console, Google Ads, Meta, and others — per what you enabled), extra widgets show data from those links. If an integration is disconnected or errors, the UI should show error state rather than hiding the tab.
Insytix sources come from what the tag sees in the browser (UTM, referrer). They complement, not replace, GA4 depth reports when GA is also installed.
Real time versus historical range
Some views show active visitors or recent activity near now. Main KPI cards respect the date filter you chose — switching from “this week” to “today” updates all totals at once. When comparing to a prior period, the system may show trend direction versus the parallel range.
For short decisions — what happened this morning — today or yesterday is enough. For trend detection — a week or month. Jumping ranges without context (comparing Saturday to Tuesday) produces wrong conclusions.
What does not appear automatically
- Custom GA4 conversions — only if you connected integration, not as a duplicate.
- Phone text without a tel: link — will not count as phone_click.
- Store sales without a purchase event from the site — will not show in purchases.
- GMB data (reviews, profile calls) — belongs to maps integration, not on-site tracking.
This list prevents frustration: an owner expecting “every click on the site” will find totalClicks or specific engagement metrics depend on what you marked and what the script recognizes. A missing event is usually fixed in HTML or form setup — not by swapping dashboards.
Reading the numbers correctly
Start with one weekly question: “how many site leads?” Only then widen to “from which source.” Compare week to week on the same weekdays when you can. If GA4 is also installed, compare trends — not identical daily totals.
💡 A green or red trend chip does not mean automatic success — open the breakdown and confirm leads rose, not only views. On service businesses, three quality inquiries beat a hundred visitors with no call.
More views in the same dashboard
Beyond headline cards you will find recent activity feeds, individual event lists, and sometimes integration tabs (search, ads, maps) showing external data next to what tf.js measures. Each tab still respects the date range and connection status.
On the multi-site home you see visitor and lead summaries per site — handy for agencies managing several clients. Confirm each site uses the correct tracking ID so domains do not blur together.
Summary
After Insytix embed, dashboard statistics reflect real events: visitors, views, leads, and on stores cart and purchase metrics too. Each metric maps to a defined event type; understanding view versus phone click versus form is what turns the dashboard into a decision tool.
Confirm tracking is live, pick a consistent date range, and use the leads list and alerts for immediate action. Other reports build on the same event foundation.
Frequently Asked Questions
Why is everything zero after install?
Usually no traffic yet, the tag is not on all pages, or site optimization blocks the script. Check tracking status in the dashboard and load the site in a browser after cache clear.
What is the difference between a lead and a form in the numbers?
formSubmissions counts submit events. The leads list shows saved field records. Failed validation might avoid creating a lead even if a submit attempt was logged — depends on form setup.
Do statistics include bots?
The system attempts basic bot filtering server-side. Not every bot is blocked; if you see a spike, check suspicious traffic source before marketing conclusions.