The numbersyour ad blocker stole.

Website analytics is the practice of measuring how visitors interact with a site — what pages they read, where they came from, and which actions they take. Modern analytics combines three streams: client-side events (clicks, form submits, page views), server-side traffic logs (raw requests captured at the edge), and integrations into tools like Google Analytics 4 or PostHog. Ploy ships all three with the website.

Yes — heavily. Studies estimate 20–40% of site visitors run an ad blocker, browser privacy mode, or DNS-level filter that blocks third-party analytics scripts. Those sessions are invisible to client-side tools like Google Analytics 4 or Plausible. Ploy works around this two ways: server-side traffic logs catch every request at the edge regardless of what runs in the browser, and GA4 + PostHog scripts are hosted first-party so they load from your own domain instead of getting blocked at the network layer.

Client-side analytics runs JavaScript in the visitor's browser to record page views and events — fast to set up but invisible whenever an ad blocker, privacy extension, or DNS filter strips the script. Server-side analytics captures requests on the server (or at the edge) before the browser ever runs anything, so every visit is logged regardless of browser state. The two are complementary: client-side captures rich event detail; server-side guarantees completeness.

Ploy can replace Google Analytics for most teams — page views, events, goals, funnels, and traffic sources are all built in, with no SDK install or tag manager. Ploy can also run alongside Google Analytics 4: connect once and Ploy hosts the GA4 script first-party so your existing GA4 property keeps working, with the ad-blocker losses cut. Most teams use both: Ploy for the source-of-truth view and GA4 for reports their leadership already relies on.

Plausible and Fathom are privacy-first client-side analytics — clean dashboards, but they suffer the same 20–40% ad-blocker loss as any client-side tool, and neither offers server-side traffic logs or integrations to keep GA4 and PostHog working. Ploy ships the same lightweight events plus server-side logs that catch what ad blockers eat, hosts GA4 + PostHog first-party, and includes everything in every plan instead of metering on traffic volume.

Yes. Drop the PostHog snippet into your Ploy site and Ploy hosts the script first-party — served from your own domain, so it loads on Brave, on uBlock, on any browser that would normally block a third-party analytics script. Every PostHog capability still works: events, session replay, feature flags, surveys, and PostHog's own A/B tests. The PostHog integration is a hosting layer, not a re-implementation, so the full PostHog feature set stays available.

No. Page views, link clicks, form submits, and goal events instrument themselves on every page Ploy renders — no Google Tag Manager, no Segment, no SDK install, no pixel to maintain. Custom events take a single line of code when you want them. Because Ploy already runs the site, there is no separate analytics deployment to keep in sync when you redeploy.

Page views, link clicks, and form submits track automatically. For everything else, call `trackEvent(name, properties)` once at the moment the event happens — the same syntax across every page on the site. Goal events (signup_clicked, demo_requested, contact_initiated, workspaces_visited) classify themselves based on the destination URL using `trackGoalForHref()`, so most conversion funnels build themselves without any custom code at all.

Yes. Event tracking, goal tracking, server-side traffic logs, first-party GA4 hosting, first-party PostHog hosting, and Ploy-surfaced AI-crawler visibility are all included in every Ploy plan — there is no metered upgrade, no traffic-volume cap, and no enterprise-only tier behind these features.