From 0a3419907bfc59477bcd2be94069967171ec18af Mon Sep 17 00:00:00 2001
From: Marko Saric <marko@plausible.io>
Date: Wed, 20 May 2026 11:02:20 +0200
Subject: [PATCH] what's next

---
 docs/bot-traffic-filtering.md                  |  2 +-
 docs/carrd-integration.md                      |  6 ++++++
 docs/community-integrations.md                 |  7 -------
 docs/custom-domain.md                          | 11 -----------
 docs/custom-event-goals.md                     |  7 +++++++
 docs/custom-pageview-props.md                  |  7 -------
 docs/discourse-integration.md                  |  6 ++++++
 docs/excluding-pages.md                        |  9 ---------
 docs/filters-segments.md                       |  7 +++++++
 docs/ghost-integration.md                      |  6 ++++++
 docs/google-analytics-import.md                |  7 +++++++
 docs/google-search-console-integration.md      |  6 ++++++
 docs/google-tag-manager.md                     |  9 ---------
 docs/hubspot-analytics.md                      |  6 ++++++
 docs/integration-guides.md                     |  2 +-
 docs/internal-link-click-tracking.md           |  9 ---------
 docs/javascript-snippet.md                     |  9 ---------
 docs/plausible-analytics-self-hosted-guides.md |  9 ---------
 docs/plausible-script.md                       |  7 +++++++
 docs/script-extensions-for-wp-plugin.md        |  9 ---------
 docs/self-hosting-configuration.md             |  9 ---------
 docs/self-hosting.md                           |  9 ---------
 docs/shopify-integration-deprecated.md         |  9 ---------
 docs/shopify-integration.md                    |  7 +++++++
 docs/squarespace-integration.md                |  6 ++++++
 docs/trial-to-paid.md                          |  7 +++++++
 docs/twitter.md                                |  7 -------
 docs/verify-integration.md                     |  9 ---------
 docs/webflow-integration.md                    |  7 +++++++
 docs/wix-integration.md                        |  6 ++++++
 docs/wordpress-integration.md                  |  6 ++++++
 docusaurus.config.js                           |  3 ++-
 src/theme/Footer/index.js                      |  4 ++--
 33 files changed, 103 insertions(+), 127 deletions(-)
 delete mode 100644 docs/community-integrations.md
 delete mode 100644 docs/custom-domain.md
 delete mode 100644 docs/custom-pageview-props.md
 delete mode 100644 docs/excluding-pages.md
 delete mode 100644 docs/google-tag-manager.md
 delete mode 100644 docs/internal-link-click-tracking.md
 delete mode 100644 docs/javascript-snippet.md
 delete mode 100644 docs/plausible-analytics-self-hosted-guides.md
 delete mode 100644 docs/script-extensions-for-wp-plugin.md
 delete mode 100644 docs/self-hosting-configuration.md
 delete mode 100644 docs/self-hosting.md
 delete mode 100644 docs/shopify-integration-deprecated.md
 delete mode 100644 docs/twitter.md
 delete mode 100644 docs/verify-integration.md

diff --git a/docs/bot-traffic-filtering.md b/docs/bot-traffic-filtering.md
index cf84597e..15551479 100644
--- a/docs/bot-traffic-filtering.md
+++ b/docs/bot-traffic-filtering.md
@@ -55,7 +55,7 @@ Once you have identified the source, use [Shields](excluding.md) to stop it bein
 - **By country**: if the traffic is concentrated in one country you don't operate in, block that country
 - **By hostname**: if a specific hostname or referrer domain is the source, block it
 - **By IP address**: if the traffic is coming from a known IP or range, block that IP
