You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Internal traffic filtering in Google Analytics #696
Ashley noticed a third of our traffic is from Direct links, likely from existing PauseAI people.
Here are two options for identifying internal traffic so it can be filtered out. Both only mark data going forwards, i.e. past reports are unaffected:
Option 1: Internal Rule for static IPs
To understand our actual traffic flow, you can mark internal traffic per below (I lack access): analytics account → property → web stream → Tag Settings → Define Internal Traffic → Create Internal Rule
Then internal IPs can be added. If the Data Filter "Internal Traffic" seems to be picking up the right stuff, you can change its state from Testing to Active.
Option 2: Manually add UTM parameter if dynamic IPs
If people are working from home or their home IPs keep changing, we instead ask active volunteers to include parameters when accessing the site. These can easily be filtered out in our reports. Example: https://pauseai.info/australia_**?utm_medium=internal**_
Activity
Wituareard commentedon Mar 25, 2026
Hmm this seems hard to do on a meaningful scale
anthonybailey commentedon Mar 25, 2026
Agree that the idea is good but suggested implementations are not.
Option C is For Cookie https://share.google/uP9o5meEN2j4IUIYy That's good enough for me.
https://claude.ai/share/55cc1254-52b6-4b96-896f-822290631e1f
Wituareard commentedon Mar 26, 2026
I think GA should already recognize repeat visitors right? Who should get the cookie and how?
anthonybailey commentedon Mar 26, 2026
Wituareard commentedon Mar 26, 2026
Nope, sorry. Makes sense.
PeterHorniak commentedon Apr 2, 2026
Any action needed from me to progress this one please?