{"id":3320,"date":"2023-01-24T22:16:36","date_gmt":"2023-01-24T20:16:36","guid":{"rendered":"https:\/\/webanalyst.ro\/?p=3320"},"modified":"2023-10-13T14:42:13","modified_gmt":"2023-10-13T11:42:13","slug":"limite-ga4-looker-studio","status":"publish","type":"post","link":"https:\/\/webanalyst.ro\/blog\/2023\/limite-ga4-looker-studio\/","title":{"rendered":"Limitele dashboard-urilor GA4 \u0219i solu\u021bia Data Studio \/ Looker Studio"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">La sf\u00e2r\u0219itul anului 2022, Google a anun\u021bat noi limite pentru datele trimise prin Google Analytics Data API. Primii care au avut probleme sunt cei care preiau datele din <strong>Google Analytics 4<\/strong>, \u00een special pentru diverse dashboard-uri. Sunt inclu\u0219i aici \u0219i utilizatorii de <strong>Google Data Studio<\/strong> \/ <strong>Looker Studio<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Multe rapoarte f\u0103cute \u00een Looker Studio nu mai func\u021bioneaz\u0103. \u00cen continuare, voi detalia motivele, dar \u0219i posibile solu\u021bii pentru a vedea datele \u00een Google Analytics \u00een Looker Studio (Data Studio) sau \u00een alte instrumente de dashboarding.<\/p>\n\n\n\n<!--more-->\n\n\n\n<h2 class=\"wp-block-heading\">Google Analytics Data API<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Acest API ne ofer\u0103 acces programatic la datele din Google Analytics 4. Cei care au rapoarte care folosesc aceste date \u00een afara interfe\u021bei de Google Analytics, probabil \u00eel folosesc deja.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pe 10 noiembrie 2022, Google a anun\u021bat limite la datele care se pot prelua din Google Analytics. Dup\u0103 atingerea acestor limite, datele nu mai pot fi preluate, iar dashboard-ul nu va mai func\u021biona. \u00cen cazul Google Data Studio \/ Looker Studio, vom primi o eroare atunci c\u00e2nd \u00eencerc\u0103m s\u0103 acces\u0103m raportul:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"603\" height=\"251\" src=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-eroare-ga4.png\" alt=\"\" class=\"wp-image-3321\" srcset=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-eroare-ga4.png 603w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-eroare-ga4-300x125.png 300w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-eroare-ga4-150x62.png 150w\" sizes=\"auto, (max-width: 603px) 100vw, 603px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Printre cele mai importante limit\u0103ri se afl\u0103 cele 25.000 de <em>tokens<\/em> sau pachete de date pe care le putem folosi \u00eentr-o zi dintr-o proprietate de Google Analytics 4. Aten\u021bie, exist\u0103 \u0219i o limit\u0103 de <strong>1.250 de <em>tokens<\/em> pe care le putem folosi \u00eentr-o or\u0103<\/strong>! Am \u00eencercat un raport propriu pentru acest site \u0219i am observat c\u0103 putem atinge u\u0219or cifra de 1.000 de <em>tokens<\/em> \u00eentr-un raport, iar asta a fost la un site cu pu\u021bine date!<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>UPDATE: Google a realizat c\u0103 num\u0103rul de tokens este mult prea mic \u0219i a ridicat limitele. Celelalte probleme r\u0103m\u00e2n \u00eens\u0103 valabile pentru cei care au nevoie de mai multe date din Google Analytics!<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Alte limite se refer\u0103 la num\u0103rul apel\u0103rilor de API \u0219i sunt limitate la 10. Asta \u00eenseamn\u0103 c\u0103 dac\u0103 \u00eenc\u0103rc\u0103m un dashboard cu 10 grafice bazate pe date din Google Analytics, am atins limita. Mai mult, dac\u0103 un grafic are \u0219i legend\u0103, e posibil s\u0103 foloseasc\u0103 dou\u0103 apel\u0103ri, deci \u0219i aceasta este o limit\u0103 u\u0219or de atins. Mai mul\u021bi utilizatori care \u00eencarc\u0103 un raport \u00een acela\u0219i timp sunt contoriza\u021bi \u0219i ei cu apel\u0103ri separate.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Vizualizarea limitelor \u00een Data Studio \/ Looker Studio<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Rapoartele create \u00een Looker Studio pot fi monitorizate pentru a vedea c\u00e2te pachete de date de la Google Analytics au utilizat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rapoartele care sunt legate la o surs\u0103 de date din Google Analytics vor avea op\u021biunea numit\u0103 <em><strong>Google Analytics Tokens Usage<\/strong><\/em>, pe care o vede\u021bi cu un click dreapta pe raport, atunci c\u00e2nd sunte\u021bi \u00een modul <em>Edit<\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pute\u021bi vedea monitorizarea pentru un raport de-al meu. Raportul nu este creat acum, \u00eens\u0103 prima dat\u0103 c\u00e2nd l-am \u00eenc\u0103rcat a dep\u0103\u0219it 1.000 de <em>tokens<\/em>.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"683\" height=\"735\" src=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-token-usage.png\" alt=\"\" class=\"wp-image-3322\" srcset=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-token-usage.png 683w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-token-usage-279x300.png 279w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-token-usage-139x150.png 139w\" sizes=\"auto, (max-width: 683px) 100vw, 683px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen acest caz, nu este o problem\u0103 la nivel de raport, dar este la unele dintre graficele mele, care nu mai apar pentru c\u0103 am accesat datele de prea multe ori \u00een ultima or\u0103. Eroarea poate fi v\u0103zut\u0103 \u00een imaginea de la \u00eenceputul articolului. Partea bun\u0103 este c\u0103 aceast\u0103 eroare a trecut la finalul respectivei ore, dar nu tot timpul suntem la fel de noroco\u0219i.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Looker Studio ne ofer\u0103 posibilitatea de a vedea datele \u0219i la nivelul fiec\u0103rui grafic sau tabel din raport. Dac\u0103 vrem s\u0103 vedem pentru unul singur, putem merge pe acesta. Av\u00e2nd graficul selectat, vom da click dreapta \u0219i vom alege \u0219i aici <em>Google Analytics Tokens Usage<\/em>. Monitorizarea unui singur grafic sau tabel arat\u0103 ca \u00een imaginea urm\u0103toare:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"543\" height=\"330\" src=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-graph-monitor.png\" alt=\"\" class=\"wp-image-3324\" srcset=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-graph-monitor.png 543w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-graph-monitor-300x182.png 300w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2023\/01\/looker-studio-graph-monitor-150x91.png 150w\" sizes=\"auto, (max-width: 543px) 100vw, 543px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Solu\u021bii pentru a vizualiza dashboard-uri<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Datele care ne sunt oferite de Looker Studio ne ajut\u0103 s\u0103 identific\u0103m problema. Putem vedea dac\u0103 este o problem\u0103 cu toate rapoartele conectate sau este doar cu un raport. La nivel de raport, putem vedea dac\u0103 tot raportul are o problem\u0103 sau numai anumite grafice din acesta.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Iat\u0103 c\u00e2teva poten\u021biale solu\u021bii care pot fi \u00eencercate atunci c\u00e2nd sunt probleme cu un raport:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Limitarea persoanelor care au acces la raport &#8211; scriam mai sus c\u0103 fiecare utilizator ar putea cere noi pachete de date<\/li>\n\n\n\n<li>Acces redus la date &#8211; utilizatorii pot avea acces la date, dar pot avea acces la acelea\u0219i date, adic\u0103 li se poate reduce dreptul la filtre sau la schimabrea datelor calendaristice<\/li>\n\n\n\n<li>O grij\u0103 sporit\u0103 ar trebui s\u0103 avem utilizarea de <a href=\"https:\/\/webanalyst.ro\/blog\/2022\/data-blending-joins\/\" target=\"_blank\" rel=\"noreferrer noopener\">blended data<\/a>; graficele \u0219i tabelele care folosesc dou\u0103 sau mai multe surse de date afecteaz\u0103 at\u00e2t viteza raportului, c\u00e2t \u0219i consumul de date<\/li>\n\n\n\n<li>Manipularea datelor ar trebui realizat\u0103 \u00een alte platforme, chiar dac\u0103 Looker Studio \u0219i celelalte instrumente de dashboarding au propriile filtre; un raport va dura mai mult, dar va func\u021biona; sunt cazuri \u00een care, pe l\u00e2ng\u0103 Google Analytics \u0219i Looker Studio, va fi nevoie s\u0103 apel\u0103m \u0219i la foi tabelare, data wharehouses \u0219i \/ sau baze de date precum <a href=\"https:\/\/webanalyst.ro\/blog\/2022\/ga4-bigquery\/\" target=\"_blank\" rel=\"noreferrer noopener\">BigQuery<\/a>; desigur, aceste noi instrumente au costurile lor, dar trebuie s\u0103 ne obi\u0219nuim cu asta<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">PS: De la Data Studio la Looker Studio<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A\u0219a cum scriam \u00een octombrie 2022, <a href=\"https:\/\/webanalyst.ro\/blog\/2022\/looker-studio\/\" target=\"_blank\" rel=\"noreferrer noopener\">Data Studio se nume\u0219te acum Looker Studio<\/a>. \u0218tiu c\u0103 majoritatea utilizatorilor \u00eenc\u0103 nu s-au obi\u0219nuit cu schimbarea, a\u0219a c\u0103 am folosit ambele nume \u00een articol.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen sensul schimb\u0103rii, am observat c\u0103 \u0219i URL-ul s-a schimbat de s\u0103pt\u0103m\u00e2na aceasta din datastudio.google.com \u00een <a href=\"https:\/\/lookerstudio.google.com\" target=\"_blank\" rel=\"noreferrer noopener\">lookerstudio.google.com<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>La sf\u00e2r\u0219itul anului 2022, Google a anun\u021bat noi limite pentru datele trimise prin Google Analytics Data API. Primii care au avut probleme sunt cei care preiau datele din Google Analytics 4, \u00een special pentru diverse dashboard-uri. Sunt inclu\u0219i aici \u0219i utilizatorii de Google Data Studio \/ Looker Studio. Multe rapoarte f\u0103cute \u00een Looker Studio nu [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3323,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,867],"tags":[97,925,897],"class_list":["post-3320","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-google-analytics","category-google-data-studio","tag-api","tag-ga4","tag-gaaw"],"_links":{"self":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3320","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=3320"}],"version-history":[{"count":2,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3320\/revisions"}],"predecessor-version":[{"id":3577,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3320\/revisions\/3577"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media\/3323"}],"wp:attachment":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media?parent=3320"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/categories?post=3320"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/tags?post=3320"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}