-- **By page**: if only specific pages are being hit, use [page exclusions](excluding-pages.md)
+- **By page**: if only specific pages are being hit, use [page exclusions](top-pages.md#block-traffic-from-specific-pages-or-sections)
 
 Shields rules take effect immediately and apply going forward. They do not remove historical data already recorded.
 
diff --git a/docs/carrd-integration.md b/docs/carrd-integration.md
index 2296feef..b34256ce 100644
--- a/docs/carrd-integration.md
+++ b/docs/carrd-integration.md
@@ -134,3 +134,9 @@ If you want to trigger multiple custom events on the same site, you don't need t
 ```
 
 <img alt="track multiple elements in Carrd" src={useBaseUrl('img/track-multiple-elements-carrd.png')} />
+
+## What's next?
+
+- [Create goals](custom-event-goals.md) in your Plausible site settings to match the custom events you set up. They won't appear in your dashboard until you do
+- [Verify the integration is working](troubleshoot-integration.md) to confirm events are firing correctly
+- [Filter your dashboard by goal](filters-segments.md) to see which sources are driving the most conversions
diff --git a/docs/community-integrations.md b/docs/community-integrations.md
deleted file mode 100644
index d28fd421..00000000
--- a/docs/community-integrations.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: Community integrations
-description: "Browse community-built integrations for Plausible Analytics. Third-party plugins and connectors for frameworks and platforms not covered by official guides."
----
-
-[Full list of community integrations and other guides is here](integration-guides.md).
diff --git a/docs/custom-domain.md b/docs/custom-domain.md
deleted file mode 100644
index d61e6dbb..00000000
--- a/docs/custom-domain.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: Serve the script from your domain as a first-party connection
-description: "Older approach to serving the Plausible script from your own domain. We now recommend using the proxy instead. See proxy setup instructions."
----
-
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-:::note
-We now recommend the proxy instead of the custom domain. [Here are the proxy instructions](/proxy/introduction.md)
-:::
diff --git a/docs/custom-event-goals.md b/docs/custom-event-goals.md
index 3e506b7b..99a4f0a7 100644
--- a/docs/custom-event-goals.md
+++ b/docs/custom-event-goals.md
@@ -362,3 +362,10 @@ Example: Tracking audio and video elements
 The same code also applies for `<video>` elements. Feel free to replace `Media Played` with a more suitable name for your custom event.
 
 </details>
+
+## What's next?
+
+- [Attach custom properties](/custom-props/for-custom-events) to your events to track additional context like plan type, product name or coupon code alongside conversions
+- [Add revenue values](ecommerce-revenue-tracking.md) to purchase or checkout events to track ecommerce revenue attribution
+- [Build a funnel](funnel-analysis.md) using your custom events as steps to see where visitors drop off between landing and converting
+- [Filter your dashboard by goal](filters-segments.md) to see which sources and pages drive the most conversions for each event
diff --git a/docs/custom-pageview-props.md b/docs/custom-pageview-props.md
deleted file mode 100644
index 8ae21ab7..00000000
--- a/docs/custom-pageview-props.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: Custom properties for pageviews
-description: "Documentation for custom properties in Plausible has moved. Find the updated guide on attaching and using custom properties with your pageviews and events."
----
-
-Our custom properties documentation has been moved to [this page](/custom-props/introduction.md).
diff --git a/docs/discourse-integration.md b/docs/discourse-integration.md
index 24e5d251..380e368a 100644
--- a/docs/discourse-integration.md
+++ b/docs/discourse-integration.md
@@ -31,3 +31,9 @@ We display your snippet during the process of adding a new site to your account.
 Discourse will automatically add a nonce to the script to satisfy the Content Security Policy headers so no further action is necessary for that.
 
 Now you can go to your Discourse community and verify whether Plausible Analytics script has been added and to your Plausible Analytics account to see whether the stats are being tracked. See here [how to verify the integration](troubleshoot-integration.md).
+
+## What's next?
+
+- [Set up goals](goal-conversions.md) to track key actions on your forum such as new topic creation or sign-ups
+- [Invite your team](users-roles.md) so moderators and community managers can access the stats directly
+- [Create a shared link](shared-links.md) for read-only dashboard access without requiring a Plausible account
diff --git a/docs/excluding-pages.md b/docs/excluding-pages.md
deleted file mode 100644
index 0d43af71..00000000
--- a/docs/excluding-pages.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: Exclude specific pages from being tracked
-description: "Stop Plausible from recording traffic on specific pages or sections of your site by configuring page exclusions in your site settings."
----
-
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-You can exclude traffic on specific pages or sections of your site from being recorded in your dashboard in the site settings. [See more here](top-pages.md#block-traffic-from-specific-pages-or-sections).
diff --git a/docs/filters-segments.md b/docs/filters-segments.md
index 4568f232..cef9d3c7 100644
--- a/docs/filters-segments.md
+++ b/docs/filters-segments.md
@@ -92,3 +92,10 @@ Open a previously saved segment and click its name in the top line of your Plaus
 To save your changes, click the **Update segment** button. Use the arrow next to this button to save the existing segment as a brand new segment (**Save as a new segment**) or to delete the existing segment (**Delete segment**).
 
 P.S. We've written an in-depth guide on effective use of audience segmentation, you can [read it here](https://plausible.io/audience-segmentation).
+
+## What's next?
+
+- [Set up goals](goal-conversions.md) so you can filter your dashboard by conversion and see which sources and campaigns drive the most signups or purchases
+- [Compare two time periods](compare-stats.md) alongside your segment filters to understand how a specific audience's behavior has changed over time
+- [Export filtered stats](export-stats.md) to CSV to share a specific segment's data outside the dashboard
+- [Create a shared link](shared-links.md) pre-filtered to a specific segment for stakeholders who only need to see part of your data
diff --git a/docs/ghost-integration.md b/docs/ghost-integration.md
index e77b1e00..45728918 100644
--- a/docs/ghost-integration.md
+++ b/docs/ghost-integration.md
@@ -29,3 +29,9 @@ The Sign In/Sign up flows are part of Ghost's [Portal](https://ghost.org/help/se
 However, you can bypass this and customize your sign up flows by using a custom theme on the "[Creator plan](https://ghost.org/pricing/)" or higher. 
 
 If you're using a custom theme, you can simply add the tagged events extension to your script and CSS class to the element that you want to track as explained in [this doc](https://plausible.io/docs/custom-event-goals).
+
+## What's next?
+
+- [Verify the integration](troubleshoot-integration.md) to confirm the snippet is firing and stats are being collected
+- [Set up a pageview goal](pageview-goals.md) for your newsletter signup confirmation page to track how many visitors become subscribers
+- [Invite your team](users-roles.md) or [create a shared link](shared-links.md) for collaborators who need read access to your stats
diff --git a/docs/google-analytics-import.md b/docs/google-analytics-import.md
index d9d095cf..230272cf 100644
--- a/docs/google-analytics-import.md
+++ b/docs/google-analytics-import.md
@@ -207,3 +207,10 @@ Check the date range of your import in your Plausible site settings. If your GA4
 **Imported data and native data show a gap or overlap**
 
 The import tool sets the end date of the import to one day before your first Plausible native data point. If you see a gap, check that Plausible was correctly installed and recording data before you ran the import. If you see overlap, delete the import and re-run it after confirming your Plausible installation date.
+
+## What's next?
+
+- [Set up goals in Plausible](goal-conversions.md) to replace the GA4 conversions you were tracking. Imported goal data will appear once you recreate matching goals in your site settings
+- [Compare date ranges](compare-stats.md) that span your imported history and your native Plausible data together
+- [Filter and segment](filters-segments.md) your imported data by source, page or country to reproduce the key reports you used in GA4
+- [Export to CSV](export-stats.md) or use the [Stats API](stats-api.md) for reporting outside the dashboard
diff --git a/docs/google-search-console-integration.md b/docs/google-search-console-integration.md
index 0f6d05e9..de12da3b 100644
--- a/docs/google-search-console-integration.md
+++ b/docs/google-search-console-integration.md
@@ -117,3 +117,9 @@ You can check if Plausible Analytics is integrated with and has the right permis
 If you'd like to remove the Google Search Console integration, click on the **Unlink Google account** button in the **Google Search Console Integration** module within the **Integrations** section of your website settings.
 
 P.S. If you want to learn more about analyzing organic search traffic in Plausible, visit our [blog post](https://plausible.io/blog/seo-dead#analyzing-organic-search-traffic).
+
+## What's next?
+
+- [Set up goals](goal-conversions.md) so you can see which search keywords and landing pages drive the most signups or purchases
+- [Use filters and segments](filters-segments.md) to isolate your organic search audience and see their full behavior across your site
+- [Compare two time periods](compare-stats.md) to track how your search traffic has changed since your last content or SEO update
diff --git a/docs/google-tag-manager.md b/docs/google-tag-manager.md
deleted file mode 100644
index 176f8a5c..00000000
--- a/docs/google-tag-manager.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: How to add the script to your site using Google Tag Manager
-description: "Deploy Plausible Analytics via Google Tag Manager using the official GTM template. No manual code editing required."
----
-
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-We have published a template that makes setting up Plausible Analytics with Google Tag Manager simple. For more details on the Plausible Analytics Google Tag Manager template, please [see our guide](https://plausible.io/gtm-template). 
diff --git a/docs/hubspot-analytics.md b/docs/hubspot-analytics.md
index b61ee813..f61ed07f 100644
--- a/docs/hubspot-analytics.md
+++ b/docs/hubspot-analytics.md
@@ -23,3 +23,9 @@ In HubSpot you can inject code across your entire site or on an individual post
 * After adding your code, click on the **Save** button.
 
 Now you can go to your website and verify whether Plausible Analytics script has been added and to your Plausible Analytics account to see whether the stats are being tracked. See here [how to verify the integration](troubleshoot-integration.md).
+
+## What's next?
+
+- [Set up pageview goals](pageview-goals.md) for your thank-you pages to track form submission conversions without writing any code
+- [Set up custom event goals](custom-event-goals.md) to track button clicks and other interactions across your HubSpot pages
+- [Invite your team](users-roles.md) so marketing colleagues can access the dashboard directly
diff --git a/docs/integration-guides.md b/docs/integration-guides.md
index 604b6974..6a43b9f0 100644
--- a/docs/integration-guides.md
+++ b/docs/integration-guides.md
@@ -154,7 +154,7 @@ Step-by-step guides for popular website builders and content management systems.
 | [Google AMP Pages](https://github.com/plausible/analytics/discussions/220#discussioncomment-904022) | Declare an AMP-analytics object on your AMP pages to track with Plausible |
 | [Google Chrome extensions](https://gist.github.com/Joelkw/31b798f69c714c00e9e097b1fd4bb3c8) | Instructions for tracking Chrome browser extensions with Plausible |
 | [DNT and offline](https://github.com/ian/analytics/tree/main/packages/plausible) | Add Do Not Track and offline functionality via the analytics library |
-| [Segment](google-tag-manager.md) | No official integration, but you can integrate via Google Tag Manager |
+| [Segment](https://plausible.io/gtm-template) | No official integration, but you can integrate via Google Tag Manager |
 
 ### Monitoring and automation
 
diff --git a/docs/internal-link-click-tracking.md b/docs/internal-link-click-tracking.md
deleted file mode 100644
index 9a649188..00000000
--- a/docs/internal-link-click-tracking.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: Internal link click tracking
-description: "Track internal link clicks in Plausible using CSS class names and custom event goals. No JavaScript required for most setups."
----
-
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-Our goals and custom events now make it easy to track internal link clicks using CSS class names. Here's [how you can set it up](custom-event-goals.md).
diff --git a/docs/javascript-snippet.md b/docs/javascript-snippet.md
deleted file mode 100644
index 7dc89e80..00000000
--- a/docs/javascript-snippet.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: Where do I find my JavaScript snippet?
-description: "Find your Plausible Analytics JavaScript snippet. Locate the tracking code in your site settings and add it to your site's header to start collecting stats."
----
-
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-See how to [add the Plausible Analytics tracking script to your website](plausible-script.md).
diff --git a/docs/plausible-analytics-self-hosted-guides.md b/docs/plausible-analytics-self-hosted-guides.md
deleted file mode 100644
index 4e6c44da..00000000
--- a/docs/plausible-analytics-self-hosted-guides.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: Plausible Community Edition (CE)
-description: "Self-host Plausible Analytics with Community Edition. Free, AGPL-licensed and open source. Get started with the CE setup guide and compare CE vs. managed cloud hosting."
----
-
-Plausible Community Edition (CE) is our "free as in beer", self-hosted and AGPL-licensed release. Check out the [getting started guide to self-hosting Plausible Community Edition](https://github.com/plausible/community-edition/).
-
-Here's the complete overview of differences between [Plausible Analytics managed hosting in the cloud and Plausible CE](https://plausible.io/self-hosted-web-analytics).
diff --git a/docs/plausible-script.md b/docs/plausible-script.md
index edd82311..2ef96c87 100644
--- a/docs/plausible-script.md
+++ b/docs/plausible-script.md
@@ -40,3 +40,10 @@ We've put together [several other guides and plugins](integration-guides.md) tha
 ## How to check if Plausible Analytics is installed correctly
 
 After adding the Plausible snippet to your website, you can use our testing tool to verify that the snippet is installed correctly and the integration is working. Have some issues with the integration? Take a look at [our guide to troubleshooting your Plausible Analytics integration](troubleshoot-integration.md).
+
+## What's next?
+
+- [Verify the snippet is installed correctly](troubleshoot-integration.md) before assuming data is being collected
+- [Set up goals](goal-conversions.md) to track signups, button clicks, purchases or any other conversion that matters to your site
+- [Import your Google Analytics history](google-analytics-import.md) so your Plausible dashboard starts with your full data record
+- [Invite your team](users-roles.md) so colleagues can access the dashboard without sharing your login
diff --git a/docs/script-extensions-for-wp-plugin.md b/docs/script-extensions-for-wp-plugin.md
deleted file mode 100644
index 3e7e271e..00000000
--- a/docs/script-extensions-for-wp-plugin.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: How to use script extensions with the WordPress plugin
-description: "Enable enhanced measurements like outbound link and file download tracking directly in the Plausible WordPress plugin settings, without editing code."
----
-
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-[Our official WordPress plugin](https://plausible.io/wordpress-analytics-plugin) now supports enhanced measurements with script extensions directly in the plugin settings.
diff --git a/docs/self-hosting-configuration.md b/docs/self-hosting-configuration.md
deleted file mode 100644
index 65a6094e..00000000
--- a/docs/self-hosting-configuration.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: Plausible Community Edition (CE)
-description: "Configuration reference for Plausible Community Edition (CE). Self-host Plausible Analytics with the AGPL-licensed CE release using the GitHub setup guide."
----
-
-Plausible Community Edition (CE) is our "free as in beer", self-hosted and AGPL-licensed release. Check out the [getting started guide to self-hosting Plausible Community Edition](https://github.com/plausible/community-edition/).
-
-Here's the complete overview of differences between [Plausible Analytics managed hosting in the cloud and Plausible CE](https://plausible.io/self-hosted-web-analytics).
diff --git a/docs/self-hosting.md b/docs/self-hosting.md
deleted file mode 100644
index 0f410fd4..00000000
--- a/docs/self-hosting.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: "Self-hosting Plausible: Community Edition (CE)"
-description: "Plausible Community Edition is a free, self-hosted, AGPL-licensed release of Plausible Analytics. Get started with the CE setup guide on GitHub."
----
-
-Plausible Community Edition (CE) is our "free as in beer", self-hosted and AGPL-licensed release. Check out the [getting started guide to self-hosting Plausible Community Edition](https://github.com/plausible/community-edition/).
-
-Here's the complete overview of differences between [Plausible Analytics managed hosting in the cloud and Plausible CE](https://plausible.io/self-hosted-web-analytics).
diff --git a/docs/shopify-integration-deprecated.md b/docs/shopify-integration-deprecated.md
deleted file mode 100644
index d18da251..00000000
--- a/docs/shopify-integration-deprecated.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: Adding Plausible to Shopify
-description: "Deprecated Shopify integration guide for Plausible Analytics. See the updated instructions for the current setup method."
----
-
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-Please see our updated [instructions on integrating Plausible Analytics with your Shopify store](shopify-integration.md).
diff --git a/docs/shopify-integration.md b/docs/shopify-integration.md
index 866187dc..70651d47 100644
--- a/docs/shopify-integration.md
+++ b/docs/shopify-integration.md
@@ -358,3 +358,10 @@ If you want to trigger multiple custom events on the same site, you don't need t
 
 <img alt="track multiple elements in Shopify" src={useBaseUrl('img/track-multiple-elements-shopify.png')} />
 </details>
+
+## What's next?
+
+- [Create goals](custom-event-goals.md) in your Plausible site settings to match the custom events you set up. They won't appear in your dashboard until you do
+- [Add revenue tracking](ecommerce-revenue-tracking.md) to your checkout events to see revenue attribution per source and campaign
+- [Build a funnel](funnel-analysis.md) from product page to checkout to order confirmation to find where visitors drop off
+- [Invite your team](users-roles.md) so colleagues can access the dashboard directly
diff --git a/docs/squarespace-integration.md b/docs/squarespace-integration.md
index 811ad250..bd552adc 100644
--- a/docs/squarespace-integration.md
+++ b/docs/squarespace-integration.md
@@ -69,3 +69,9 @@ In Squarespace, all completed orders are being redirected to a page with the fol
 `https://yourwebsite.com/commerce/orders/977f8aa0-f618-47d0-8787-ee37b1457cc0`
 
 To track completed orders, you can set up a pageview goal. Since the ID (in our example `/977f8aa0-f618-47d0-8787-ee37b1457cc0`) changes with every order, you will need to group those dynamic pages. You can use asterisks (*) to do so. Asterisks can be placed on either end or in the middle of any page path URL. For the example above, you can set up a pageview goal `/commerce/orders/*` to group all of the dynamically created order completion pages.
+
+## What's next?
+
+- [Add revenue tracking](ecommerce-revenue-tracking.md) to your order confirmation goal to measure revenue per source and campaign
+- [Build a funnel](funnel-analysis.md) from your product page to the order confirmation page to see where visitors drop off
+- [Invite your team](users-roles.md) or [share the dashboard](shared-links.md) with your client or collaborators
diff --git a/docs/trial-to-paid.md b/docs/trial-to-paid.md
index 4120fd71..774c5da0 100644
--- a/docs/trial-to-paid.md
+++ b/docs/trial-to-paid.md
@@ -60,3 +60,10 @@ If you skip this step, you can add these details later by opening any invoice fr
 </div>
 
 Your subscription starts immediately and renews automatically. You can [change](change-plan.md) or [cancel](cancel-subscription.md) your plan at any time.
+
+## What's next?
+
+- [Invite your team](users-roles.md) so colleagues can access the dashboard directly without sharing your login credentials
+- [Set up email reports](email-reports.md) to receive a weekly or monthly summary of your stats by email
+- [Create shared links](shared-links.md) to give read-only dashboard access to clients or stakeholders without requiring a Plausible account
+- [Set up goals](goal-conversions.md) to start tracking conversions if you have not already done so
diff --git a/docs/twitter.md b/docs/twitter.md
deleted file mode 100644
index d038a66b..00000000
--- a/docs/twitter.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: Twitter referrals
-description: "Twitter referral tracking in Plausible is no longer supported. See the Sources tab for current acquisition and referrer data."
---- 
-
-This is no longer supported. [See here](https://plausible.io/docs/top-referrers) for more on the Sources tab and acquisition data.
diff --git a/docs/verify-integration.md b/docs/verify-integration.md
deleted file mode 100644
index 65a2ce4d..00000000
--- a/docs/verify-integration.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-displayed_sidebar: someSidebar
-title: Verify that the integration is working
-description: "Check that Plausible Analytics is installed correctly and counting visitors. Use the built-in testing tool to confirm your snippet is firing as expected."
---- 
-
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-See how to check whether Plausible Analytics has been [integrated correctly into your site and is counting your visitors](troubleshoot-integration.md).
diff --git a/docs/webflow-integration.md b/docs/webflow-integration.md
index 4584114f..4fef6a7f 100644
--- a/docs/webflow-integration.md
+++ b/docs/webflow-integration.md
@@ -165,3 +165,10 @@ Use a double dash instead: `plausible-event-name--Signup`. Plausible treats `--`
 ### Anything else?
 
 See the [full custom event troubleshooting guide](custom-event-goals.md#custom-event-not-showing-up) for additional checks including how to verify events are firing in your browser's Network tab.
+
+## What's next?
+
+- [Create goals](custom-event-goals.md) in your Plausible site settings to match the custom events you set up. They won't show in your dashboard until you do
+- [Attach custom properties](/custom-props/for-custom-events) to your events to track additional context like button label or plan type
+- [Build a funnel](funnel-analysis.md) using your custom events as steps to see where visitors drop off
+- [Create a shared link](shared-links.md) to give clients read-only access to the dashboard without a Plausible account
diff --git a/docs/wix-integration.md b/docs/wix-integration.md
index a058275f..a91fbd9b 100644
--- a/docs/wix-integration.md
+++ b/docs/wix-integration.md
@@ -17,3 +17,9 @@ Site-wide JavaScript code injection is a premium Wix feature so you need to upgr
 * Paste your Plausible tracking code, give it a name, choose which pages to add the code to (**All Pages**), select **Load code once per visit** ([read more about this here](https://support.wix.com/en/article/custom-code-loading-options)), select **Head** as the place for the code and click the **Apply** button.
 
 Now you can go to your website and verify whether Plausible Analytics script has been added and to your Plausible Analytics account to see whether the stats are being tracked. See here [how to verify the integration](troubleshoot-integration.md).
+
+## What's next?
+
+- [Set up goals](goal-conversions.md) to track form submissions, button clicks or any conversion that matters to your site
+- [Invite your team](users-roles.md) or [share the dashboard](shared-links.md) with your clients or collaborators
+- [Import your Google Analytics history](google-analytics-import.md) if you're switching from GA and want to keep your historical data
diff --git a/docs/wordpress-integration.md b/docs/wordpress-integration.md
index bffca05f..c134a357 100644
--- a/docs/wordpress-integration.md
+++ b/docs/wordpress-integration.md
@@ -19,3 +19,9 @@ Having trouble with the plugin? Jump to the relevant section:
 - **WP Rocket or another caching plugin is interfering**: add the Plausible script to the exclusion list in your caching plugin's settings
 
 For a full diagnostic walkthrough, see the [troubleshooting guide](troubleshoot-integration.md).
+
+## What's next?
+
+- [Enable enhanced measurements](script-extensions.md) in the plugin settings to automatically track outbound links, file downloads and form submissions without writing code
+- [Set up goals](goal-conversions.md) to measure signups, purchases or any other key action on your site
+- [Import your Google Analytics history](google-analytics-import.md) to keep your stats continuous if you're switching from GA
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 6a28371c..d6380873 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -66,7 +66,8 @@ module.exports = {
             { label: 'Privacy focused', href: 'https://plausible.io/privacy-focused-web-analytics' },
             { label: 'Open source', href: 'https://plausible.io/open-source-website-analytics' },
             { label: 'Visitor segmentation', href: 'https://plausible.io/audience-segmentation' },
-            { label: 'Ecommerce tracking', href: 'https://plausible.io/for-ecommerce-saas' },
+            { label: 'Ecommerce', href: 'https://plausible.io/for-ecommerce' },
+            { label: 'SaaS', href: 'https://plausible.io/for-saas' },
             { label: 'Publishers', href: 'https://plausible.io/for-bloggers-creators' },
             { label: 'Agencies', href: 'https://plausible.io/for-freelancers-agencies' },
             { label: 'White label', href: 'https://plausible.io/white-label-web-analytics' },
diff --git a/src/theme/Footer/index.js b/src/theme/Footer/index.js
index 9aa820e8..24073f78 100644
--- a/src/theme/Footer/index.js
+++ b/src/theme/Footer/index.js
@@ -8,9 +8,9 @@ export default function Footer(props) {
       <div className={styles.ctaBanner}>
         <p className={styles.ctaText}>
           Haven't tried Plausible yet?{' '}
-          <a href="https://plausible.io/register" className={styles.ctaLink}>Start a free trial</a>
+          <a href="https://plausible.io/register" onClick={() => window.plausible && window.plausible('CTA Click', {props: {location: 'Docs footer', button: 'Start free trial'}})} className={styles.ctaLink}>Start a free trial</a>
           {' '}or{' '}
-          <a href="https://plausible.io/plausible.io" className={styles.ctaLink}>view the live demo</a>.
+          <a href="https://plausible.io/plausible.io" onClick={() => window.plausible && window.plausible('CTA Click', {props: {location: 'Docs footer', button: 'View live demo'}})} className={styles.ctaLink}>view the live demo</a>.
         </p>
       </div>
       <OriginalFooter {...props} />