{"id":1923,"date":"2016-09-02T13:28:51","date_gmt":"2016-09-02T10:28:51","guid":{"rendered":"https:\/\/webanalyst.ro\/?p=1923"},"modified":"2017-07-10T15:34:11","modified_gmt":"2017-07-10T12:34:11","slug":"workspaces-google-tag-manager","status":"publish","type":"post","link":"https:\/\/webanalyst.ro\/blog\/2016\/workspaces-google-tag-manager\/","title":{"rendered":"Workspaces \u00een Google Tag Manager"},"content":{"rendered":"

S\u0103pt\u0103m\u00e2na aceasta a fost anun\u021bat un update major la Google Tag Manager (GTM). Ini\u021bial, instrumentul nu a fost g\u00e2ndit pentru lucrul \u00een echip\u0103, astfel c\u0103 era un chin ca mai multe persoane s\u0103 lucreze \u00een paralel la acela\u0219i container.<\/p>\n

S\u0103 ne g\u00e2ndim la cazul \u00een care dou\u0103 companii lucreaz\u0103 \u00een GTM pentru acela\u0219i site. Ei editeaz\u0103 aceea\u0219i versiune, iar unii dintre ei pot avea nevoie s\u0103 publice modific\u0103rile c\u00e2nd ceilal\u021bi nu au ajuns la o versiune final\u0103. Totu\u0219i, publicarea le-ar trimite pe toate pe site, ceea ce poate cauza probleme func\u021bion\u0103rii site-ului.<\/p>\n

Problema va fi par\u021bial rezolvat\u0103 prin apari\u021bia unui nou nivel, numit Workspaces. Astfel, fiecare echip\u0103 sau fiecare persoan\u0103 \u00ee\u0219i va edita propriul Workspace \u0219i \u00eel va publica drept versiune nou\u0103 doar c\u00e2nd \u0219tie c\u0103 este gata. Un alt avantaj este c\u0103 \u00een workspaces diferite pot fi editate \u00een acela\u0219i timp chiar acelea\u0219i tag-uri, deci scad riscurile ca altcineva s\u0103 altereze proiectul la care lucr\u0103m. Sigur, c\u00e2nd fiecare \u00ee\u0219i public\u0103 propriul workspace, pot ap\u0103rea conflicte \u00eentre acestea, dar GTM va verifica \u0219i ne va alerta dac\u0103 este cazul, duc\u00e2ndu-ne \u00eentr-o fereastr\u0103 din care le putem rezolva \u00eenainte de publicare.\u00a0\u00cen versiunea gratuit\u0103 de GTM vor putea fi folosite p\u00e2n\u0103 la 3 workspaces \u00een acela\u0219i timp, \u00een timp ce versiunea pl\u0103tit\u0103<\/a> nu are aceast\u0103 limit\u0103.<\/p>\n

Interfa\u021b\u0103 nou\u0103<\/h2>\n

Tot s\u0103pt\u0103m\u00e2na aceasta a fost modificat\u0103 \u0219i interfa\u021ba, pentru a se adopta mai multe elemente de Material Design. Desigur, spa\u021biul prestabilit \u00een care vom lucra de acum este Workspace, \u00een loc de Container. C\u00e2nd verific\u0103m istoricul, \u00eel vom vedea pentru noul container, \u00eens\u0103 \u00een urm\u0103torul tab avem versiunile, unde putem vedea \u0219i informa\u021biile pentru acestea.<\/p>\n

Sunt multe modific\u0103ri interesante de interfa\u021b\u0103 la toate nivelurile de lucru din GTM, ar a\u0219 sublinia interfa\u021ba pentru a crea un nou tag:<\/p>\n

\"gtm_tag_nou\"<\/p>\n

Observa\u021bi butoanele X, de unde putem \u00eenchide rapid respectivul overlayer pentru a reveni la ce lucram anterior, lucru disponibil acum \u00een toat\u0103 interfa\u021ba.<\/p>\n

GTM \u00eenc\u0103 are probleme de rezolvat, inclusiv la permisiunile utilizatorilor, dar echipa de acolo sugereaz\u0103\u00a0c\u0103 lucreaz\u0103 la mai multe func\u021bionalit\u0103\u021bi noi.<\/p>\n","protected":false},"excerpt":{"rendered":"

S\u0103pt\u0103m\u00e2na aceasta a fost anun\u021bat un update major la Google Tag Manager (GTM). Ini\u021bial, instrumentul nu a fost g\u00e2ndit pentru lucrul \u00een echip\u0103, astfel c\u0103 era un chin ca mai multe persoane s\u0103 lucreze \u00een paralel la acela\u0219i container. S\u0103 ne g\u00e2ndim la cazul \u00een care dou\u0103 companii lucreaz\u0103 \u00een GTM pentru acela\u0219i site. Ei […]<\/p>\n","protected":false},"author":1,"featured_media":1929,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[717,718,719,485,821],"class_list":["post-1923","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-noutati","tag-google-tag-manager","tag-gtm","tag-tag-management","tag-tag-manager","tag-workspaces"],"_links":{"self":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/1923","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=1923"}],"version-history":[{"count":2,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/1923\/revisions"}],"predecessor-version":[{"id":1991,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/1923\/revisions\/1991"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media\/1929"}],"wp:attachment":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media?parent=1923"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/categories?post=1923"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/tags?post=1923"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}