Built-in analytics
Traffic and form conversion numbers for every published PageFork site, with no third-party account and usually no cookie banner.
Every published PageFork site collects its own traffic and conversion numbers. There’s nothing to install, no account to create, and no tracking script to paste — it’s on by default once the site is live.
Open Analytics in the sidebar and pick a site.
What you get
- Pageviews — how many pages were viewed.
- Conversions — form submissions counted as conversions.
- Submits / pageviews — your conversion rate.
- Pageviews by day — the trend over the selected window.
- Top pages — which paths get traffic, and how many submits each produced.
Choose a window of 7, 30, or 90 days.
What counts as a conversion
A form submission. Any form PageFork generated counts automatically, so “views → leads” is meaningful from the first day without configuring a goal.
Conversions attribute to the page the form was on, not the page a visitor lands on afterwards — so a form that redirects to a thank-you page still credits the page that did the work.
What isn’t counted
- Preview traffic. Views inside the editor preview and shared preview links are excluded, so your own work doesn’t inflate the numbers.
- Unpublished sites. Collection starts when a site is live.
If a number looks lower than another tool reports, this is usually why — along with ad blockers, which affect every analytics tool including this one.
Privacy and cookie consent
Built-in analytics is cookieless and first-party: the beacon goes to PageFork, not to a third-party ad network, and no cookie is set to follow visitors between sites.
In practice that puts it in the same category as Plausible or Fathom, which usually do not require a consent banner. PageFork does not turn on the cookie consent modal for built-in analytics alone — it turns it on when you add cookie-setting tools like GA4 or Meta Pixel.
Cookieless is not the same as “no data processing”, though. If you publish a privacy policy, mention that you collect aggregate traffic statistics. If your jurisdiction or your legal advice is stricter than the norm, follow that.
Built-in vs Google Analytics
Built-in analytics answers “is the site getting traffic, and are forms converting?” That’s the question most PageFork sites need answered.
Add GA4 or another tool when you need what it doesn’t do: funnels and multi-step journeys, audience demographics, ad-platform conversion tracking for paid campaigns, cross-domain tracking, or custom event taxonomies.
Running both is fine. Their numbers will never match exactly — different tools filter bots, count sessions, and get blocked differently. Use one as your reference and treat the other as a cross-check.