<story><title>The Google Analytics Setup I Use on Every Site I Build</title><url>https://philipwalton.com/articles/the-google-analytics-setup-i-use-on-every-site-i-build/</url></story><parent_chain></parent_chain><comment><author>jameslk</author><text>It&amp;#x27;s pretty annoying that I have to create spam filters for Google Analytics to be useful. Every site I&amp;#x27;ve installed GA on has required me to filter out spam. I don&amp;#x27;t understand why something isn&amp;#x27;t done about it at an engineering level. If site owners can set up filters against spammers, is it really that hard for Google to do it? Especially since they can see it across their accounts. Seems like it&amp;#x27;s the same type of issue that plagues email, yet Google seems to have that under control.</text></comment>
<story><title>The Google Analytics Setup I Use on Every Site I Build</title><url>https://philipwalton.com/articles/the-google-analytics-setup-i-use-on-every-site-i-build/</url></story><parent_chain></parent_chain><comment><author>kristianc</author><text>Echoing what others are saying, I much prefer Google Tag Manager. Many clients use a CMS which make injecting dynamic variables into a page a bit of a pain if it&amp;#x27;s not done via rules at runtime.&lt;p&gt;The Next Web has open-sourced its Google Tag Manager setup (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;thenextweb&amp;#x2F;gtm&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;thenextweb&amp;#x2F;gtm&lt;/a&gt;), which has things like Scroll Tracking, Engagement Tracking (riveted.js), Outbound Link Tracking and lots of other things that are not in the default GA setup. They have recently added support for AMP.&lt;p&gt;In my experience it allows clients to get up and running with a useful GA setup in a couple of hours and means that you as a developer don&amp;#x27;t get bothered to make trivial changes.</text></comment>