Skip to content

Commit 43e5bb2

Browse files
Update troubleshoot-integration.md
1 parent 10ec94f commit 43e5bb2

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/troubleshoot-integration.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,15 +26,15 @@ If you are using caching on your site, the latest version of your site where our
2626

2727
## Have you implemented Plausible using Google Tag Manager?
2828

29-
GTM strips the `data-*` attributes by default which can break the tracking which is why we recommend you use our GTM template. Please follow [our GTM guide](https://plausible.io/gtm-template) for instructions on how to integrate Plausible with our Google Tag Manager template.
29+
Please follow [our GTM guide](https://plausible.io/gtm-template) for instructions on how to integrate Plausible with our Google Tag Manager template.
3030

3131
## Does your site use a Content Security Policy (CSP)?
3232

3333
If it does, you would need to add our domain name (plausible.io) specifically to the allowed domains list in order for the script to work. [More info here](https://github.com/plausible/docs/issues/20).
3434

3535
## Are you running on localhost?
3636

37-
Our script automatically disables itself when running on localhost as most people don't want those stats to be counted. In the `script.js` script, `window.location.hostname` is used to verify that. If you do want to track stats on localhost, [see configuration guide](script-extensions.md).
37+
Our script automatically disables itself when running on localhost as most people don't want those stats to be counted. If you do want to track stats on localhost, [see our configuration guide](script-extensions.md).
3838

3939
## Are you running a Google AMP page?
4040

@@ -69,11 +69,11 @@ Are you using Cookiebot or a similar consent management platform? Have you set t
6969

7070
Plausible is built to be privacy-first and compliant with various privacy regulations so do raise this with your legal team as they could provide the green light to not require user consent. See more details in [our data policy](https://plausible.io/data-policy) and in [this legal assessment written by a data protection lawyer](https://plausible.io/blog/legal-assessment-gdpr-eprivacy).
7171

72-
## Is your website on a different URL than the one you added as your site?
72+
## Is your website on a different URL than the one you added?
7373

7474
Our testing tool visits the exact URL that you added to your Plausible account. For example, if you added `yourdomain.com` as your site, the tool will try to visit `yourdomain.com` directly.
7575

76-
If the URL you added doesn’t work or doesn’t point to your actual website, the tool won’t be able to reach it and can’t verify the integration. In that case, please use [our manual verification process instead](#how-to-manually-check-your-integration).
76+
If your website is at a different address, the verification tool will let you enter another URL manually. If the URL you added doesn’t work or doesn’t point to your actual site, the tool won’t be able to reach it or verify your integration. In that case, please use [our manual verification process instead](#how-to-manually-check-your-integration).
7777

7878
## Are you blocking our script or using a VPN that blocks us?
7979

0 commit comments

Comments
 (0)