u/Bukashk0zzz

Google Tag Manager updates timeline (2023–2026) - what actually changed

Been meaning to write this up for a while. Three years of GTM releases in one place.

2023

  • Transformations launched for server containers — finally a way to redact/augment event data before it hits your tags
  • GA4 config tags became Google Tags (September) — settings variables arrived alongside
  • Consent Mode V2 introduced: two new params, ad_user_data and ad_personalization

2024

  • Tag Diagnostics launched with tag quality statuses such as Excellent, Good, Needs attention, Urgent, and No recent data. 
  • Consent Mode override setting added directly in GTM
  • Cloudflare first-party mode automated setup (December)
  • IE support officially dropped

2025

  • April: GTM containers auto-load Google Tag before firing — bigger than it sounds, unlocks Enhanced Conversions and cross-domain in one click
  • May: "First-party mode" renamed Google tag gateway, went GA with Cloudflare support
  • August: readAnalyticsStorage API — finally an official way to read GA client/session IDs in custom templates
  • December: Client ID, Session ID, and Session Number added as native built-in variables

2026 (so far)

  • January: Akamai joins the tag gateway CDN program alongside Cloudflare; Google Tag Gateway enters beta.
  • May: Full integration of Akamai and Fastly.

May 21 (Google Marketing Live): GTM containers can now become Google Tags. Legacy Google Tags inside containers become "Destinations" — one script load instead of three. Visual Event Builder added (WYSIWYG tag/trigger creation). Upgrade is opt-in; nothing breaks automatically.

reddit.com
u/Bukashk0zzz — 4 days ago

sGTM vs no-code tracking tools

The server-side tracking tool market got crowded fast. Stape, TAGGRS, Addingwell, Tracklution, Elevar, ServerTrack - all claiming to solve your tracking problems. Here's a quick framework for choosing.

Go with sGTM hosting (Stape, TAGGRS, Addingwell) if:

  • You already use Google Tag Manager and want to extend it server-side
  • You need flexibility to customize tags, triggers, variables
  • You track across multiple ad platforms (Meta, Google, TikTok, Pinterest, etc.)

These platforms host and manage the server infrastructure so you don't have to mess with Google Cloud or AWS yourself. However, you still need to configure everything in GTM on your side. Stape is the cheapest entry point (starts at $17/month).

Go with no-code / plug-and-play tools (Tracklution, Elevar, TrackBee) if:

  • You want it working today without touching GTM
  • You're on Shopify and just need accurate conversion data sent to your ad platforms
  • You're fine with less customization in exchange for zero maintenance

These tools handle everything - data collection, cookie management, API connections to ad platforms. Trade-off: less control over what data goes where, and you're locked into what the tool supports.

CDPs (Segment, RudderStack)?

This is a completely different category. CDPs fit companies that need to route customer data to dozens of destinations with governance, identity resolution, and schema enforcement. If you're asking "Stape or Segment?" you probably need Stape. If you already know you need a CDP, you're past this conversation.

Remember that no tool fixes bad event naming or a broken data layer. You must get the foundation right first, then pick the infrastructure that matches your team.

reddit.com
u/Bukashk0zzz — 17 days ago

Is your tracking actually server-side?

Some agencies charge for "server-side tracking" and just rearrange client-side tags. Here are some lifehacks on how to detect that in a couple of minutes.

Browser DevTools: Open Network tab, view a page, or add something to the cart to record an event. If the requests go straight to google-analytics.com or facebook.com/tr - that's still client-side. A real server-side setup sends requests to YOUR subdomain (like ss.yoursite.com), and only from there are they redirected to analytical platforms.

GTM account: You need TWO containers - a web container AND a server container. One container = no server-side.

Meta Events Manager: Check event sources. "Pixel" = browser. "Conversions API" = server. If Pixel is mentioned everywhere, that means nothing has changed.

The dead giveaway: Ask your agency to provide you with the container endpoint URL. If they struggle answering that instantly, you don't have server-side tracking.

The verification takes only 2-3 minutes, but it is definitely worth checking before the next invoicing window, should you have any suspicions.

u/Bukashk0zzz — 1 month ago