diff --git a/docs/add-website.md b/docs/add-website.md index ce68faf8..3fd61745 100644 --- a/docs/add-website.md +++ b/docs/add-website.md @@ -1,6 +1,6 @@ --- title: Add your website details -description: "Add your website to Plausible Analytics. Set your domain, configure timezone, and handle subdomains. Your first step before installing the tracking snippet." +description: "Add your website to Plausible Analytics. Set your domain and handle subdomains. Your first step before installing the tracking snippet." --- import useBaseUrl from '@docusaurus/useBaseUrl'; @@ -18,13 +18,3 @@ If you'd like to track a particular subdomain independently from the rest of you :::tip Advanced: the domain field works like a site ID In some setups, you may want to track traffic under a different domain than where the snippet is installed. For example, if you run country-specific domains (`example.de`, `example.nl`) you can point them all at a single Plausible site to collect stats in one place. This is only recommended if you want everything in one dashboard without separate per-domain dashboards. In that case, the domain field acts as an identifier rather than an exact match. [See how to track multiple country or language domains](subdomain-hostname-filter.md#tracking-multiple-country-or-language-domains). ::: - -## Select your reporting timezone - -You need to select your reporting timezone too. This sets the day boundary of your reports regardless of where your traffic is coming from. - -For instance, if you select **(GMT+01:00) Amsterdam, Berlin…** then the beginning and the end of each day of your reporting is calculated based on the time in Amsterdam, even if your visitors come from London or New York. - -The best practice is to set the timezone that reflects the location of your audience or if the audience is very broad and spread across the world to set the timezone of your location. - -Click on the **Add snippet** button to go to the next step where we will provide you with the tracking snippet that you need to [insert into your site](plausible-script.md) to start counting your stats. diff --git a/docs/troubleshoot-integration.md b/docs/troubleshoot-integration.md index 566aa099..ad1902df 100644 --- a/docs/troubleshoot-integration.md +++ b/docs/troubleshoot-integration.md @@ -83,15 +83,17 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; After you've [added the Plausible snippet to your site](plausible-script.md), the dashboard starts displaying stats in real-time as soon as the first visit is counted. There are no delays with data in Plausible. -If you see the dashboard with graphs and numbers, everything is working. Do you keep seeing a blinking green dot instead? That means we're listening for incoming visits but haven't recorded any yet. +After you add the snippet, your dashboard opens immediately. A banner at the top shows the progress and result of the installation check. Plausible first checks whether it can reach your site and detect the installation, then confirms if visits are being counted correctly. -Our testing tool launches automatically from the blinking green dot screen to send test traffic to your site. This test traffic won't be recorded in your dashboard, but you'll see a status message indicating whether Plausible has been installed correctly. +Our testing tool launches automatically in the backgroundto send test traffic to your site. This test traffic won't be recorded in your dashboard. When the check finishes, the banner displays a status message indicating whether Plausible has been installed correctly. + +If the check fails, the banner explains the problem and lets you check again, try another URL, review the installation instructions or verify the installation manually.
- Integration verification tool + Successful installation status in the dashboard banner
-As soon as the first visit is recorded, the verification screen disappears and your dashboard loads automatically. +Real visits appear in your stats as soon as they are recorded. The testing tool does not affect your tracking. If real visits are being recorded correctly, you can safely ignore any error or warning the tool shows. @@ -115,7 +117,7 @@ Before diving deeper, make sure you have done each of these: Find your symptom and jump straight to the right section: -- **[Blinking green dot, nothing recorded yet](#no-data-recorded-yet)**: snippet not loading, cache issue or site not reachable +- **[Installation check is still running or shows an error](#no-data-recorded-yet)**: site unreachable, snippet not loading, cache issue or incorrect URL - **[Tracking was working, then it stopped](#tracking-stopped-working)**: cache, plugin update or script change - **[WordPress plugin issues](#wordpress-plugin-issues)**: admin exclusion, proxy not working or cache conflict - **[My own visits are not showing](#my-own-visits-are-not-showing)**: ad blocker, VPN or WordPress admin exclusion diff --git a/static/img/v2/add-script-extensions-verify-installation.webp b/static/img/v2/add-script-extensions-verify-installation.webp index 1ac2275a..b569587a 100644 Binary files a/static/img/v2/add-script-extensions-verify-installation.webp and b/static/img/v2/add-script-extensions-verify-installation.webp differ diff --git a/static/img/v2/integration-verification-tool.webp b/static/img/v2/integration-verification-tool.webp index 4fbeb076..468d3fe3 100644 Binary files a/static/img/v2/integration-verification-tool.webp and b/static/img/v2/integration-verification-tool.webp differ diff --git a/static/img/v2/website-details.webp b/static/img/v2/website-details.webp index f0b969b6..bbbdb3d4 100644 Binary files a/static/img/v2/website-details.webp and b/static/img/v2/website-details.webp differ