clomonitor
clomonitor copied to clipboard
Do a check for google analytics header
This should be done below probably the check for a website.
We generally want projects to use GA or Hubspot tracking.
cc: @nate-double-u
Hi @caniszczyk
We used to have this check but some users complained about it (i.e. #1307). We discussed it with you and removed it soon afterwards at #1317.
@nate-double-u please work to figure this out
I think we should reintroduce it. Google analytics can be made to be opt in, and in fact this may be a good place to help track whether or not it is opt in on any given site.
The LF uses Google Analytics, and it is helpful to be able to track its use project site to project site.
I'd also like to expand this -- @caniszczyk is asking for a Google analytics check, I'd like to have a general check/listing of which project sites have analytics, and if they do, which analytics they're using. Let's check and document:
- [ ] Site has analytics
- [ ] Type of analytics
- [ ] google analytics, analytics code (or URL for dashboard)
- [ ] plausible.io, analytics code (or URL for dashboard)
- [ ] Hubspot
- [ ] other?
- [ ] is opt-in setup
I agree that there should be a check for analytics and, for each project, an indication of the kind(s) of analytics services that are enabled.
Use of analytics is a best practice, and whether a project uses GA or Plausible or another service is up to them. So, in response to #1307, we shouldn't require GA. Instead CLOMonitor should detect and report which ever analytics service is used. WDYT?
just a follow up, I've also found some projects using Scarf
Thanks, we'll look into this 🙂
@tegioz - thanks. If you could post progress here, that would be great.
We've added the analytics check back at #1756.
- The check now does not affect the project/repository score, as it has a weight of 0 (i.e. not required to pass)
- It now supports some additional providers: GTM (not strictly a provider, but can be useful), Plausible and Scarf
- We've removed support for Google Universal Analytics (GA3)
- We've also improved some regular expressions for previously supported providers
Closed by #1756