Skip to content
VisibilityIQ365 VisibilityIQ365 VisibilityIQ Help

Plausible Analytics connector

The Plausible Analytics connector brings privacy-friendly traffic data into VisibilityIQ so you can weight audit findings by real visitor volume — without the consent-banner and ad-blocker suppression that erodes GA4 numbers. If you run Plausible instead of, or alongside, Google Analytics, this connector gives the audit engine the per-page traffic signal it needs to prioritize what matters.

What you’ll need

Section titled “What you’ll need”
  • A Plausible account (Plausible Cloud or a self-hosted Plausible instance) with the site you’re auditing already set up.
  • A Plausible API key with stats access, generated from your Plausible account settings.
  • For self-hosted Plausible, the base URL of your instance so VisibilityIQ knows which endpoint to query.

Why privacy-friendly analytics matters here

Section titled “Why privacy-friendly analytics matters here”

GA4’s traffic numbers are increasingly suppressed by cookie-consent gating, ad blockers, and tracking-prevention features in browsers. For some audiences — privacy-conscious, technical, or EU — a large fraction of real sessions never fire a GA4 event, which understates traffic on exactly the pages those visitors use. Plausible is cookieless and consent-exempt in most jurisdictions, so it counts a higher and more representative share of real visits. For weighting audit findings — where the question is simply “how much does this page matter?” — that fuller count is often the better signal.

Connect

Section titled “Connect”
  1. In Plausible, generate an API key with stats access and copy it.
  2. In your VisibilityIQ project, go to Settings → Connectors.
  3. Click Connect next to Plausible Analytics.
  4. Paste your API key. For self-hosted instances, also enter your Plausible base URL.
  5. Select the Plausible site that matches your project domain.

The API key is stored encrypted and never logged or returned in any response. Plausible data normalizes into the internal TrafficObservation model — the same model GA4 and Search Console feed — so the audit engine treats Plausible traffic identically to any other traffic source when weighting findings.

What’s pulled

Section titled “What’s pulled”
  • Page visits — visitors and pageviews per URL, the core weighting signal.
  • Sources — referrer breakdown, so organic-search traffic can be isolated from direct, social, and referral.
  • Engagement signals — visit duration and bounce rate where Plausible exposes them, used to distinguish pages that draw traffic from pages that hold it.

Plausible does not provide query-level search performance (that’s Search Console) or conversion-revenue attribution in the way an e-commerce GA4 property does. It is a traffic-volume and engagement connector, not a SERP or revenue connector — connect it for accurate visit weighting and pair it with GSC for the search-side picture.

How it changes prioritization

Section titled “How it changes prioritization”

With Plausible connected, a technical finding on a page is promoted or demoted by that page’s real visit volume. Because Plausible undercounts far less than GA4, traffic-weighted prioritization more faithfully reflects which defects sit in front of actual visitors — which is the whole point of weighting in the first place.

Reconnect

Section titled “Reconnect”

If Plausible shows an Error status, the API key was likely revoked or rotated:

  1. Generate a fresh API key in Plausible.
  2. Go to Settings → Connectors, disconnect Plausible, and reconnect with the new key.

Historical data already synced is retained.

Next steps

Section titled “Next steps”