Traditional analytics tools — Google Analytics 4, Adobe Analytics, and even Matomo in its default setup — write a small text file (a cookie) into every visitor’s browser. That file assigns a unique ID to the device, enabling cross-session tracking. It also triggers the EU’s ePrivacy Directive, GDPR, and the UK’s PECR: storing anything on a visitor’s device requires their prior consent.

Cookie-free analytics removes that step entirely. Session continuity is managed server-side using anonymized signals — hashed IP fragments, browser family, viewport size — that are never stored in identifiable form. Nothing is written to the visitor’s device, so the legal trigger for consent never fires.

Why cookie-free analytics matters for WordPress sites

You recover 40–60% of your traffic data

Studies from Cookiebot and similar consent platforms consistently show that 40–60% of European visitors decline analytics cookies when given a real, equally-prominent choice. That’s nearly half your audience invisible to your dashboards. Cookie-free analytics captures every session — your data reflects reality, not a consent-filtered subset.

Consent banners become simpler — or disappear

If analytics cookies are the only reason your consent banner exists, switching to cookie-free analytics can let you remove the banner entirely. That means fewer friction points at the top of the funnel, faster page loads without the consent script executing, and a cleaner first impression for new visitors.

Your data stays on your server

Third-party analytics platforms receive a copy of your visitors’ behavioral data. Austria’s DSB, France’s CNIL, and Italy’s Garante have each ruled that sending analytics data to US-based servers — even with consent — may violate GDPR’s Chapter V cross-border transfer restrictions. When your analytics data never leaves your server, this entire class of compliance question disappears.

Two legal instruments govern cookies in Europe: GDPR (Regulation 2016/679) and the ePrivacy Directive (2002/58/EC, as amended). Here is how they interact with a properly implemented cookie-free setup:

  • ePrivacy Article 5(3) requires consent before storing or accessing information on a user’s terminal device. Cookie-free analytics stores nothing on the device — no cookie, no localStorage entry, no fingerprint hash — so Article 5(3) is not triggered at all.
  • GDPR Article 6 lawful basis: because IP addresses are immediately hashed and discarded rather than retained, many data protection authorities treat the resulting aggregate data as falling outside GDPR’s personal-data scope entirely.
  • GDPR Recital 26 (“anonymous information”) explicitly states that data protection principles do not apply to information that cannot be attributed to an identified or identifiable natural person.
This is technical guidance, not legal advice. Consent requirements depend on your specific implementation, jurisdiction, and full site configuration. Consult a qualified privacy lawyer before removing your consent banner.

The practical takeaway: replacing GA4 with a server-side, cookie-free plugin like FPAI typically removes the legal trigger for the analytics portion of your consent banner. If analytics were the only reason the banner existed, it may no longer be necessary at all.

How to install FPAI on WordPress — complete step-by-step

FPAI (First Party AI Analytics) is a free WordPress plugin. No external account, no API key, no CDN configuration — it is a single plugin install that starts tracking immediately after activation.

Option A: Install directly from the WordPress admin

Step 1 — Open the plugin installer. In your WordPress dashboard, go to Plugins → Add New Plugin. You will see a search box in the top-right area of the screen.

Step 2 — Search for FPAI. Type FPAI or First Party AI Analytics in the search box and press Enter. The plugin card should appear as the first result, showing the plugin name, a brief description, star rating, and active install count.

Step 3 — Install and activate. Click Install Now on the plugin card. WordPress downloads and unpacks the plugin from the official repository. Once the button label changes to Activate, click it. You will be redirected to the Plugins list with a confirmation notice at the top.

Screenshot tip: after activation, look at your left admin sidebar — “FPAI Analytics” should appear as a new menu item. That confirms the plugin is live.

Option B: Manual zip upload

Step 1 — Download the zip. Visit the FPAI plugin page on WordPress.org and click the Download button to save the .zip file to your computer.

Step 2 — Upload via WordPress admin. Go to Plugins → Add New Plugin → Upload Plugin. Click Choose File, select the downloaded zip, then click Install Now. After the installation completes, click Activate Plugin.

Step 3 — Verify the tracking script is loading

After activation, open your site’s front-end in a browser tab. Press F12 to open DevTools, go to the Network tab, and reload the page. Filter requests by typing fpai in the filter box — you should see fpai-tracker.js returning HTTP 200. If it loads, tracking is live. No manual script injection is needed; FPAI hooks into WordPress’s standard wp_footer action automatically on activation.

Step 4 — Review your first data in the dashboard

Click FPAI Analytics in the left admin sidebar. On first activation the dashboard may read “no data yet” — browse your own front-end a few times or wait for organic traffic. Sessions typically appear within minutes. Logged-in admin users are excluded from tracking by default, so use a private browsing window to generate test sessions.

Step 5 (optional) — Configure exclusions and settings

Navigate to FPAI Analytics → Settings to define: which user roles to exclude, IP ranges to ignore, and URL patterns to skip (e.g. /wp-admin/, staging subdirectories). This is also where you connect an AI provider if you want to use the natural-language query feature.

No cookie notice needed after installing FPAI. The plugin writes zero cookies to the visitor’s browser. If analytics was the only reason your consent banner existed, you can remove it once FPAI is active and you have verified that no other cookie-setting scripts remain on the page.

