{"id":4309,"date":"2026-05-10T12:18:20","date_gmt":"2026-05-10T09:18:20","guid":{"rendered":"https:\/\/webanalyst.ro\/?p=4309"},"modified":"2026-05-10T12:36:56","modified_gmt":"2026-05-10T09:36:56","slug":"noul-tag-manager","status":"publish","type":"post","link":"https:\/\/webanalyst.ro\/blog\/2026\/noul-tag-manager\/","title":{"rendered":"Unificarea dintre Google Tag \u0219i Google Tag Manager"},"content":{"rendered":"\n

\u00cen ultimii ani, am avut relans\u0103ri pentru Google Analytics<\/a>, Google Data Studio<\/a>, Google Tag<\/a>, GTM Server-Side<\/a>, \u00eens\u0103 lucrurile au r\u0103mas aproape neschimbate la Google Tag Manager pentru web. Acest lucru se schimb\u0103 chiar \u00een aceast\u0103 lun\u0103.<\/p>\n\n\n\n

Nout\u0103\u021bile din mai 2026 reprezint\u0103 cea mai mare schimbare de arhitectur\u0103 din istoria Google Tag Manager<\/strong> (GTM). Google a \u00eenceput unificarea complet\u0103 \u00eentre GTM<\/strong> \u0219i Google Tag (gtag.js)<\/strong>, introduc\u00e2nd concepte noi precum Destinations<\/strong> \u0219i o pagin\u0103 de Overview<\/strong> regenerat\u0103.<\/p>\n\n\n\n

P\u00e2n\u0103 la finalul acestei luni, ar trebui s\u0103 avem cea mai mare modificare de interfa\u021b\u0103 de c\u00e2nd a ap\u0103rut Google Tag Manager, urmat\u0103 \u00een scurt timp de preluarea capabilit\u0103\u021bilor din Google Tag. \u00cen continuarea articolului, voi detalia aceste schimb\u0103ri, \u00een ordinea cronologic\u0103.<\/p>\n\n\n\n\n\n\n\n

Lansarea paginii \u201eContainer Overview\u201d<\/h2>\n\n\n\n

Google a \u00eenceput de c\u00e2teva zile \u00eenlocuirea vechiului tab de Overview<\/em> (care ar\u0103ta doar istoricul versiunilor) cu o interfa\u021b\u0103 de tip dashboard<\/em>.<\/p>\n\n\n\n

Pe aceast\u0103 pagin\u0103 ar trebui s\u0103 vedem \u00een timp real dac\u0103 datele curg corect c\u0103tre destina\u021bii \u0219i dac\u0103 exist\u0103 erori de implementare sau probleme de consim\u021b\u0103m\u00e2nt (Consent Mode).<\/p>\n\n\n\n

Tot aici, ar trebui s\u0103 apar\u0103 \u0219i butonul oficial de upgrade, prin care utilizatorii GTM pot transforma containerul de aici \u00eentr-un Google Tag cu drepturi depline.<\/p>\n\n\n\n

Destina\u021bii \u00een GTM<\/h2>\n\n\n\n

Imediat dup\u0103 upgrade-ul containerului, structura meniului se schimb\u0103 pentru a face loc sec\u021biunii de Destinations<\/strong>.<\/p>\n\n\n\n

\u00cen loc s\u0103 creeze zeci de tag-uri individuale pentru GA4, Google Ads \u0219i Floodlight, cei care se ocup\u0103 de GTM vor defini aceste platforme ca \u201edestina\u021bii\u201d conectate la Google Tag-ul central.<\/p>\n\n\n\n

Beneficiul imediat al acestei schimb\u0103ri este c\u0103 GTM nu va mai \u00eenc\u0103rca libr\u0103ria gtag.js<\/code> de mai multe ori (o dat\u0103 pentru Ads, o dat\u0103 pentru GA4 etc.), ci o singur\u0103 dat\u0103 pentru toate, ceea ce va \u00eembun\u0103t\u0103\u021bi drastic scorurile Core Web Vitals, \u00een special LCP (Largest Contentful Paint<\/em>)<\/strong> \u0219i TBT<\/strong> (Total Blocking Time<\/em><\/strong>).<\/p>\n\n\n\n

Centralizarea set\u0103rilor Google Tag<\/h2>\n\n\n\n

Odat\u0103 cu consolidarea destina\u021biilor, Google introduce un nou panou de set\u0103ri globale \u00een GTM.<\/p>\n\n\n\n

Set\u0103ri precum redefinirea datelor utilizatorilor (User-provided data<\/em>), set\u0103rile de domeniu (cross-domain tracking<\/em>) \u0219i excluderile de trafic vor fi configurate o singur\u0103 dat\u0103<\/strong> la nivel de container.<\/p>\n\n\n\n

Acestea se vor aplica automat tuturor destina\u021biilor, elimin\u00e2nd riscul de erori umane la configurarea individual\u0103 a tag-urilor. Aceast\u0103 actualizare este a\u0219teptat\u0103 s\u0103 apar\u0103 luna urm\u0103toare \u00een conturi.<\/p>\n\n\n\n

\u201eVisual Event Builder\u201d \u00een GTM<\/h2>\n\n\n\n

Google pl\u0103nuie\u0219te s\u0103 aduc\u0103 experien\u021ba de configurare codeless<\/em> direct \u00een containerul GTM upgradat.<\/p>\n\n\n\n

Astfel, \u00een Google Tag Manager vom putea deschide o fereastr\u0103 \u00een care vom putea selecta butoane sau formulare pentru a crea events sau triggers, f\u0103r\u0103 a mai c\u0103uta manual ID-uri de elemente sau clase de CSS.<\/p>\n\n\n\n

Modificarea aceasta ar trebui s\u0103 simplifice modul de lucru \u00een Tag Manager \u0219i este a\u0219teptat\u0103 \u00een luna iulie 2026.<\/p>\n\n\n\n

Deprecierea vechilor tag-uri de configurare<\/h2>\n\n\n\n

Se estimeaz\u0103 c\u0103 \u00een august – septembrie 2026, vechile tag-uri de tipul GA4 Configuration<\/em> vor fi marcate ca fiind dep\u0103\u0219ite (deprecated<\/em>). De\u0219i vor continua s\u0103 func\u021bioneze, noile func\u021bionalit\u0103\u021bi de AI \u0219i optimizare a vitezei nu vor mai fi disponibile dec\u00e2t pentru cei care au adoptat modelul Destinations<\/strong>.<\/p>\n\n\n\n

De data aceasta, se pare c\u0103 Google a \u00eenv\u0103\u021bat din gre\u0219eli, iar aceast\u0103 migrare va fi, pentru prima dat\u0103, una de tip opt-in<\/em><\/strong>. Google nu va for\u021ba trecerea imediat\u0103 a tuturor conturilor \u00een mai 2026, dar va condi\u021biona accesul la noile unelte de performan\u021b\u0103 \u0219i AI de acest upgrade al containerului.<\/p>\n\n\n\n

Altfel spus, utilizatorii care nu vor aceste schimb\u0103ri vor putea folosi Google Tag Manager la fel ca \u0219i p\u00e2n\u0103 acum.<\/p>\n","protected":false},"excerpt":{"rendered":"

\u00cen ultimii ani, am avut relans\u0103ri pentru Google Analytics, Google Data Studio, Google Tag, GTM Server-Side, \u00eens\u0103 lucrurile au r\u0103mas aproape neschimbate la Google Tag Manager pentru web. Acest lucru se schimb\u0103 chiar \u00een aceast\u0103 lun\u0103. Nout\u0103\u021bile din mai 2026 reprezint\u0103 cea mai mare schimbare de arhitectur\u0103 din istoria Google Tag Manager (GTM). Google a […]<\/p>\n","protected":false},"author":1,"featured_media":4311,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[730,11],"tags":[719,485],"class_list":["post-4309","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-google-tag-manager-2","category-noutati","tag-tag-management","tag-tag-manager"],"_links":{"self":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/4309","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/comments?post=4309"}],"version-history":[{"count":3,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/4309\/revisions"}],"predecessor-version":[{"id":4314,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/4309\/revisions\/4314"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media\/4311"}],"wp:attachment":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media?parent=4309"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/categories?post=4309"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/tags?post=4309"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}