{"id":3370,"date":"2023-03-28T18:39:36","date_gmt":"2023-03-28T15:39:36","guid":{"rendered":"https:\/\/webanalyst.ro\/?p=3370"},"modified":"2023-03-28T18:42:26","modified_gmt":"2023-03-28T15:42:26","slug":"unassigned-in-google-analytics-4","status":"publish","type":"post","link":"https:\/\/webanalyst.ro\/blog\/2023\/unassigned-in-google-analytics-4\/","title":{"rendered":"Unassigned \u00een Google Analytics 4"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">S\u0103pt\u0103m\u00e2na trecut\u0103 am semnalat apari\u021bia canalelor de trafic peronalizate (<strong><em><a href=\"https:\/\/webanalyst.ro\/blog\/2023\/ga4-custom-channel-groups\/\" target=\"_blank\" rel=\"noreferrer noopener\">Custom channel groups<\/a><\/em><\/strong>) \u00een Google Analytics 4 \u0219i am detaliat despre cum le pute\u021bi crea \u0219i vizualiza \u00een rapoarte.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Cei care s-au jucat cu noua func\u021bionalitate din analytics au putut observa c\u0103, pe l\u00e2ng\u0103 canalele proprii create, este foarte posibil s\u0103 apar\u0103 \u0219i aici canalul numit <strong>Unassigned<\/strong>. Acela\u0219i lucru se \u00eent\u00e2mpl\u0103 \u0219i \u00een raportul cu <a href=\"https:\/\/webanalyst.ro\/blog\/2021\/channels-google-analytics\/\" target=\"_blank\" rel=\"noreferrer noopener\">canale standard de trafic<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Vestea bun\u0103 este c\u0103 avem solu\u021bii! Dup\u0103 ce am scris despre alte valori nedefinite din Google Analytics 4, precum <em><a href=\"https:\/\/webanalyst.ro\/blog\/2023\/other-in-google-analytics-4\/\" target=\"_blank\" rel=\"noreferrer noopener\">(other)<\/a><\/em> sau chiar un <a href=\"https:\/\/webanalyst.ro\/blog\/2023\/ga4-landing-page-standard\/\" target=\"_blank\" rel=\"noreferrer noopener\">spa\u021biu gol<\/a>, \u00een acest articol voi detalia ce este cu traficul <em>Unassigned<\/em> \u0219i cum putem face ca acesta s\u0103 dispar\u0103 din rapoarte.<\/p>\n\n\n\n<!--more-->\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen Google Analytics 4, traficul care apare cu sursa <em><strong>Unassigned<\/strong><\/em> este traficul pentru care nu s-a calificat pentru niciuna dintre regulile de a intra \u00eentr-un alt canal de trafic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google Analytics 4 organizeaz\u0103 informa\u021biile privind achizi\u021bia clien\u021bilor la nivel de utilizator (<em>user-scope<\/em>), sesiune (<em>session-scope<\/em>) sau eveniment (<em>event-scope<\/em>).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tehnic, <em>Unassigned<\/em> este un canal de trafic care poate avea <em>event-scope<\/em>, <em>user-scope<\/em> sau <em>session-scope<\/em>, adic\u0103 poate ap\u0103rea \u00een toate aceste feluri de rapoarte. Pute\u021bi \u00eencerca acest lucru dac\u0103 ve\u021bi crea diverse rapoarte cu canalele de trafic drept dimensiune \u00een <em><a href=\"https:\/\/webanalyst.ro\/blog\/2022\/explorations-rapoarte-personalizate\/\" target=\"_blank\" rel=\"noreferrer noopener\">Explorations<\/a><\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Canalul de trafic <em>Unassigned<\/em> poate fi v\u0103zut \u0219i \u00een rapoartele standard, mai exact \u00een toate rapoartele din zona de <em>Acquisition<\/em>. Astfel, poate fi v\u0103zut \u00een widget-urile de la <em>Overview<\/em>, dar \u0219i \u00een <em>User acquisition<\/em> \u0219i \u00een <em>Traffic acquisition<\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 avem trafic cu <em>Unassigned<\/em> \u00een rapoarte, nu \u00eenseamn\u0103 neap\u0103rat c\u0103 nu \u0219tim nimic despre acest trafic. O parte din trafic poate fi recunoscut dac\u0103 ad\u0103ug\u0103m \u00een rapoarte dimensiuni precum <em>session source<\/em>, <em>session medium<\/em> sau <em>session campaign<\/em>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cum sc\u0103p\u0103m de <em>Unassigned<\/em><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 a\u021bi urmat pa\u0219ii descri\u0219i mai sus, a\u021bi v\u0103zut c\u0103 o parte din traficul <em>Unassigned<\/em> poate fi identificat \u00een anumite ac\u021biuni de marketing, \u00een timp ce o alt\u0103 parte apare cu <em><strong>(not set)<\/strong><\/em> \u0219i la celelalte dimensiuni.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Iat\u0103 ce putem face \u00een ambele cazuri!<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Folosim parametri UTM<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Traficul de care scriam \u00eenainte c\u0103 apare cu <em>(not set)<\/em> nu a avut parametrii UTM pentru identificarea sursei \u00een Google Analytics.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Traficul trimis spre site-ul sau aplica\u021bia noastr\u0103 ar trebui s\u0103 con\u021bin\u0103 parametrii UTM, pentru a recunoa\u0219te de unde a venit. F\u0103c\u00e2nd asta de fiecare dat\u0103, traficul cu (not set) va disp\u0103rea sau cel pu\u021bin se va mic\u0219ora.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Este dificil s\u0103 punem parametrii pe peste tot, \u00een aceast\u0103 lume digital\u0103 cu aplica\u021bii mobile, re\u021bele social media care se schimb\u0103 mereu sau email-uri care sunt citite \u00een diverse moduri, dar merit\u0103 \u00eencercat.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Urm\u0103m regulile canalelor de trafic<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">S\u0103 ne imagin\u0103m c\u0103 avem o postare \u00een social media cu link c\u0103tre site. Dac\u0103 la modalitate (<em>session medium<\/em>) vom trece <em>social<\/em>, Google Analytics va recunoa\u0219te acest lucru \u0219i va introduce traficul \u00een canalul Organic Social.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen schimb, dac\u0103 noi vom trece <em>pagina<\/em> la modalitate, Google Analytics nu o s\u0103 \u0219tie ce \u00eenseamn\u0103 acest lucru, iar traficul va ajunge la <em>Unassigned<\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ideal ar fi s\u0103 \u00eenv\u0103\u021b\u0103m regulile trecute la <em><a href=\"https:\/\/webanalyst.ro\/blog\/2021\/channels-google-analytics\/\" target=\"_blank\" rel=\"noreferrer noopener\">Default Channels Grouping<\/a><\/em> \u0219i s\u0103 le aplic\u0103m atunci c\u00e2nd stabilim UTM-urile pentru link-uri.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Folosim auto-tagging pentru Google Ads<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Folosim parametri UTM \u00een link-urile din campanii de Search, Display, Video etc. Dar ce facem cu noile canale de trafic, precum Performance Max sau Discovery?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google Analytics renunoa\u0219te mai multe surse de trafic pentru traficul pl\u0103tit:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Paid Search<\/li>\n\n\n\n<li>Paid Social<\/li>\n\n\n\n<li>Paid Shopping<\/li>\n\n\n\n<li>Paid Video<\/li>\n\n\n\n<li>Display<\/li>\n\n\n\n<li>Cross-network<\/li>\n\n\n\n<li>Paid Other<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Sursele de trafic pl\u0103tit din Google, mai exact Google Ads, Google Search 360 \u0219i Google Display &amp; Video 360 pot fi legate automat de proprietatea de Google Analytics 4, prin procedeul numit auto-tagging.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">F\u0103c\u00e2nd acest lucru, suntem asigura\u021bi c\u0103 tot traficul venit din campanii va ap\u0103rea la canalele men\u021bionate mai sus \u0219i nu la <em>Unassigned<\/em>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Ne asigur\u0103m c\u0103 nu exist\u0103 probleme tehnice<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Pe l\u00e2ng\u0103 sfaturile de mai sus, trebuie s\u0103 ne asigur\u0103m \u0219i c\u0103 Google Analytics func\u021bioneaz\u0103 corect.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">C\u00e2teva exemple de probleme care ne-ar putea strica sursele de trafic:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>parametrii UTM nu sunt p\u0103stra\u021bi \u00een site sau aplica\u021bie<\/li>\n\n\n\n<li>GA nu este implementat corect pe toate paginile din site<\/li>\n\n\n\n<li>apar probleme la \u00eenregistrarea evenimentului <code>session_start<\/code><\/li>\n\n\n\n<li>traficul importat \u00een GA nu con\u021bine \u0219i informa\u021bii privind parametrii UTM<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Pe l\u00e2ng\u0103 Unassigned, \u00een acelea\u0219i rapoarte mai poate ap\u0103rea \u0219i <em>(other)<\/em>. Pentru mai multe detalii, v\u0103 invit s\u0103 citi\u021bi <a href=\"https:\/\/webanalyst.ro\/blog\/2023\/other-in-google-analytics-4\/\" target=\"_blank\" rel=\"noreferrer noopener\">articolul despre <em>other<\/em><\/a>. Despre apari\u021bia de <em>(not set)<\/em> \u00een locul unor dimensiuni am scris \u00een acest articol, dar va urma \u0219i un articol detaliat.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>S\u0103pt\u0103m\u00e2na trecut\u0103 am semnalat apari\u021bia canalelor de trafic peronalizate (Custom channel groups) \u00een Google Analytics 4 \u0219i am detaliat despre cum le pute\u021bi crea \u0219i vizualiza \u00een rapoarte. Cei care s-au jucat cu noua func\u021bionalitate din analytics au putut observa c\u0103, pe l\u00e2ng\u0103 canalele proprii create, este foarte posibil s\u0103 apar\u0103 \u0219i aici canalul numit [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3374,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[296,782,925,897],"class_list":["post-3370","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-google-analytics","tag-campanii","tag-channel-grouping","tag-ga4","tag-gaaw"],"_links":{"self":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3370","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=3370"}],"version-history":[{"count":2,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3370\/revisions"}],"predecessor-version":[{"id":3373,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3370\/revisions\/3373"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media\/3374"}],"wp:attachment":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media?parent=3370"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/categories?post=3370"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/tags?post=3370"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}