What FPAI tracks — and what it never stores

FPAI tracks:

  • Page URL and page title
  • Session start time and duration
  • Referrer and traffic source (including UTM parameters)
  • Device type (mobile, desktop, tablet)
  • Browser family
  • Country derived from IP geolocation (the raw IP is never written to the database)
  • Scroll depth, click events, and form submissions
  • Custom conversion events you define in settings

FPAI never stores:

  • Full IP addresses — they are hashed in memory and discarded before any database write
  • Browser cookies of any kind
  • Any personally identifiable information
  • Cross-site tracking data or third-party identifiers

All collected data lives in your WordPress MySQL database under tables prefixed wp_fpai_. Nothing is sent to any external server — no Anthropic cloud, no FPAI SaaS backend, nothing. You can export data as CSV, include it in your normal database backups, or query it directly with SQL.

How to get actionable insights from the FPAI dashboard

Traffic source breakdown

Go to FPAI Analytics → Traffic Sources to see sessions segmented by referrer domain, UTM source and medium, and direct traffic. Because FPAI captures all sessions — including those from visitors who would have declined a GA4 cookie prompt — the numbers are unfiltered and directly comparable to your server access logs.

Page performance by scroll depth

Under Top Pages, sort by average scroll depth to distinguish posts that hold readers’ attention from those with high immediate abandonment. Scroll depth is tracked automatically on every page — no custom event configuration is required.

Conversion tracking

Go to FPAI Analytics → Conversions and define a URL-match rule (e.g. your WooCommerce order-received page) or a named custom event tied to a button click. Conversion rates per traffic source then appear directly in the main dashboard, making it straightforward to compare which acquisition channels actually drive outcomes.

AI-powered natural-language queries

If you have connected an AI provider in settings, type questions directly into the dashboard: “Which referral sources drove the most conversions last month?” or “How has organic traffic trended since I relaunched the homepage?” The AI queries your local MySQL database and returns a plain-English answer — your data never leaves your hosting environment.

FPAI vs Plausible vs Matomo — at a glance

Several privacy-friendly analytics options exist for WordPress. Here is how FPAI compares to the two most widely used alternatives:

  • Data hosting — FPAI: your WordPress database  |  Plausible (cloud): EU-based SaaS servers  |  Matomo: self-hosted or cloud
  • Cookie-free by default — FPAI: yes  |  Plausible: yes  |  Matomo: no — requires deliberate configuration; cookies are on by default
  • Consent banner needed for analytics — FPAI: no  |  Plausible: no  |  Matomo: depends on configuration
  • WordPress integration — FPAI: native single plugin, zero external dependency  |  Plausible: third-party WP plugin  |  Matomo: official plugin, significantly heavier setup
  • AI-powered queries — FPAI: built-in, connects to any provider  |  Plausible: not available  |  Matomo: not available
  • Cost for analytics core — FPAI: free  |  Plausible (cloud): from $9/month  |  Matomo (self-hosted): free

For most WordPress site owners the decisive factors are: FPAI requires no external accounts, no monthly fees, and keeps all data inside the database infrastructure you already manage. Plausible is excellent if you prefer a managed SaaS product and are comfortable with the subscription cost. Matomo self-hosted is the most feature-complete option but demands considerably more configuration effort to achieve cookie-free compliance.

Frequently asked questions

Does FPAI slow down my WordPress site?

The tracking script loads asynchronously via wp_footer, meaning it does not block page rendering or affect Core Web Vitals. The database writes occur server-side after the page has been delivered to the browser. In practice, FPAI adds no perceptible load time for visitors.

Will my analytics data survive a WordPress migration?

Yes. FPAI stores everything in standard MySQL tables (wp_fpai_*). Any normal database migration — cPanel backup, WP Migrate DB, a manual mysqldump — will include your FPAI data. Export, import, and your full analytics history arrives intact on the new host.

Can I run FPAI alongside Google Analytics during a transition?

Yes. Both can run simultaneously. A common approach is to activate FPAI while keeping GA4 live for four to eight weeks, allowing FPAI to accumulate enough data to be useful before you deprovision the GA4 tag and simplify or remove the consent banner.

Does FPAI work with caching plugins like WP Rocket or LiteSpeed Cache?

Yes. Because the tracking script executes client-side in the browser, full-page caching at the server level does not interfere with data collection. Every visitor’s browser runs the script regardless of whether the HTML was served from cache.

What happens to my data if I deactivate the plugin?

The FPAI database tables remain intact when you deactivate — your historical data is preserved. Only a full plugin deletion with “delete data on uninstall” enabled in settings will remove the tables. You can safely deactivate and reactivate without losing any analytics history.

Is FPAI compatible with WooCommerce?

Yes. FPAI tracks click events and page views across WooCommerce product pages, cart, checkout, and order-confirmation URLs out of the box. You can define the order-confirmation URL as a conversion goal to track purchase completion rates by traffic source without any additional code.

FPAI – First Party AI Analytics is a free WordPress plugin for complete, cookie-free analytics. No external account required, no monthly fee, and your data never leaves your server. Download FPAI from WordPress.org and have privacy-first analytics running on your site in under five minutes.