{"id":16891,"date":"2020-03-30T08:30:44","date_gmt":"2020-03-30T06:30:44","guid":{"rendered":"https:\/\/www.gpec.ro\/blog\/?p=16891"},"modified":"2020-06-12T15:33:13","modified_gmt":"2020-06-12T12:33:13","slug":"google-analytics-cum-te-asiguri-ca-datele-colectate-sunt-corecte-si-complete","status":"publish","type":"post","link":"https:\/\/www.gpec.ro\/blog\/google-analytics-cum-te-asiguri-ca-datele-colectate-sunt-corecte-si-complete","title":{"rendered":"Modul corect de a amplasa codul Google Analytics \u00een site. Cum evi\u021bi gre\u0219elile comune"},"content":{"rendered":"<div class=\"fcbkbttn_buttons_block\" id=\"fcbkbttn_left\"><div class=\"fcbkbttn_like \"><div class=\"fb-like fb-like-button_count\" data-href=\"https:\/\/www.gpec.ro\/blog\/google-analytics-cum-te-asiguri-ca-datele-colectate-sunt-corecte-si-complete\" data-colorscheme=\"light\" data-layout=\"button_count\" data-action=\"like\"  data-size=\"small\"><\/div><\/div><\/div><p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-17152\" src=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/gpec_blog_eugen-1024x586.jpg\" alt=\"\" width=\"910\" height=\"521\" srcset=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/gpec_blog_eugen-1024x586.jpg 1024w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/gpec_blog_eugen-300x172.jpg 300w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/gpec_blog_eugen-768x440.jpg 768w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/gpec_blog_eugen.jpg 2048w\" sizes=\"auto, (max-width: 910px) 100vw, 910px\" \/><\/p>\n<p><strong>Majoritatea deciziilor bune \u00een business sunt sus\u021binute de date. Pentru un business online, Google Analytics este unul dintre cele mai importante instrumente care colecteaz\u0103 \u0219i raporteaz\u0103 datele astfel \u00eenc\u00e2t s\u0103 informeze c\u00e2t mai multe decizii bune.<\/strong><\/p>\n<p><strong>Dar cum ar fi dac\u0103 datele din Google Analytics nu ar fi m\u0103surate corect? Cum ar fi dac\u0103 Google Analytics nu ar m\u0103sura anumite informa\u021bii foarte utile pentru business-ul t\u0103u, care te-ar ajuta s\u0103 iei decizii mai u\u0219or \u0219i cu un grad mai mare de certitudine?\u00a0<\/strong><\/p>\n<p><!--more--><\/p>\n<p><span style=\"font-weight: 400;\">Adev\u0103rul este c\u0103 \u00een majoritatea cazurilor <strong>Google Analytics<\/strong> nu este implementat corespunz\u0103tor, colect\u00e2nd gre\u0219it \u0219i incomplet datele de care ai nevoie. Mai mult, problema este c\u0103 \u00een cele mai multe cazuri nu po\u021bi corecta informa\u021biile care au fost deja colectate gre\u0219it. De aceea este necesar s\u0103 faci c\u00e2t mai repede o verificare a modului \u00een care este configurat codul de Google Analytics \u0219i\u00a0 dac\u0103 colectarea datele se face corect \u0219i complet.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u00cen acest ghid \u00ee\u021bi voi ar\u0103ta pas cu pas cum s\u0103 faci o astfel de verificare \u0219i cum s\u0103 rezolvi cele mai comune erori de implementare pe care le-am \u00eent\u00e2lnit \u00een peste o sut\u0103 de conturi de Google Analytics cu care am interac\u021bionat la <a href=\"https:\/\/www.uxstudio.ro\/\" target=\"_blank\" rel=\"noopener noreferrer\">UX Studio<\/a>.\u00a0<\/span><\/p>\n<p><b><i>Not\u0103:<\/i><\/b><i><span style=\"font-weight: 400;\"> \u00cenainte de a \u00eencepe \u00ee\u021bi recomand s\u0103 setezi <strong>limba Englez\u0103<\/strong> pentru interfa\u021ba Google Analytics. Toate indica\u021biile din acest ghid vor fi pe aceast\u0103 versiune a interfe\u021bei.<\/span><\/i><\/p>\n<h2><b>Verific\u0103 codul de baz\u0103 Google Analytics<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Pentru a func\u021biona, Google Analytics trebuie s\u0103 fie prezent pe paginile site-ului t\u0103u. <strong>Codul Google Analytics<\/strong> poate fi plasat \u00een site prin mai multe metode. Cel mai des sunt folosite urm\u0103toarele metode:\u00a0<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Amplasarea \u00een codul surs\u0103 al paginii<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Amplasarea cu ajutorul unui plugin\/add-on\/extensie a platformei pe care este construit site-ul<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Amplasarea cu ajutorul unui sistem de gestiune a tag-urilor precum Google Tag Manager<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">Dac\u0103 codul este configurat \u0219i amplasat corect, metoda prin care se face acest lucru nu conteaz\u0103 at\u00e2t de mult. Totu\u0219i, noi recomand\u0103m utilizarea Google Tag Manager (GTM) pentru a gestiona toate codurile amplasate pe site, inclusiv Google Analytics. Despre avantajele utiliz\u0103rii Google Tag Manager vom discuta poate \u00eentr-un alt articol. P\u00e2n\u0103 atunci, s\u0103 vedem <strong>ce condi\u021bii trebuie s\u0103 \u00eendeplineasc\u0103 codul de baz\u0103 Google Analytics:<\/strong><\/span><\/p>\n<h3><b>Codul Google Analytics trebuie s\u0103 fie amplasat o singur\u0103 dat\u0103 pe pagin\u0103<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Una dintre cele mai \u00eent\u00e2lnite erori de implementare a codului de Google Analytics este c\u0103 acesta este amplasat pe o pagin\u0103 de mai multe ori. Cel mai des se \u00eent\u00e2mpl\u0103 acest lucru atunci c\u00e2nd amplasarea codului se realizeaz\u0103 prin mai multe metode simultan. De exemplu, este pus un cod prin GTM \u0219i unul direct \u00een sursa paginii. Ne \u00eent\u00e2lnim adesea \u0219i cu cazuri \u00een care codul Google Analytics este amplasat de multiple extensii utilizate de platformele care stau la baza site-ului.\u00a0<\/span><\/p>\n<p><span style=\"text-decoration: underline;\"><span style=\"font-weight: 400;\">D<\/span>e ce e o problem\u0103?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Atunci c\u00e2nd codul Google Analytics este amplasat de mai multe ori pe pagin\u0103, aceste coduri trimit c\u0103tre Google Analytics informa\u021bia c\u0103 s-au f\u0103cut mai multe vizualiz\u0103ri de pagin\u0103 (Pageview), c\u00e2nd de fapt vizualizarea paginii a fost f\u0103cut\u0103 de c\u0103tre utilizator o singur\u0103 dat\u0103. Acest lucru afecteaz\u0103 mai mul\u021bi indicatori precum rata de bounce, num\u0103rul de pagini vizualizate, pagini \/ sesiune, etc.<\/span><\/p>\n<p><span style=\"text-decoration: underline;\"><span style=\"font-weight: 400;\">Cum verific\u0103m dac\u0103 avem aceast\u0103 problem\u0103?<\/span><\/span><\/p>\n<p><span style=\"font-weight: 400;\">Avem mai multe modalit\u0103\u021bii \u0219i indicii care ne pot ajuta s\u0103 identific\u0103m dac\u0103 aceast\u0103 problem\u0103 persist\u0103 \u00een site-ul nostru. Hai s\u0103 le lu\u0103m pe r\u00e2nd:<\/span><\/p>\n<ul>\n<li id=\"verificarecodUA\" style=\"font-weight: 400;\"><strong>Cu ajutorul extensiei de Chrome: <a href=\"https:\/\/www.gpec.ro\/blog\/google-shopping-ads-in-3-pasi\" target=\"_blank\" rel=\"noopener noreferrer\">Google Tag Assistant<\/a>.<\/strong><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Google Tag Assistant este o extensie de Chrome dezvoltat\u0103 de Google care ne permite s\u0103 observ\u0103m ce informa\u021bii se trimit c\u0103tre Google la interac\u021biunea cu o pagin\u0103 web.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u00cen cazurile \u00een care codul Google Analytics este instalat de dou\u0103 (sau mai multe) ori, ve\u021bi vedea \u00een Google Tag Assistant o alert\u0103 \u00een dreptul codului Google Analytics cu mesajul \u201c<\/span><i><span style=\"font-weight: 400;\">Same web property ID is tracked twice<\/span><\/i><span style=\"font-weight: 400;\">\u201d. De asemenea, ve\u021bi vedea c\u0103 la o singur\u0103 accesare a paginii, Google Tag Assistant ne informeaz\u0103 c\u0103 s-au trimis dou\u0103 evenimente de tip Pageview (\u201c<\/span><i><span style=\"font-weight: 400;\">2 Pageview Requests<\/span><\/i><span style=\"font-weight: 400;\">\u201d).<\/span><\/p>\n<div id='gallery-1' class='gallery galleryid-16891 gallery-columns-2 gallery-size-full'><figure class='gallery-item'>\n\t\t\t<div class='gallery-icon portrait'>\n\t\t\t\t<img loading=\"lazy\" decoding=\"async\" width=\"447\" height=\"596\" src=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-tag-analysis.png\" class=\"attachment-full size-full\" alt=\"\" srcset=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-tag-analysis.png 447w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-tag-analysis-225x300.png 225w\" sizes=\"auto, (max-width: 447px) 100vw, 447px\" \/>\n\t\t\t<\/div><\/figure><figure class='gallery-item'>\n\t\t\t<div class='gallery-icon portrait'>\n\t\t\t\t<img loading=\"lazy\" decoding=\"async\" width=\"449\" height=\"597\" src=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-metadata.png\" class=\"attachment-full size-full\" alt=\"\" srcset=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-metadata.png 449w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-metadata-226x300.png 226w\" sizes=\"auto, (max-width: 449px) 100vw, 449px\" \/>\n\t\t\t<\/div><\/figure>\n\t\t<\/div>\n\n<p><span style=\"font-weight: 400;\">Aceast\u0103 modalitate ne permite s\u0103 verific\u0103m dac\u0103 problema este prezent\u0103 doar pe pagina pe care facem aceast\u0103 verificare. Majoritatea problemelor de acest gen le putem identifica prin aceasta modalitate, dar exist\u0103 posibilitatea ca problema s\u0103 apar\u0103 doar pe anumite pagini (pe care nu le verific\u0103m) &#8211; caz \u00een care, pentru depistare, ne ajut\u0103 urm\u0103toarea modalitate.\u00a0<\/span><\/p>\n<p><b><i>Not\u0103:<\/i><\/b><i><span style=\"font-weight: 400;\"> Ca alternativ\u0103 la Google Tag Assistant se pot folosi \u0219i alte extensii care urm\u0103resc ce informa\u021bii se trimit c\u0103tre Google Analytics. De exemplu, preferin\u021ba mea pentru a verifica astfel de informa\u021bii este <\/span><\/i><a href=\"https:\/\/chrome.google.com\/webstore\/detail\/google-analytics-debugger\/jnkmfdileelhofjcijamephohjechhna?hl=en\" target=\"_blank\" rel=\"noopener noreferrer\"><b><i>Google Analytics Debugger<\/i><\/b><\/a><i><span style=\"font-weight: 400;\">, o alt\u0103 extensie de Chrome dezvoltat\u0103 de Google care afi\u0219eaz\u0103 informa\u021biile ceva mai detaliat \u00een consola browser-ului.\u00a0<\/span><\/i><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><strong>Identificarea paginilor de aterizare (landing pages) cu bounce rate foarte mic<\/strong><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">C\u00e2nd observ\u0103m \u00eentr-un cont de Google Analytics o rat\u0103 de bounce mic\u0103 (sub 25%) poate fi un indiciu c\u0103 ne confrunt\u0103m cu problema de <strong>dublare de cod<\/strong>.\u00a0<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-16894\" src=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-bouncerate.png\" alt=\"\" width=\"450\" height=\"254\" srcset=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-bouncerate.png 586w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-bouncerate-300x169.png 300w\" sizes=\"auto, (max-width: 450px) 100vw, 450px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Dac\u0103 rata de bounce este mic\u0103 \u00een \u00eentregul cont, atunci problema persist\u0103 cel mai probabil pe toate paginile. <a href=\"#verificarecodUA\">Folosim metoda indicat\u0103 la punctul 1<\/a> \u0219i valid\u0103m \u0219i prin intermediul ei problema.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Dac\u0103 rata de bounce pentru \u00eentregul cont pare c\u00e2t de c\u00e2t normal\u0103 (peste 25%), vrem s\u0103 ne asigur\u0103m c\u0103 nu exist\u0103 problema de dublare a codului doar pe anumite pagini.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Ca s\u0103 identific\u0103m aceste pagini, navig\u0103m \u00een interfa\u021ba Google Analytics \u00een <\/span><b>Behavior &gt; Site Content &gt; Landing Pages<\/b><span style=\"font-weight: 400;\">, aplic\u0103m un filtru cu ajutorul c\u0103ruia s\u0103 vedem doar paginile cu mai mult de 1.000 sesiuni (ne dorim s\u0103 elimin\u0103m paginile cu pu\u021bin trafic unde putem avea natural rate de bounce foarte mici) \u0219i ordon\u0103m raportul cresc\u0103tor dup\u0103 Bounce Rate.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-16895\" src=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-bouncerate-pages-1024x440.png\" alt=\"\" width=\"910\" height=\"391\" srcset=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-bouncerate-pages-1024x440.png 1024w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-bouncerate-pages-300x129.png 300w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-bouncerate-pages-768x330.png 768w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-bouncerate-pages.png 1600w\" sizes=\"auto, (max-width: 910px) 100vw, 910px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Observ\u0103m dac\u0103 sunt pagini cu bounce rate foarte mic \u0219i valid\u0103m dac\u0103 este sau nu vreo problem\u0103 prin intermediul metodei descrise la punctul anterior.\u00a0\u00a0<\/span><\/p>\n<h3><b>Codul Google Analytics trebuie s\u0103 fie amplasat pe fiecare pagin\u0103 a site-ului<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Ca datele din Google Analytics s\u0103 se \u00eenregistreze corect, codul Google Analytics trebuie amplasat pe fiecare pagin\u0103 a site-ului. Dac\u0103 site-ul are p\u00e2n\u0103 \u00een 10.000 pagini unice, po\u021bi folosi folosi un instrument disponibil online: <\/span><a href=\"http:\/\/gachecker.com\/\" target=\"_blank\" rel=\"noopener noreferrer\"><b>GA Checker<\/b><\/a><span style=\"font-weight: 400;\">. Ca alternativ\u0103 po\u021bi folosi un instrument de \u201csite crawler\u201d prin care po\u021bi seta reguli astfel \u00eenc\u00e2t s\u0103 identifice \u0219i s\u0103 raporteze doar paginile care nu au \u00een surs\u0103 secven\u021ba de cod asociat\u0103 cu Google Analytics sau Google Tag Manager. Un astfel de instrument pe care \u00eel folosim la UX Studio este <\/span><a href=\"https:\/\/www.screamingfrog.co.uk\/seo-spider\/\" target=\"_blank\" rel=\"noopener noreferrer\"><b>Screaming Frog<\/b><\/a><span style=\"font-weight: 400;\">, utilizat cu succes \u0219i \u00een <strong>activit\u0103\u021bile de optimizare pentru motoarele de c\u0103utare<\/strong> (SEO).<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Dac\u0103 codul Google Analytics este amplasat \u00een pagin\u0103 prin intermediul Google Tag Manager, folose\u0219te metodele de mai sus pentru a identifica dac\u0103 scriptul GTM este \u00eenc\u0103rcat pe toate paginile apoi vezi \u00een interfa\u021ba GTM dac\u0103 trigger-ul pentru codul Google Analytics este setat s\u0103 se declan\u0219eze pe toate paginile site-ului.<\/span><\/p>\n<p><b><i>Excep\u021bie!<\/i><\/b><i><span style=\"font-weight: 400;\"> Dac\u0103 folose\u0219te \u00een site iframe-uri, asigur\u0103-te c\u0103 nu se declan\u0219eaz\u0103 codul de Google Analytics \u0219i \u00een pagina p\u0103rinte \u0219i \u00een pagina iframe, altfel se va dubla num\u0103rul de afi\u0219\u0103ri de pagini raportate c\u0103tre Google Analytics din aceste pagini.<\/span><\/i><\/p>\n<h3><b>Codul Google Analytics trebuie s\u0103 foloseasc\u0103 ultima libr\u0103rie disponibil\u0103<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Google Analytics evolueaz\u0103 constant, iar pentru a \u021bine pas cu aceste evolu\u021bii este nevoie ca periodic s\u0103 rescrie complet libr\u0103riile pe care se bazeaz\u0103. Cea mai utilizat\u0103 \u0219i stabil\u0103 versiune \u00een acest moment este cea numit\u0103 <strong>Universal Analytics<\/strong> (construit\u0103 \u00een jurul libr\u0103riei JavaScript &#8211; analytics.js). Cu toate c\u0103 majoritatea site-urilor o folosesc, \u00eenc\u0103 ne mai \u00eent\u00e2lnim uneori cu versiunea anterioar\u0103 (construit\u0103 \u00een jurul libr\u0103riei JavaScript &#8211; ga.js). Cu toate c\u0103 \u00eenc\u0103 este suportat\u0103, acesteia \u00eei lipsesc multe dintre func\u021bionalit\u0103\u021bile \u0219i capabilit\u0103\u021bile de raportare pe care le are \u00een prezent Google Analytics.<\/span><\/p>\n<p><strong>Universal Analytics vs Global Site Tag (GTAG)<\/strong><\/p>\n<p><span style=\"font-weight: 400;\">E posibil s\u0103 fi auzit \u00een ultimii ani de Global Site Tag (gtag.js) ca fiind o versiune mai recent\u0103 pentru Universal Analytics (analytics.js). Cu toate c\u0103 este adev\u0103rat c\u0103 aceast\u0103 versiune a fost lansat\u0103 dup\u0103 Universal Analytics (2017 vs 2013), Global Site Tag (gtag.js) este momentan o libr\u0103rie menit\u0103 s\u0103 uneasc\u0103 sub o singur\u0103 umbrel\u0103 mai multe instrumente de la Google (ex. Google Analytics, Google Ads).\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u00cen practic\u0103, Global Site Tag folose\u0219te Universal Analytics ca libr\u0103rie pentru Google Analytics, doar c\u0103 schimb\u0103 un pic modul \u00een care se apeleaz\u0103 diverse func\u021bii din aceast\u0103 libr\u0103rie.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u00cen orice caz, nu trebuie s\u0103 \u00ee\u021bi faci griji referitor la care dintre libr\u0103riile de mai sus s\u0103 le utilizezi at\u00e2t timp c\u00e2t utilizezi Google Tag Manager pentru a integra codul Google Analytics pe pagini.<\/span><\/p>\n<h3><strong>Cum identific\u0103m ce libr\u0103rie de Google Analytics folose\u0219te un site \u0219i ce trebuie s\u0103 facem?<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Cea mai simpl\u0103 modalitate de a identifica ce libr\u0103rie se folose\u0219te este s\u0103 verific\u0103m sursa HTML a unei pagini de pe site. \u00cen sursa paginii efectua\u021bi o c\u0103utare dup\u0103 <\/span><b>UA-<\/b><span style=\"font-weight: 400;\"> (a\u0219a \u00eencep toate id-urile de proprietate Google Analytics).<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u00cen general, ne \u00eent\u00e2lnim cu una dintre urm\u0103toarele variante (nu te \u00eengrijora dac\u0103 nu arat\u0103 fix ca \u00een exemplu):\u00a0<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\"><strong>Global Site Tag (gtag.js)<\/strong><\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-16897\" src=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-global-site-tag.png\" alt=\"\" width=\"766\" height=\"242\" srcset=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-global-site-tag.png 766w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-global-site-tag-300x95.png 300w\" sizes=\"auto, (max-width: 766px) 100vw, 766px\" \/><\/p>\n<p><strong>2. Universal Analytics (analytics.js)<\/strong><\/p>\n<p><span style=\"font-weight: 400;\"><strong><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-16898\" src=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-UA.png\" alt=\"\" width=\"772\" height=\"342\" srcset=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-UA.png 772w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-UA-300x133.png 300w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-UA-768x340.png 768w\" sizes=\"auto, (max-width: 772px) 100vw, 772px\" \/><br \/>\n<\/strong><\/span><span style=\"font-weight: 400;\">Dac\u0103 identifici una dintre libr\u0103riile de mai sus, \u00eenseamn\u0103 c\u0103 se folose\u0219te <strong>ultima versiune stabil\u0103 pentru Google Analytics<\/strong>. Cu toate c\u0103, setate corect, nu exist\u0103 nicio problem\u0103 \u00een ceea ce prive\u0219te \u00eenregistrarea datelor \u00een Google Analytics, este recomandat totu\u0219i ca astfel de coduri s\u0103 fie gestionate prin intermediul Google Tag Manager (GTM).<\/span><\/p>\n<p><span style=\"font-weight: 400;\"><strong>3. Classic Analytics (ga.js)<\/strong><\/span><\/p>\n<p><span style=\"font-weight: 400;\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-16899\" src=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-classic.png\" alt=\"\" width=\"775\" height=\"347\" srcset=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-classic.png 775w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-classic-300x134.png 300w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-classic-768x344.png 768w\" sizes=\"auto, (max-width: 775px) 100vw, 775px\" \/><\/span><\/p>\n<p><span style=\"font-weight: 400;\">Dac\u0103 identifici aceast\u0103 versiune de Google Analytics, \u00eenseamn\u0103 c\u0103 site-ul folose\u0219te <strong>o libr\u0103rie veche<\/strong>, care nu beneficiaz\u0103 de func\u021bionalit\u0103\u021bile noi \u0219i nu mai prime\u0219te suport. Ar trebui de urgen\u021b\u0103 s\u0103 ini\u021biezi un proiect de migrare c\u0103tre Universal Analytics (analytics.js) &#8211; cea mai nou\u0103 libr\u0103rie stabil\u0103 de la Google Analytics.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Dac\u0103 c\u0103ut\u00e2nd <b>UA- <\/b>\u00een sursa HTML a paginii nu ai g\u0103sit nimic, \u00eencearc\u0103 s\u0103 identifici codul de Google Tag Manager (GTM). Caut\u0103 dup\u0103 <b>GTM-<\/b> (a\u0219a \u00eencep toate id-urile de container GTM) ca s\u0103 \u00eel identifici. Codul ar trebui s\u0103 arate \u00een felul urm\u0103tor:<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u00cen sec\u021biunea <\/span><b>&lt;head&gt;<\/b><span style=\"font-weight: 400;\"> a paginii:<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-16900\" src=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-sectiunea-head.png\" alt=\"\" width=\"773\" height=\"167\" srcset=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-sectiunea-head.png 773w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-sectiunea-head-300x65.png 300w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-sectiunea-head-768x166.png 768w\" sizes=\"auto, (max-width: 773px) 100vw, 773px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Imediat dup\u0103 tag-ul HTML <\/span><b>&lt;body&gt;<\/b><span style=\"font-weight: 400;\">:<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-16901\" src=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-sectiunea-body.png\" alt=\"\" width=\"773\" height=\"112\" srcset=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-sectiunea-body.png 773w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-sectiunea-body-300x43.png 300w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/setare-analytics-sectiunea-body-768x111.png 768w\" sizes=\"auto, (max-width: 773px) 100vw, 773px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Dac\u0103 codul Google Analytics este gestionat prin intermediul Google Tag Manager, nu trebuie s\u0103-\u021bi faci griji cu privire la versiunea libr\u0103riei folosite.<\/span><\/p>\n<h3><strong>Google Analytics App + Web<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Versiunile stabile ale libr\u0103riilor Google Analytics de p\u00e2n\u0103 acum puteau colecta \u0219i raporta date fie doar pentru <strong>site-urile web (Universal Analytics)<\/strong>, fie doar pentru <strong>aplica\u021biile de mobil (Firebase)<\/strong>. Multe business-uri online folosesc \u00eens\u0103 at\u00e2t site-uri web c\u00e2t \u0219i aplica\u021bii mobile pentru a-\u0219i desf\u0103\u0219ura activitatea. De aici \u0219i nevoia de a veni cu o versiune unificat\u0103 de Google Analytics care s\u0103 poat\u0103 colecta \u0219i raporta simultan datele at\u00e2t din aplica\u021biile mobile c\u00e2t \u0219i din site-urile web.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">De aceea, <\/span><a href=\"https:\/\/blog.google\/products\/marketingplatform\/analytics\/new-way-unify-app-and-website-measurement-google-analytics\/\"><span style=\"font-weight: 400;\">Google a lansat \u00een 2019<\/span><\/a><span style=\"font-weight: 400;\"> versiunea beta a libr\u0103riei App + Web, o libr\u0103rie bazat\u0103 pe libr\u0103ria Firebase (folosit\u0103 p\u00e2n\u0103 acum pentru aplica\u021biile mobile) \u0219i care urmeaz\u0103 \u00een viitorul apropiat s\u0103 devin\u0103 noul standard pentru Google Analytics. Aceast\u0103 versiune schimb\u0103 radical modul \u00een care sunt colectate \u0219i raportate datele \u00een Google Analytics, dar fiind \u00eenc\u0103 \u00een beta, recomandarea noastr\u0103 este s\u0103 folosi\u021bi momentan versiunea Universal Analytics (chiar dac\u0103 \u00eencuraj\u0103m s\u0103 testa\u021bi \u00een paralel \u0219i versiunea App + Web).<\/span><\/p>\n<h3><b>Cross-domain tracking este configurat corect (dac\u0103 este cazul)<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">C\u00e2teodat\u0103 se \u00eent\u00e2mpl\u0103 ca un business online s\u0103-\u0219i desf\u0103\u0219oare activitatea pe mai multe domenii web, interconectate. C\u00e2nd ne \u00eent\u00e2lnim cu acest caz este nevoie s\u0103 ne asigur\u0103m c\u0103 informa\u021biile despre utilizatori se trimit corect \u00eentre domenii atunci c\u00e2nd vizitatorii navigheaz\u0103 dintr-un domeniu \u00een altul.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>\u00cen urm\u0103torul articol vom discuta despre <a href=\"https:\/\/www.gpec.ro\/blog\/google-analytics-cum-te-asiguri-ca-datele-colectate-sunt-corecte-si-complete-partea-ii\" target=\"_blank\" rel=\"noopener noreferrer\">verificarea set\u0103rilor de baz\u0103<\/a> (Property \u0219i View).<\/p>\n<p>&nbsp;<\/p>\n<hr \/>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-17147 alignleft\" src=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/eugen-potlog.jpg\" alt=\"\" width=\"202\" height=\"202\" srcset=\"https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/eugen-potlog.jpg 415w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/eugen-potlog-150x150.jpg 150w, https:\/\/www.gpec.ro\/blog\/wp-content\/uploads\/2020\/03\/eugen-potlog-300x300.jpg 300w\" sizes=\"auto, (max-width: 202px) 100vw, 202px\" \/><\/p>\n<p><strong>Eugen Potlog<\/strong><\/p>\n<p><em>Founder &amp; Chief Optimizer\u00a0<strong><a href=\"https:\/\/www.uxstudio.ro\/\" target=\"_blank\" rel=\"noopener noreferrer\">UX Studio<\/a><\/strong><\/em><\/p>\n<p><a href=\"https:\/\/ro.linkedin.com\/in\/eugenpotlog\" target=\"_blank\" rel=\"noopener noreferrer\"><strong>Eugen<\/strong><\/a> are peste 10 ani de experien\u021b\u0103 \u00een online. A lansat UX Studio \u00een iulie 2017 din dorin\u021ba de a ajuta companiile s\u0103-\u0219i \u00eembun\u0103t\u0103\u021beasc\u0103 performan\u021bele site-urilor prin oferirea unor experien\u021be de utilizare mai bune. Fiind certificat de <a href=\"http:\/\/bit.ly\/uxcertified\" target=\"_blank\" rel=\"noopener noreferrer\">Nielsen Norman Group<\/a> (UX Certified) \u0219i <a href=\"http:\/\/bit.ly\/CXLcertified\" target=\"_blank\" rel=\"noopener noreferrer\">ConversionXL<\/a> (CXL Certified Optimizer \u0219i CXL Certified Digital Analyst), Eugen aplic\u0103 \u00een cadrul UX Studio metode de User Experience (UX) \u0219i Conversion Rate Optimization (CRO) pentru a identifica, testa \u0219i valida modalit\u0103\u021bi de \u00eembun\u0103t\u0103\u021bire a ratelor de conversie \u0219i a experien\u021bei de utilizare a site-ului.<\/p>\n<p>&nbsp;<\/p>\n<hr \/>\n<p>Nu rata seria de articole cu con\u021binut #CraftedToInspire semnate de speciali\u0219ti \u00een eCommerce \u0219i Digital Marketing, aboneaz\u0103-te la <a href=\"https:\/\/www.gpec.ro\/aboneaza-te-la-newsletter-ul-gpec\/\">Newsletter-ul GPeC<\/a>!<\/p>\n","protected":false},"excerpt":{"rendered":"<div class=\"fcbkbttn_buttons_block\" id=\"fcbkbttn_left\"><div class=\"fcbkbttn_like \"><div class=\"fb-like fb-like-button_count\" data-href=\"https:\/\/www.gpec.ro\/blog\/google-analytics-cum-te-asiguri-ca-datele-colectate-sunt-corecte-si-complete\" data-colorscheme=\"light\" data-layout=\"button_count\" data-action=\"like\"  data-size=\"small\"><\/div><\/div><\/div><p>Majoritatea deciziilor bune \u00een business sunt sus\u021binute de date. Pentru un business online, Google Analytics este unul dintre cele mai importante instrumente care colecteaz\u0103 \u0219i raporteaz\u0103 datele astfel \u00eenc\u00e2t s\u0103 informeze c\u00e2t mai multe decizii bune. Dar cum ar fi dac\u0103 datele din Google Analytics nu ar fi m\u0103surate corect? Cum ar fi dac\u0103 Google Analytics nu ar m\u0103sura anumite informa\u021bii foarte utile pentru business-ul t\u0103u, care te-ar ajuta s\u0103 iei decizii mai u\u0219or \u0219i cu un grad mai mare de certitudine?\u00a0<\/p>\n","protected":false},"author":25,"featured_media":17152,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3493],"tags":[740,624,281,3501,3497,3495,3499,719],"class_list":["post-16891","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-google-analytics","tag-cro","tag-eugen-potlog","tag-google-analytics-ro","tag-google-analytics-setup","tag-google-tag-assistant","tag-google-tag-manager","tag-universal-analytics","tag-ux"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.gpec.ro\/blog\/wp-json\/wp\/v2\/posts\/16891","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gpec.ro\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gpec.ro\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gpec.ro\/blog\/wp-json\/wp\/v2\/users\/25"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gpec.ro\/blog\/wp-json\/wp\/v2\/comments?post=16891"}],"version-history":[{"count":10,"href":"https:\/\/www.gpec.ro\/blog\/wp-json\/wp\/v2\/posts\/16891\/revisions"}],"predecessor-version":[{"id":17578,"href":"https:\/\/www.gpec.ro\/blog\/wp-json\/wp\/v2\/posts\/16891\/revisions\/17578"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gpec.ro\/blog\/wp-json\/wp\/v2\/media\/17152"}],"wp:attachment":[{"href":"https:\/\/www.gpec.ro\/blog\/wp-json\/wp\/v2\/media?parent=16891"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gpec.ro\/blog\/wp-json\/wp\/v2\/categories?post=16891"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gpec.ro\/blog\/wp-json\/wp\/v2\/tags?post=16891"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}