Why GA4 is confusing, and what to do

GA4 is confusing because it is several products sharing a UI: event taxonomy, user-id stitching, consent mode, modeled conversions, explorations, advertising identity, and a property that still thinks in "sessions" while the docs insist sessions are gone. You did not fail onboarding. The object is large.

SiteLine is smaller on purpose. If you need GA4's ad platform, you still need GA4. If you need "what pages were viewed, which named events fired, did they hit /thanks, what did Google searchers click," you do not.

What people usually mean by "GA4 is confusing"

Events for everything. A page view is an event. A scroll is an event. A video is an event. Your schema is a committee. SiteLine has two ingest types: pageview and custom. Custom needs a name. Max 10 properties. That is the whole taxonomy you have to govern.

Identity. GA4 tries to recognize a person across devices when it can (User-ID, Google signals, device id). SiteLine hashes truncated IP + user agent + a daily salt. No cookie. No cross-day person. No cross-device person. Reports will not match. They should not.

Conversions as configuration archaeology. GA4 marks events as conversions, then models some of them when consent mode ate the hit. SiteLine goals are exact path, path contains, or event name, defined in the dashboard, derived from events you already sent. No extra hit. No modeled row.

Explorations vs reports vs advertising. Three places that disagree. SiteLine analytics is Overview, Live (~30 minutes), dimension breakdowns (pages, referrers, countries, devices, browsers, OS, UTMs, event names), Goals, Funnels, Install. Search Console is a separate report with its own lag.

Quota and sampling language. GA4 properties have free-tier and 360-tier ceilings that surface as "(other)" rows and sampled explorations. SiteLine Starter is 1M billable events per period at $4.99, Growth 10M at $19.99, Scale $99.99 with $2.99 per extra 1M. Soft cap: ingest continues, charts hide post-cap data until you upgrade. Scale does not hide on volume; it meters. That is a billing sentence, not a sampling sentence.

What you should do instead of becoming a GA4 expert

Keep GA4 if ads and Google-owned identity are the job. Add SiteLine if Search Console history and first-party on-site counts are the job. They can run together. They will not reconcile.

SiteLine also keeps GSC: 16-month backfill, 25k rows/day per report, retained while you subscribe. GA4's "Search Console linking" is not a 16-month warehouse. If the pain is "Google dropped my query report again," that is GSC, and SiteLine's import is the fix. If the pain is "I cannot find pageviews," that is analytics install.

A smaller loop

1. Register and enable analytics on the domain.
2. Install the script or React SDK. Absolute data-endpoint / endpoint.
3. Confirm Live. Ignore GA4 real-time while you do this.
4. Send a few custom events you can name in a sentence.
5. Add one goal on /thanks or signup_completed.
6. Connect Search Console on the same domain. Do not compare today's GSC clicks to today's SiteLine pageviews; GSC is ~2 days behind.

When a stakeholder asks for sessions, bounce rate, and engaged sessions, say you do not have those metrics. You have visitors (daily hash), pageviews, and conversion rules. Translating GA4 vocabulary into SiteLine vocabulary is cheaper than turning SiteLine into GA4.

Things SiteLine will not replace

• Google Ads attribution and consent-mode modeling
• Cross-device user stitching
• BigQuery export of a GA4 property
• A consent banner platform (you may still need one for other vendors)
• Multi-member client logins (teams exist in the product codebase; they are off by default — one user per subscription unless SiteLine enables them)

If those are requirements, keep the other tool. Do not wait for SiteLine to grow a "GA4 import."

Ad blockers will still hide some SiteLine events. A first-party proxy reduces that. GA4 has the same class of problem plus gtag.js fame on every blocklist.

FAQ

Will SiteLine numbers match GA4 after a few weeks?

No. Different identity, different bot filters, different consent, different event definitions. Use one tool as the source of truth per question: GSC for search clicks, SiteLine for on-site paths, GA4 for ads if you still run ads.

Do I need to mark events as conversions in code?

No. Send the pageview or named event. Create the goal in the dashboard. Funnels are sequences of the same steps. Neither emits extra billable events.

Is cookieless why GA4 feels more "complete"?

GA4 feels complete because it estimates people. SiteLine refuses that estimate. Completeness and honesty are not the same chart.