Frequently asked questions

Straight answers for the two people who scrutinize an analytics platform hardest — the agency owner who has to trust it in front of clients, and the data analyst who has to defend the numbers. Where the honest answer is "not yet," it says so.

The basics

What is SiteTraffic?

SiteTraffic is a multi-site web-analytics dashboard. It reads your existing platforms — Google Analytics 4, Google Search Console, Meta Pixel, and (rolling out) Bing Webmaster Tools — into one account, scopes everything per site, and lines those numbers up beside first-party visitor data collected directly on your own pages through Mosa.Click. You get one consistent view of traffic, acquisition, search visibility, on-site behavior, and visitor quality across every site you run.

What problem does it actually solve?

The reconciliation problem. Most teams already have the data — it is just scattered across a dozen logins, each with its own definitions and its own version of "performance." Monday mornings turn into rebuilding reports and arguing about whose number is right. SiteTraffic puts every source on one screen, over one date range, with consistent definitions, so the meeting is about strategy instead of about the data.

Does it replace GA4, Search Console, or my other tools?

No. It joins them. GA4, Search Console, and Meta keep doing what they do; SiteTraffic reads them through their official connections and presents them together, next to the one dataset they can't give you — unsampled, first-party behavior from your own site.

What does SiteTraffic not do?

• It is not an ad platform. It reports on marketing performance; it does not create, buy, or optimize ad campaigns.
• It does not de-anonymize individuals. "Who is visiting" means behavioral and quality intelligence — new vs. returning, human vs. bot, engagement, source — not resolving anonymous traffic into named people.
• It is not a tag manager or A/B testing tool.
• Per-social-post traffic attribution is on the roadmap, not shipped (see Social & roadmap).
• There is no public data API yet — exports are via CSV on every view (see exports).

Data accuracy & methodology

Where does the data come from?

• Mosa.Click first-party data — collected directly on your pages via a lightweight script: pageviews, engagement time, page-to-page behavior, new vs. returning visitors, and a classification of every hit (human visitor, good bot, AI crawler, or bad bot).
• Google Analytics 4 — users, sessions, channels, devices, events, engagement.
• Google Search Console — queries, clicks, impressions, CTR, average position.
• Meta Pixel — pixel events, leads, reach, spend, per site.
• Bing Webmaster Tools — search performance (rolling out).

Is the first-party data sampled?

No. First-party data is collected on your own property and reported unsampled — every qualifying hit is counted. That is a key reason it is treated as the source of truth when GA4's modeled or sampled figures and a platform's attributed figures disagree.

Why don't the numbers match between GA4, Meta, and first-party?

Because they measure different things in different ways — client-side tags vs. platform attribution vs. first-party collection, with different bot filtering, session rules, consent handling, and attribution windows. Disagreement is expected, not a bug. SiteTraffic's job is to show the sources side by side over the same date range so you can see how they differ and choose the right one for the question at hand.

Which number should I trust?

It depends on the question. For "what really happened on my site," the unsampled first-party dataset is the most dependable, because nobody else can sample, change, or switch it off. For "how did Google rank me," Search Console is authoritative. For "what did my Meta spend produce," the Pixel is. SiteTraffic keeps them adjacent so you apply the right source deliberately rather than by accident.

How are bots and AI crawlers filtered?

Every first-party hit is classified before it reaches a chart as a human visitor, a good bot (e.g. Googlebot), an AI crawler, or a bad bot. Non-human traffic is labeled and kept out of visitor counts, so your engagement and visitor numbers aren't inflated by automated traffic — and you can still see the crawler and AI-bot activity separately.

How fresh is the data?

It varies by source, and SiteTraffic surfaces each source's freshness rather than pretending everything is real-time:

• First-party — effectively live.
• GA4 — near real-time to a few hours, per Google's processing.
• Search Console — typically delayed 2–3 days (Google's own reporting lag).
• Social (Meta) — refreshed on a daily snapshot.

How do you define "session," "engaged session," and "visitor"?

Within each source, SiteTraffic uses that platform's definitions so the numbers reconcile with the platform itself, and it applies the same date range across every source and site. First-party "visitors" are human hits after bots and crawlers are removed. Because definitions differ between platforms, the dashboard keeps each source labeled rather than silently blending them into a single figure.

How far back does the data go?

First-party collection begins the moment the tag is installed — it builds history forward from install. Connected platforms (GA4, Search Console, Meta) bring whatever history their own APIs expose when you connect them.

Can I export the data? Is there an API?

Every view has CSV export, so any number on screen can travel to a spreadsheet or a board deck. There is no public data API today; if programmatic access is important to your workflow, tell us at team@coreinsites.com — it helps us prioritize.

First-party visitor data (Mosa.Click)

What is "first-party" data, and why does it matter?

First-party data is collected directly on your own website, on your own domain, rather than inferred by a third-party platform's tag. It gives you greater control, clearer governance, and a more dependable measurement foundation — it is the one dataset nobody else can sample, alter, or turn off. SiteTraffic uses Mosa.Click to provide this layer.

Does the first-party tracking use cookies?

No — first-party collection is cookieless, and consent state is stored with each visit.

Does "understand who is visiting" mean you identify people by name?

No. It means visitor intelligence: new vs. returning, human vs. automated, how they engage, where they came from, and how they move through the site. It is consent-aware and first-party — behavioral quality, not personal-identity resolution.

How do I install it?

One small script on your site. On the Business plan you can email the tracking tag straight to your developer, and the guided setup wizard verifies the tag is live before you rely on it.

Will the tracking script slow down my site?

The script loads asynchronously, so it does not block your page from rendering, and it is designed to be lightweight. It sets no cookies and does its classification server-side, keeping the on-page footprint small.

What's the relationship between SiteTraffic, Core InSites, and Mosa.Click?

Core InSites builds and operates SiteTraffic and holds the direct relationship with you. Mosa.Click (a service of Merandian LLC) operates the first-party data infrastructure beneath the dashboard as a subprocessor — it processes your analytics data on your instruction and does not use it for its own purposes. Full detail is in the Privacy Policy.

For agencies & teams

Can I manage many client sites in one place?

Yes — that's the core use case. See the whole portfolio at once or drill into a single site, with sites organized per client on the Agency plan and client-by-client reporting from the same account.

Can I give clients and stakeholders access without paying per seat?

Yes. Viewers are free, read-only, and scoped to only the sites you assign them. Owners and admins manage sites; viewers just see the numbers for their own sites. Everyone shares the same date range and definitions, so there is one trusted view rather than five conflicting screenshots.

Is it white-labeled?

Not today. The Agency plan organizes sites per client and gives client-by-client reporting and scoped viewer access, but the dashboard is presented as SiteTraffic. If white-label branding is important to your practice, let us know at team@coreinsites.com.

How does pricing scale as I add sites and clients?

• Individual — a single site, with first-party tracking, GA4, Search Console, UTM and event tracking, lead tracking, and guided setup.
• Business — 5 sites included (up to 15 at $199/site/month), one admin included (extra admins $150/month), unlimited free viewers, per-site retention 1–10 years, CSV export.
• Agency — 10 client sites included (unlimited at $149/site/month), two admins included (extra admins $150/month), organized per client.

Every data source is included in every tier. Full detail on the pricing page.

Privacy, security & ownership

Who owns the data?

The first-party data is collected on your own property and belongs to you. Mosa.Click processes it as your subprocessor and does not use it for its own purposes.

Is it GDPR-friendly / consent-aware?

First-party collection is cookieless and consent-aware — consent state is stored with each visit — and EU traffic is handled in an EU-aware mode. Note that each website operator remains responsible for its own privacy notice and for obtaining any required consent from its visitors; SiteTraffic gives you the controls, not the legal obligation. See the Privacy Policy.

How long is data retained?

Retention is configurable per site, from one year to ten.

Where is the data processed?

Core InSites operates from the United States and configures US-based regions where available; EU-origin personal data processed on a customer's behalf is governed by Standard Contractual Clauses as described in the Privacy Policy.

Social & roadmap

Does it show social media data?

Meta (Facebook and Instagram) is connected today — follower trends and per-post engagement (likes, comments, shares, reach) via the Meta Graph API, using a Business/Partner access model so a client shares their Page with the platform's business rather than handing over a password.

Can it tell me which social posts drive traffic to my site?

Honestly: platform-level today, per-post is on the roadmap. You can already see how much traffic each channel (e.g. Facebook, Instagram) sends, from referrer and UTM data. Attributing a specific post to the visits it produced — the deeper join between social engagement and site traffic — is in active development.

What's coming next?

• Bing Webmaster Tools in the same unified view.
• Per-post social-to-traffic attribution.
• Additional social platforms (e.g. TikTok, YouTube) over time.

Roadmap items are directional, not commitments to a date.

Getting started

How do I set it up, and do I need to be technical?

Pick a tier, connect a site, and paste one tag. The guided setup wizard verifies each connection — GA4, Search Console, the first-party tag, Meta — as you go, so you know it works before you leave. On the Business plan you can email the tag to a developer if you'd rather not touch the site yourself.

Still have a question?

Email team@coreinsites.com and a person at Core InSites will answer.

© 2026 Core InSites. SiteTraffic.io is a Core InSites product (a trade name of Oak Hill Business Consultants, LLC). First-party visitor data in partnership with Mosa.Click.
Home · Pricing · Privacy · Terms · Contact