plausible · metmarkosaric · May 20, 2026 · May 20, 2026
diff --git 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
@@ -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
diff --git a/docs/custom-domain.md b/docs/custom-domain.md
diff --git 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
diff --git 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
diff --git 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
@@ -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
@@ -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
@@ -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
diff --git 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
@@ -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
diff --git a/docs/javascript-snippet.md b/docs/javascript-snippet.md
diff --git a/docs/plausible-analytics-self-hosted-guides.md b/docs/plausible-analytics-self-hosted-guides.md
diff --git 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
diff --git a/docs/self-hosting-configuration.md b/docs/self-hosting-configuration.md
diff --git a/docs/self-hosting.md b/docs/self-hosting.md
diff --git a/docs/shopify-integration-deprecated.md b/docs/shopify-integration-deprecated.md
diff --git 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
@@ -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
@@ -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
diff --git a/docs/verify-integration.md b/docs/verify-integration.md
diff --git 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