Website Analytics with Server-Side Tracking | Ploy

The numbers your ad blocker stole.

Built-in website analytics for sites built on Ploy. Track every event client-side, capture what ad blockers eat with server-side traffic logs, and host GA4 + PostHog first-party so they actually load — no SDK, no tag manager.

Inside Insights

Know who your site is working on.

Traffic, identified companies, engagement, and account rollups — the numbers that tell you what your site is doing and which accounts to act on next.

Overview Last 7 days

Pageviews & Visitors

By industry

Engagement Last 7 days

Conversion funnel

Top actions

Accounts Last 7 days

Most engaged accounts Engagement rolled up by company · identified visitors

Analytics that ships with the site. Plus the stack you already have.

Four streams running on the same surface. No tag manager, no Segment, no SDK install — and no separate analytics deployment to keep in sync with your site.

01 Track.

Every page view, every CTA click, every form submit captured automatically. No SDK to install, no tag manager to configure, no pixel that breaks on redeploy.

02 Goals.

Signup clicks, demo requests, contact submits, login clicks — classified as goals automatically based on where each link points. Conversion funnels build themselves.

03 Server logs.

Edge-level request logs catch the 20–40% of sessions ad blockers eat. Ploy reads the user agents and tells you when Googlebot, GPTBot, PerplexityBot, or ClaudeBot crawled.

04 Host GA4 + PostHog.

Drop in GA4 or PostHog and Ploy serves the scripts from your own domain. They actually load — on Brave, on uBlock, on every browser that would normally block them.

Analytics, defined

What is website analytics?

Website analytics is the practice of measuring how visitors interact with a website — what pages they read, where they came from, and which actions they take. Modern analytics combines client-side events with server-side website analytics, which captures raw requests at the edge, plus first-party analytics integrations for tools like Google Analytics 4 or PostHog. Ploy ships all three with the website instead of bolting them on as separate vendors.

Events

Client-side events

Page views, link clicks, form submits, and custom events captured in the browser. Fast, rich, and easy to instrument — but lost the moment an ad blocker, privacy extension, or DNS filter strips the script.

Logs

Server-side traffic logs

Every request hitting the site is logged at the edge before the browser runs anything. Catches the 20–40% of sessions ad blockers eat, plus every bot, crawler, and AI agent — Googlebot, GPTBot, PerplexityBot, ClaudeBot.

Goals

Goals and conversions

Signup clicks, demo requests, contact submits, login clicks — classified as goals automatically based on where each link points. The conversion funnel builds itself without manual instrumentation in a tag manager.

First-party

First-party integrations

Google Analytics 4 and PostHog hosted first-party from your own domain. Existing GA4 properties and PostHog projects keep working — with the ad-blocker losses cut and no separate proxy server to maintain.

Events & goal tracking

If it happens on your site, it's an event.

Page views, link clicks, form submits, and CTA interactions instrument themselves on every page. Goal events — signup_clicked, demo_requested, contact_initiated, workspaces_visited — classify themselves based on where each link points.

Auto-instrumented

Page views, link clicks, and form submits track themselves — no install.

Goals self-classify

goal_* events are classified automatically for the conversions that matter.

Custom events in one line

Add a custom event in one line — same syntax across every page.

No tag manager

Filter, group, and chart events without touching a tag manager.

Server-side traffic logs

Client-side analytics is half a picture.

Studies estimate 20–40% of site visitors run an ad blocker, privacy extension, or DNS filter — every one of them invisible to client-side analytics. Edge-level request logs capture every visit anyway, plus every bot and AI agent reading your pages for citations.

Logged at the edge

Every request is logged at the edge — ad blockers can't strip the server.

AI crawler detection

Ploy reads user agents and surfaces when GPTBot, PerplexityBot, or ClaudeBot crawled.

Slice any way

By status, response time, country, or referer — without a logging stack.

AEO debugging

See which AI engines actually read each page.

First-party GA4 + PostHog

Your analytics scripts. Loaded from your own domain.

Ad blockers don't block scripts because of what they do — they block them based on where they load from. Ploy hosts your GA4 and PostHog scripts first-party, served from your own domain, so they load on Brave, on uBlock, on every browser that would normally kill them.

GA4, first-party

Your existing property, reports, and explorations keep working.

PostHog, first-party

Events, session replay, feature flags, surveys, and A/B tests.

Nothing to maintain

No Segment, no GTM, no proxy server to run.

Per-environment toggle

Switch either script on per environment in one click.

For growth teams

See your real traffic numbers in 60 seconds.

Paste your existing site URL into Ploy. We'll show you what your client-side analytics misses — for free, before you decide to migrate anything.

Frequently asked

What is website analytics?

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.

Do ad blockers affect website analytics?

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.

What's the difference between client-side and server-side analytics?

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.

Is Ploy a Google Analytics alternative?

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.

How does Ploy compare to Plausible or Fathom?

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.

Can I keep using PostHog with Ploy?

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.

Does Ploy require a tag manager or SDK?

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.