<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>TrueCount blog</title>
  <link>https://truecount.online/blog/</link>
  <atom:link href="https://truecount.online/blog/feed.xml" rel="self" type="application/rss+xml"/>
  <description>Conversion tracking guides and platform changes for online stores.</description>
  <language>en</language>
  <item>
    <title>Why does Google Tag Manager now show gtag.config events, and do I need to change anything?</title>
    <link>https://truecount.online/blog/gtm-gtag-config-events/</link>
    <guid isPermaLink="true">https://truecount.online/blog/gtm-gtag-config-events/</guid>
    <pubDate>Sat, 10 Oct 2026 08:00:00 GMT</pubDate>
    <category>How-to</category>
    <description>As of October 2026, Google says Google Tag Manager containers start as soon as they load, without waiting for gtag(&#39;config&#39;) commands, and those commands now appear in the dataLayer as gtag.config events. A store that loads GTM with its GTM- ID, keeps the Google tag inside GTM and has no wildcard triggers needs no changes. Act if gtm.js loads with a G-, AW- or DC- ID, if the page calls gtag(&#39;config&#39;) without the gtag.js snippet, or if a Custom Event trigger matches every event with the regex .*.</description>
  </item>
</channel>
</rss>
