plausible · metmarkosaric · May 18, 2026 · May 18, 2026
diff --git a/docs/data-access.md b/docs/data-access.md
@@ -110,9 +110,9 @@ For cases where aggregated stats are not enough, Plausible offers scheduled raw
 - You need event-level data for data warehousing, internal analytics or compliance reporting
 - Aggregated stats from the CSV export or Stats API do not meet your needs
 
-Raw event exports are not self-serve and are not real-time. [Contact us](https://plausible.io/contact) to discuss your needs.
+Raw event exports are not self-serve and are not real-time. They are part of our [Enterprise plans](https://plausible.io/enterprise-web-analytics). [Contact us](https://plausible.io/contact) to discuss your needs.
 
-[Export your stats](export-stats.md)
+[Scheduled raw event exports](raw-data-export.md)
 
 ---
 

diff --git a/docs/export-stats.md b/docs/export-stats.md
@@ -42,14 +42,6 @@ As an alternative to exporting as CSV files or if you prefer a programmatic way
 
 ## Scheduled raw event data exports
 
-If you need access to event level data, we offer scheduled raw event data exports for Enterprise customers.
+If you need event-level data rather than aggregated stats, Plausible offers scheduled raw event exports as part of our [Enterprise plans](https://plausible.io/enterprise-web-analytics). These cover advanced use cases such as data warehousing, internal analytics and compliance reporting.
 
-This option complements our self serve export options and APIs and is intended for advanced use cases such as data warehousing, internal analytics or compliance reporting.
-
-Scheduled raw event exports are configured with our team. We agree on the event data fields and schema, the export format, the delivery interval such as daily or weekly and the secure delivery method.
-
-Once set up, the exports are delivered automatically on the agreed schedule.
-
-Scheduled raw event exports are not self serve and are not real time. They are intentionally scoped to keep Plausible fast, privacy friendly and predictable. This is part of our [Enterprise offerings](https://plausible.io/enterprise-web-analytics), please [contact us](https://plausible.io/contact) to discuss your needs.
-
-If you only need aggregated data, occasional exports or self serve access, our standard export options as listed above are usually the best option.
+[See full details, use cases and how to get started →](raw-data-export.md)
diff --git a/docs/proxy/introduction.md b/docs/proxy/introduction.md
@@ -1,81 +1,56 @@
 ---
-title: Adblockers and using a proxy for analytics
-description: "Why some adblockers block Plausible and how to use a proxy to serve analytics as a first-party connection from your own domain to avoid being blocked."
+title: Bypass adblockers with a proxy
+description: "Some adblockers block Plausible. A proxy routes analytics through your own domain to capture those visits. Choose between one-click, self-setup and managed options."
 ---
 
-A frequently asked question we get is, "why do adblockers block Plausible?". It's assumed that by being privacy-first, we would not be placed in the same category as Google Analytics, Facebook Pixel, or other _surveillance capitalism_ tools.
+Some visitors use adblockers or privacy tools that block analytics scripts. Plausible is blocked far less than Google Analytics. Firefox and Safari do not block it by default, but some blocklist maintainers block all analytics regardless of privacy practices.
 
-It's a good question. We're not blocked to the same extent as Google Analytics (neither Firefox nor Safari blocks Plausible), but we're blocked by some blocklist maintainers who have taken the stance that they want to block every tracking script and don't want to have the responsibility to judge what's good and what's bad.
+A proxy routes the Plausible script through your own domain as a first-party request, making it indistinguishable from your own files. This bypasses most blockers and lets you count visits that would otherwise be missed.
 
-We have great respect for open source contributors and blocklist maintainers who usually offer their free time and coding skills to do something for the common good. We believe we're on the same side and have started a dialogue hoping that they will have a change of heart.
+## Which option fits you
 
-## Giving site owners a choice
+### No proxy (default)
 
-Site owners feel unfairly targeted and an innocent casualty of this arms race between blocklist maintainers and the adtech industry. Site owners want some data to figure out what's going on and learn what they can do to improve. It's unfortunate for them to lose valuable, privacy-friendly insights that help them create a better user experience.
+Run the default script from plausible.io. This is the simplest setup and works well for most sites. Expect some visitors with strict blockers to be missed, typically between 5% and 25% depending on your audience.
 
-Plausible isn't tracking people in the way that Google Analytics is, so it's important not to confuse the two. We've put a lot of effort into giving site owners some actionable data in a [privacy-friendly way](https://plausible.io/privacy-focused-web-analytics). Plausible is simply doing web analytics the way it was at the start before surveillance capitalism became the default business model of the web:
+**Use this when:** accuracy gaps from adblockers are acceptable for your use case.
 
-* No cookies and other persistent identifiers.
-* No connection to the adtech, and surveillance capitalism.
-* No personal data is collected, and all stats are in aggregate only.
-* No cross-site or cross-device tracking.
-* You 100% own your website data, and it isn't sent to, shared with or sold to any third-parties.
-* Open source web analytics software that can be self-hosted.
-* You can see [how the dashboard looks](https://plausible.io/plausible.io).
+[Script installation →](../plausible-script.md)
 
-## Options for dealing with missing data as a site owner
-
-This section has been introduced after hearing from so many site owners who expect privacy-first analytics not to be blocked. We wanted to give a choice to people that use Plausible Analytics.
-
-### Not concerned about missing data?
-
-Simply run our default script. The easiest way to get started with Plausible Analytics is to [install the script](/docs/plausible-script.md) from our main domain.
+---
 
-This is the simplest way to install Plausible Analytics but it will also be blocked by a portion of your visitors. In [our testing](https://markosaric.com/google-analytics-blocking/), between 6% and 26% of people block scripts all depending on the type of the site and the audience. In more extreme cases, with very tech-savvy referral sources these numbers can get [up to 60%](https://plausible.io/blog/google-analytics-adblockers-missing-data).
+### WordPress one-click proxy
 
-### Are you concerned about missing data?
+The official WordPress plugin includes a built-in proxy you can enable with a single toggle in your plugin settings. No CNAME records, no server configuration, no maintenance.
 
-Proxy our script. This is the option for those who want to get more accurate stats. A proxy basically maps certain URLs from your domain to the Plausible domain:
+**Use this when:** your site runs on WordPress.
 
-```
-https://<yourdomain.com>/js/script.js -> https://plausible.io/js/pa-XXXX.js
-https://<yourdomain.com>/api/event    -> https://plausible.io/api/event
-```
+[WordPress plugin →](../wordpress-integration.md)
 
-When the browser requests a file at `https://yourdomain.com/js/script.js` it will actually be fetched from `https://plausible.io/js/pa-XXXXX.js`. The analytics will work exactly the same but the script will be served without being flagged.
+---
 
-In this case, `/js/pa-XXXXX.js` is the script location specific for your site. You can find it in the **Site Installation** area of the **General** section in your [site settings](website-settings.md).
+### Self-setup proxy
 
-:::tip Using WordPress?
-The quickest way to enable a proxy is to use our [official WordPress plugin](https://plausible.io/wordpress-analytics-plugin)
-:::
+Route requests through your own infrastructure using a Cloudflare Worker, Vercel rewrite, Netlify redirect or reverse proxy. Requires developer access but is free and gives you full control.
 
-## How to proxy requests to Plausible
+**Use this when:** you are not on WordPress, have developer access, and want to manage the proxy yourself.
 
-You can proxy requests to Plausible in several ways depending on your setup. If you'd rather not handle it yourself, we also offer a managed proxy option.
+Guides: [Cloudflare](guides/cloudflare.md) · [Vercel](guides/vercel.md) · [Netlify](guides/netlify.md) · [Nginx](guides/nginx.md) · [Apache](guides/apache.md) · [Caddy](guides/caddy.md) · [Laravel](guides/laravel.md)
 
-### Managed proxy
+---
 
-Don't want to manage your own proxy? We can handle it for you. Our managed proxy lets you send analytics through your own domain name as a first-party connection. This helps bypass adblockers and count more traffic without any setup or maintenance on your end.
+### Managed proxy (Enterprise)
 
-All you need to do is set up a CNAME record using the instructions we'll send you and update the snippet on your site. We'll take care of everything else.
+We handle the proxy for you. You set up a CNAME record pointing to our infrastructure, update the snippet on your site, and we take care of everything else. No ongoing maintenance on your end.
 
-Managed proxy is available on our [Enterprise plans](https://plausible.io/enterprise-web-analytics). [Contact us for details](https://plausible.io/contact).
+**Use this when:** you are not on WordPress and want the proxy without managing it yourself, or your infrastructure makes self-setup impractical.
 
-### A note on visitor IP addresses
+Available on [Enterprise plans](https://plausible.io/enterprise-web-analytics). [Contact us to discuss →](https://plausible.io/contact)
 
-When your proxy forwards events to Plausible, the request must include the visitor's real IP address in the `X-Forwarded-For` header. If this header is missing or contains a server, CDN, or hosting provider IP instead, Plausible's bot filtering will drop the event. The API returns HTTP 202 either way, so there is no obvious error.
+---
 
-Most CDN-level proxies (such as Cloudflare Workers or Vercel rewrites) handle this automatically. If you are writing your own proxy function, you need to set the header explicitly. See the [Events API reference](/docs/events-api#request-headers) for details and instructions on how to check whether events are being dropped.
+## A note on IP forwarding
 
-### Manual proxy
+When your proxy forwards requests to Plausible, the real visitor IP must be passed in the `X-Forwarded-For` header. If this header is missing or contains your server's IP instead of the visitor's, Plausible's bot filter will drop the event silently. The API returns HTTP 202 either way.
 
-* [Cloudflare](/docs/proxy/guides/cloudflare)
-* [Vercel](/docs/proxy/guides/vercel)
-* [Netlify](/docs/proxy/guides/netlify)
-* [Fresh](/docs/proxy/guides/fresh)
-* [Nginx](/docs/proxy/guides/nginx)
-* [Apache](/docs/proxy/guides/apache)
-* [Caddy](/docs/proxy/guides/caddy)
-* [Laravel](/docs/proxy/guides/laravel)
-* [Send events directly to our API](/docs/events-api)
+Most CDN-level proxies such as Cloudflare Workers or Vercel rewrites handle this automatically. If you are writing a custom proxy function, set the header explicitly. See the [Events API reference](../events-api.md#request-headers) for how to verify which IP Plausible is receiving.
diff --git a/docs/raw-data-export.md b/docs/raw-data-export.md
@@ -0,0 +1,40 @@
+---
+displayed_sidebar: someSidebar
+title: Scheduled raw event exports
+description: "Get event-level data from Plausible delivered automatically on a schedule. For data warehousing, compliance and internal analytics where aggregated stats are not enough."
+---
+
+The Stats API and CSV export give you aggregated data: totals, breakdowns and time series across your sites. For cases where you need the underlying event-level data, Plausible offers scheduled raw event exports.
+
+## What it is
+
+A scheduled raw export delivers event-level data from your Plausible account automatically, on an agreed schedule. Setup is configured with our team: we agree on the event data fields and schema, the export format (CSV or Parquet), the delivery interval (daily, weekly or other) and the delivery destination. We support uploading directly to your S3 bucket or Google Cloud Storage bucket. Once configured, exports are delivered automatically with no action needed on your end.
+
+Unlike the Stats API, which returns pre-aggregated results, raw exports give you individual event records. This lets you run your own aggregations, apply custom attribution models, join analytics data with other business data, and meet compliance requirements that call for event-level audit trails.
+
+Raw exports are intentionally scoped to keep Plausible fast, privacy-friendly and predictable. They are not real-time and not self-serve.
+
+## When to use it
+
+Raw exports are the right choice when:
+
+- You need to load event-level analytics data into a warehouse such as BigQuery, Snowflake or Redshift and the [community connectors](data-pipelines.md) do not meet your needs
+- You need individual event records for compliance, auditing or internal reporting
+- You want to run custom aggregations or attribution models that the Stats API cannot express
+- You are building internal analytics tooling that requires raw event data as input
+
+## When alternatives are enough
+
+Before requesting raw exports, check whether a simpler option covers your needs:
+
+| Need | Better option |
+|---|---|
+| Query stats programmatically | [Stats API](stats-api.md) |
+| Build a custom dashboard or embed stats | [Stats API](stats-api.md) |
+| Download data for a spreadsheet | [CSV export](export-stats.md) |
+| Visualize in Google's tools | [Looker Studio](looker-studio.md) |
+| Pipe aggregated stats into a warehouse | [Airbyte or Fivetran connectors](data-pipelines.md) |
+
+## How to get it
+
+Raw event exports are part of our [Enterprise plans](https://plausible.io/enterprise-web-analytics) and are not self-serve. [Contact us](https://plausible.io/contact) to discuss your data volume, delivery schedule and format requirements.
diff --git a/docs/subscription-plans.md b/docs/subscription-plans.md
@@ -34,6 +34,27 @@ Compare full features and pricing on [our website](https://plausible.io/#pricing
 
 Nonprofits, educational institutions and open-source projects are eligible for a 15% discount on Business plans with annual billing. See [nonprofit and education pricing](nonprofit-and-education-pricing.md) for details.
 
+## Enterprise-only features
+
+Enterprise includes everything in Business plus a set of additional features and higher limits. The features below are not available on any lower plan and cannot be purchased as add-ons.
+
+- **SSO (Single Sign-On)**: log in via your existing identity provider using SAML 2.0. See [SSO documentation](sso.md).
+- **Sites API**: create and manage sites programmatically. See [Sites API documentation](sites-api.md).
+- **Managed proxy**: we handle the proxy setup and maintenance for you. See [proxy options](proxy/introduction.md).
+- **Scheduled raw event exports**: event-level data delivered automatically on an agreed schedule. See [raw event exports](raw-data-export.md).
+
+If you are on Growth and need SSO, for example, an upgrade to Enterprise is required. There is no add-on option.
+
+Limits that can be increased on Enterprise beyond standard plan tiers:
+
+- Monthly pageview volume
+- Number of sites
+- Number of team members
+- API rate limits
+- Data retention
+
+[Learn more about Enterprise plans](https://plausible.io/enterprise-web-analytics) or [contact us](https://plausible.io/contact) to discuss your needs.
+
 ## Traffic spikes and overages
 
 You will never be charged extra for an occasional traffic spike. No surprise fees, no stats interruption, no unexpected charges.

diff --git a/sidebars.js b/sidebars.js
@@ -96,6 +96,7 @@ module.exports = {
       'events-api',
       'sites-api',
       'export-stats',
+      'raw-data-export',
       'looker-studio',
       'data-pipelines',
     ],