Install Tidemark on WordPress

The Tidemark Analytics plugin adds the script to your public pages. It stores only its own settings in WordPress.

Your site's Settings → Tracking tab shows this same code with your domain and script already filled in, under Install on → WordPress. Each site has its own script file name (a short code such as 3fa91c0b2e.js), so copy the code from there rather than typing it.

Steps#

In WordPress, go to Plugins → Add New, search for Tidemark Analytics, then install and activate it. You can also get it from wordpress.org/plugins/tidemark-analytics.
Open Settings → Tidemark Analytics.
Enter the address of your Tidemark. The dashboard shows it under Install on → WordPress.
Set the site name to the domain you added in Tidemark. It can stay empty when your WordPress site is on that domain.
Save.

Options#

Also record: outbound link clicks, file downloads, form submissions, and scroll depth and time on page. Each one also needs a matching goal in Tidemark.
Script file: only needed if you want the same file name as your snippet, such as 3fa91c0b2e.outbound-links.js. It replaces the choices above.
Do not track: signed-in people with these roles are not counted. Administrators are left out by default. Page previews are never counted.

Record your own events#

Call window.plausible('Signup') to record a custom event, with optional properties: window.plausible('Signup', { props: { plan: 'pro' } }). In WordPress, call it from your theme's JavaScript, in response to something the visitor does. Create a matching goal in your site's settings to see it under Behaviors.

Check that it works#

Open your site in a private window, then look at your Tidemark dashboard. Visits from localhost are ignored, so test on a real address.

If nothing shows up:

Make sure the domain in the snippet matches the domain you added in Tidemark.
Turn off any ad blocker for your own test, and check the browser console for a blocked request.
Make sure the script address in the snippet is reachable from the visitor's browser.
If you use a caching or optimization plugin, exclude the Tidemark script from JavaScript combining, delaying and "load on interaction". The script runs as its own file so it can read its settings from its address.
Make sure you are not signed in as one of the roles excluded under Do not track.

Removing the plugin deletes its settings.