<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai on Simo Ahava's blog</title><link>https://www.simoahava.com/tags/ai/</link><description>Recent content in Ai on Simo Ahava's blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 09 Sep 2026 07:00:00 +0300</lastBuildDate><atom:link href="https://www.simoahava.com/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>#GTMTips: Automatically Generate Version Information In GTM</title><link>https://www.simoahava.com/gtmtips/automatically-generate-version-information-in-gtm/</link><pubDate>Wed, 09 Sep 2026 07:00:00 +0300</pubDate><guid>https://www.simoahava.com/gtmtips/automatically-generate-version-information-in-gtm/</guid><description>&lt;p>&lt;a href="https://tagmanager.google.com/">Google Tag Manager&lt;/a> has a new, AI-powered feature. It&amp;rsquo;s not flashy, it&amp;rsquo;s not prominent, and it&amp;rsquo;s not something you&amp;rsquo;d make a big deal out of. However, it contributes to an absolutely vital part of container management that many, many people neglect: &lt;strong>version naming&lt;/strong>.&lt;/p>
&lt;p>With this new feature, Google Tag Manager &lt;strong>generates a Version Name and Version Description automatically&lt;/strong> from your workspace changes.&lt;/p>
&lt;p>Container versions are often named lazily or not named at all. However, proper naming ensures that the version history is actually &lt;em>useful&lt;/em>. Having a consistent log of what was updated makes it easier to review key milestones in the container history, and it also helps avoid this:&lt;/p></description></item></channel></rss>