Repository navigation
~8% of our analytics traffic is pauseai.se (and previews): only accept our own sites #1226
Description
(Claude suggestion.)
Summary
About 8% of the sessions in our Google Analytics aren't visits to our site. They're visits to pauseai.se, a Swedish-language copy of this website run by PauseAI Sweden volunteers, built from a fork of this repo (https://github.com/EmilSvenberg/pauseai-swedish, see #385). The fork kept our analytics ID, so its visitors are counted as ours.
They probably don't know this is happening. It's inherited code, not a choice, and they can't see the data: it only reaches us. The conversation with them belongs in #385. This issue only stops our analytics from accepting traffic from sites that aren't ours.
Background, in plain terms
- Google Analytics 4 (GA4) is the database that stores our visitor statistics.
- Google Tag Manager (GTM) is a script every page loads (container
GTM-MZS328RW, insrc/app.html). It decides which tracking actions run. - In GTM, each tracking action is a tag (here: "send this page view or event to GA4"), and each tag has a trigger saying when it runs.
- Today the triggers say "run on every page", with no check of which website the page is on. Anyone who copies our code therefore reports into our GA4. That includes forks, Netlify deploy previews, and developers running the site locally.
Evidence
A GA4 exploration by hostname for 21 Sep – 18 Oct 2026:
| Hostname | Sessions | Views |
|---|---|---|
| pauseai.info | 17,917 | 32,208 |
| pauseai.se | 1,608 | 3,437 |
| pauseai.org | 195 | 214 |
| deploy-preview-1183--pauseai.netlify.app | 31 | 33 |
| localhost | 27 | 236 |
| Total | 19,916 | 36,338 |
pauseai.org is our own spare domain. It's meant to redirect to pauseai.info, and that is tracked in a separate issue.
#1223
Fix (in the GTM web interface, no code change)
- Confirm intent with the pauseai.se folk through PauseAI.se takes up first place in google #385!
- Open https://tagmanager.google.com and choose container
GTM-MZS328RW. - Go to Tags. There are four GA4 tags: the main "Google tag" (
G-VRJ4J53FC8) and three event tags,banner_show,banner_clickandbanner_dismiss. - For each tag, open its trigger. Change "This trigger fires on" from All to Some, and add this condition: Page Hostname · matches RegEx ·
^(www\.)?pauseai\.(info|org)$. A trigger shared by several tags only needs editing once. - Click Preview and check:
- The tags fire on https://pauseai.info.
- They don't fire on a deploy preview.
- Click Submit to publish. Nothing changes for visitors until you publish.
The regex includes pauseai.org deliberately. While .org still serves pages, they're real visits to our site. Once .org redirects, no pages load there, so the pattern never needs changing.
Verify
After about a week, the same hostname exploration in GA4 should show only pauseai.info, and pauseai.org until its redirect works. GA4 doesn't clean up past data, so historical reports still need a hostname filter.
Activity