updates

docs/account-settings.md

@@ -21,6 +21,11 @@ To open your account settings, click your account name in the top-right menu and
 - [Login management](login-management.md): view and remotely end active sessions
 - [Reset password](reset-password.md): change your account password
 
+**Guest sites**
+
+Shown when you've been invited to sites owned by other teams.
+- [Leave a site you're a guest on](users-roles.md#leaving-a-site-youre-a-guest-on): see the sites you have guest access to and remove yourself from any of them
+
 **Subscription and API keys**
 
 When you're viewing **My personal sites**, your subscription and API keys are managed here. When you've selected a team in the top right menu, they're in [team settings](team-settings.md) instead.

docs/authors.md

@@ -18,6 +18,7 @@ Plausible is built and run by a small, fully remote team. No office, no outside
 * Hricha - Content and community
 * Artur - Product engineer
 * Sanne - Product designer
+* Vini - Product engineer
 
 ## Contributors
 

docs/bot-traffic-filtering.md

@@ -26,7 +26,7 @@ This is a tradeoff of aggressive bot filtering. It keeps automated traffic out o
 
 ## Why you might still see some bot traffic
 
-No filter is perfect. Bots emerge constantly and there is always a gap between when a new bot appears and when we identify and block it. If you see a sudden spike from an unfamiliar source with a very high bounce rate and near-zero visit duration, it may be bot traffic we haven't classified yet. Check time on page, scroll depth and goal conversions for stronger signals.
+No filter is perfect. Bots emerge constantly and there is always a gap between when a new bot appears and when we identify and block it. A visit that shows in your dashboard has already passed these filters: it didn't come from a known data center IP range or match a traffic pattern we exclude. That's why a new kind of automated traffic can be hard to tell apart from real visitors at first. Our filtering is updated continuously as bot traffic evolves, and improvements apply to every site automatically. If you see a sudden spike from an unfamiliar source with a very high bounce rate and near-zero visit duration, it may be bot traffic we haven't classified yet. Check time on page, scroll depth and goal conversions for stronger signals.
 
 ## Investigating a suspicious traffic spike
 

docs/custom-event-goals.md

@@ -15,7 +15,7 @@ Custom events let you measure button clicks, subscription signups or any other a
 - **Using CSS class names**: add a class to any HTML element you want to track. No JavaScript required. This is the easiest approach for most use cases and is covered in the first section below.
 - **Using JavaScript**: call the `plausible()` function directly for more advanced tracking needs such as dynamic values, conditional logic or tracking non-click interactions. See the [manual JavaScript approach](#trigger-custom-events-manually-with-a-javascript-function) section.
 
-If you're using WordPress or Google Tag Manager, you can set up custom events with our [WordPress plugin](wordpress-integration.md#track-custom-events-with-css-class-names) or [GTM template](https://plausible.io/gtm-template) without writing code. Plausible also offers automated tracking for [outbound link clicks](outbound-link-click-tracking.md), [file downloads](file-downloads-tracking.md) and [form submissions](form-submissions-tracking.md) straight from your site settings, [pageview goals](pageview-goals.md) for tracking visits to specific pages and [404 error pages](error-pages-tracking-404.md) with a small snippet of code.
+If you're using WordPress or Google Tag Manager, you can set up custom events with our [WordPress plugin](wordpress-integration.md#track-custom-events-with-css-class-names) or [GTM template](google-tag-manager-integration.md#create-custom-event-tags) without writing code. Plausible also offers automated tracking for [outbound link clicks](outbound-link-click-tracking.md), [file downloads](file-downloads-tracking.md) and [form submissions](form-submissions-tracking.md) straight from your site settings, [pageview goals](pageview-goals.md) for tracking visits to specific pages and [404 error pages](error-pages-tracking-404.md) with a small snippet of code.
 
 <CtaBox
   headline="Testing this workflow for your site? Custom events work during the free trial, no credit card required"
@@ -275,7 +275,7 @@ If you see no request at all, the CSS class name was not added correctly or the
 
 ### GTM events not firing
 
-If you set up custom events through [Google Tag Manager](https://plausible.io/gtm-template), use GTM's built-in **Preview** mode to confirm the tag is firing. Check that your trigger conditions match the actual interaction and that the tag is published, not just saved as a draft.
+If you set up custom events through [Google Tag Manager](google-tag-manager-integration.md), use GTM's built-in **Preview** mode to confirm the tag is firing. Check that your trigger conditions match the actual interaction and that the tag is published, not just saved as a draft.
 
 ### Custom properties showing as (none)
 

docs/ecommerce-revenue-tracking.md

@@ -52,7 +52,7 @@ If you are tracking revenue on an order confirmation page, the revenue amount ne
 
 If you plan to send revenue from your server with the Events API, first read [how server-side events are attributed](events-api.md#how-server-side-events-are-attributed). Payment provider webhooks can't be linked to the visit that led to the payment.
 
-If your site uses Google Tag Manager and already pushes a GA4 `purchase` event, you can send that revenue to Plausible without changing your site. See [our GTM guide](https://plausible.io/gtm-template#reuse-events-from-your-existing-data-layer-optional).
+If your site uses Google Tag Manager and already pushes a GA4 `purchase` event, you can send that revenue to Plausible without changing your site. See [our GTM guide](google-tag-manager-integration.md#example-purchases-with-revenue).
 
 ## How to track ecommerce revenue
 

docs/export-stats.md

@@ -55,7 +55,7 @@ Here's how to export all the native data collected for a particular Plausible da
 
 ### What the export contains
 
-The ZIP file holds one CSV file per report: visitors, sources, pages, entry pages, exit pages, locations, devices, browsers, operating systems, custom events and custom properties. Each file has one row per day for each item, such as one row per page per day with the full page path, so you get a complete list of every page that was visited. The files use the same format as our [CSV import](csv-import.md), so you can import them into another Plausible site.
+The ZIP file holds one CSV file per report: visitors, sources, pages, entry pages, exit pages, locations, devices, browsers, operating systems, custom events and custom properties. Each file has one row per day for each item, such as one row per page per day with the full page path, so you get a complete list of every page that was visited. Visitors are counted per day, so adding them up across days gives a higher number than your dashboard shows for that period. Pageviews and visits can be added up. Scroll depth and time on page are stored as totals with their own visits columns: for a page's average over a period, add up `total_scroll_depth` and divide it by the sum of `total_scroll_depth_visits`. The same goes for `total_time_on_page` (in seconds) and `total_time_on_page_visits`. The files use the same format as our [CSV import](csv-import.md), so you can import them into another Plausible site.
 
 ## Use the stats API
 

docs/file-downloads-tracking.md

@@ -42,8 +42,8 @@ The NPM package doesn't read your site settings. Set `fileDownloads: true` in `i
 
 Click on **File Download** goal in the **Goals** tab of your Plausible dashboard to see the full list of all clicks on all files and have your dashboard filtered by file download clicks only. You can see:
 
-* The number of total file download clicks
-* The number of unique file download clicks
+* The number of total file download clicks (the **Events** column), including repeat clicks by the same visitor
+* The number of unique file download clicks (the **Visitors** column), counting each visitor once
 * The conversion rate
 * Top referral sources that lead to clicks
 * Top pages that drive the clicks

docs/form-submissions-tracking.md

@@ -35,8 +35,8 @@ The NPM package doesn't read your site settings. Set `formSubmissions: true` in
 
 Click on **Form: Submission** goal in the **Goals** tab of your Plausible dashboard to see the full list of all form submissions and have your dashboard filtered by them. You can see:
 
-* The number of total form submissions
-* The number of unique form submissions
+* The number of total form submissions (the **Events** column), including repeat submissions by the same visitor
+* The number of unique form submissions (the **Visitors** column), counting each visitor once
 * The conversion rate
 * Top referral sources that lead to submissions
 * Top pages that drive the submissions