Add Plausible Analytics or Fathom tracking to Discourse

Community Building Data & reporting
,

AI-generated summary

This discussion provides a guide for integrating Plausible Analytics and Fathom tracking into Discourse. Users share steps to add tracking scripts via theme components, noting that the standard script.js (not hash.js) works better for modern Discourse setups using HTML5 History API. Issues with tracking missing page views are discussed, with resolution found by using the correct script and ensuring the theme is set as default. The guide also addresses Content Security Policy (CSP) concerns, confirming that adding plausible.io or cdn.usefathom.com to CSP is no longer required due to Discourse’s strict-dynamic update. Fathom’s updated guide now reflects these changes, and users confirm the setup works with the recommended scripts. Discourse provides initial instructions, and FathomAsh confirms the updated guide. philh highlights the importance of attaching components to the default theme.

1

Plausible Analytics

  • First, add your domain to your Plausible Analytics instance and grab your tracking code. It should look something like this:
<script async defer data-domain="community.example.com" src="https://plausible.example.com/js/plausible.js"></script>

  • Create a new theme component from Admin > Customize > Themes.

  • Then paste the tracking code in the </head> section.

  • Click Save.

Make sure to add this to all available themes so you can track analytics across all users!

That’s it!

:information_source: If you don’t see data flowing, the script may be blocked by your CSP settings. Check your browser console and if you’re getting errors, add https://plausible.io/js/script.js to your CSP settings.

Edit: Adding the Fathom or Plausible Content security policy script src is no longer required due to this update Content-Security-Policy now uses 'strict-dynamic'

Fathom

Please see the Fathom guide for Discourse.

Updated May 14, 2025 with Fathom’s guide for Discourse
For further info, see Fathom’s guide here:

Note: For both Plausible and Fathom, their scripts work fine in a component attached to your theme(s) and inserted into head of each template you want to track. The new guide from Fathom does not use the “component method”.

3

According to Plausible’s roadmap on Github it seems that it’s going to be possible sometime in the near future to embed one’s Plausible page into one’s website.

Would something like this be embeddable into Discourse, or might it require a plugin, or…?

4

You need a theme-component for that.

5

Hey @Falco, has anything changed about your frontend routing? I can see you recommend people use the hash version of our script which is provided for hash-based routers. It seems to me like Discourse is using the HTML5 PushState API now, is that correct?

6

Not sure why @justin picked the hash version here, since we use HTML5 History API since forever. Made the OP a wiki, so it’s editable by all.

7

I use plausible and I can confirm that the regular plausible.js does NOT log the urls if a user moves from topic to topic. So if I need accurate representation of my visitors, I have to use the hashed plausible js.

8

I have same issue with the hashed version though

9

Weird to have these conflicting reports. Theoretically since Discourse uses the HTML5 history API, I would think that our standard script (not the hash script) would be the one that tracks correctly.

Unfortunately I don’t have a discourse instance set up that I could test with.

10

Probably my lack of knowledge about that :slight_smile: I originally went with the hash version due to us being a SPA and having custom tracking for other analytics providers. If plausible.js works, feel free to change it!

11

Hi @ukutaht

I switched from plausible.hash.js to plausible.js for one of my two discourse sites and this is what happens when I do that.

The site is opened in another tab and it shows no activity at all

SmartSelect_20210707-000518_Firefox
SmartSelect_20210707-000518_Firefox1080Ă—1709 95.6 KB

Here is my other site with plausible.hash.js which correctly shows 1 online and generally, correct pages are also shown in the top pages widget.

SmartSelect_20210707-000834_Firefox
SmartSelect_20210707-000834_Firefox1080Ă—1470 95 KB

I’m happy to try out any troubleshooting in case it helps eliminate need for the hashed js

12

Ah yes I recall seeing the same behavior now that you say this – which is why I went with the hashed script route.

13

Dumb question. Does adding this feature track what’s going on inside your discourse community or does it track outbound traffic to another domain the community is linked to?

What sort of metrics can you find out from this?

14

I can (in my plausible dashboard) see which links of my discourse forum are being visited and from which country.

15

So, there are some bugs with using Plausible as Analytics?

16

No it should work just fine. I’ve been using it on my community for a while now and I haven’t noticed any issues.

17

I’ve edited the OP to include simple directions for using Fathom. Please expand as necessary and further tested.

18

It’s working great :smiley:

19

Hi there and thanks for your guide.

I want to integrate fathom to discourse, do I need to add hash.js to the code, just like you did with plausible ?

20

I think it’s script.js as indicated in the OP (read till To add support for Fathom).

21

Update: The guys at Fathom put together a simple doc to walk you through what you need to do. Enjoy!

Fathom Note: There may be a way to change it, but Discourse adds the rel="canonical" tag for all pages back to the homepage. So all of our page views in Fathom showed as only coming from the homepage.

I talked to Fathom and they said, add this to your tracking script, canonical="false" so it looks as below.

<!-- Fathom - beautiful, simple website analytics -->
<script src="https://cdn.domain.com/script.js" data-spa="auto" data-site="ADHGFREZ" data-canonical="false" defer></script>
 <!-- / Fathom ->

That did the trick.