{"id":3711,"date":"2024-01-24T20:29:24","date_gmt":"2024-01-24T18:29:24","guid":{"rendered":"https:\/\/webanalyst.ro\/?p=3711"},"modified":"2024-01-25T09:46:22","modified_gmt":"2024-01-25T07:46:22","slug":"ga4-calculated-metrics","status":"publish","type":"post","link":"https:\/\/webanalyst.ro\/blog\/2024\/ga4-calculated-metrics\/","title":{"rendered":"Metrice calculate \u00een GA4"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Anul trecut, Google a anun\u021bat c\u0103 introduce <em><strong>calculated metrics<\/strong><\/em> \u00een ultima sa versiune de analytics. Acestea au fost disponibile \u00een majoritatea conturilor de Google Analytics \u00een jurul vacan\u021bei de iarn\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">S\u0103pt\u0103m\u00e2na aceasta, calculated metrics management a devenit disponibil \u0219i \u00een Google Analytics Admin API. Deocamdat\u0103 le avem \u00een versiunea afla de API, dar asta \u00eenseamn\u0103 c\u0103 \u00een cur\u00e2nd vor fi disponibile \u0219i \u00een versiunea final\u0103, deci trebuie s\u0103 ne preg\u0103tim.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00centre timp, putem crea \u0219i administra metricele calculate din interfa\u021ba Google Analytics 4. Voi detalia \u00een continuarea acestui articol.<\/p>\n\n\n\n<!--more-->\n\n\n\n<h2 class=\"wp-block-heading\">Ce sunt Metricele Calculate<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Instrumentele de digital analytics \u00eencearc\u0103 s\u0103 vin\u0103 cu cele mai bune metrice pentru a m\u0103sura performa\u021ba website-urilor \u0219i a aplica\u021biilor digitale. Totu\u0219i, ca utilizator po\u021bi observa c\u0103 ai nevoie s\u0103 calculezi anumite lucruri care nu sunt disponibile. A\u0219a au ap\u0103rut metricele calculate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Metricele calculate sunt metrice pe care le po\u021bi ad\u0103uga celor existente \u00een Google Analytics 4, combin\u00e2nd metrice existente. Partea bun\u0103 este c\u0103 pot fi folosite \u0219i metricele personalizate (<em>custom metrics<\/em>) la crearea de metrice calculate.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cum putem ad\u0103uga metrice calculate \u00een GA4<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen primul r\u00e2nd, pentru a crea o nou\u0103 metric\u0103, trebuie s\u0103 fii administrator sau editor al propriet\u0103\u021bii de Google Analytics.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Putem crea maxim 5 metrice calculate \u00eentr-o proprietate standard (gratuit\u0103) de Google Analytics 4 \u0219i p\u00e2n\u0103 la 50 de metrice calculate \u00een propriet\u0103\u021bile Google Analytics 360 (pl\u0103tite, cunoscute anterior drept <em>premium<\/em>).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ultima limitare de la Google ne limiteaz\u0103 s\u0103 calcul\u0103m o metric\u0103 pe baza altei metrice calculate. P\u00e2n\u0103 la urm\u0103, este un lucru normal, av\u00e2nd \u00een vedere c\u0103 prima metric\u0103 se poate modifica sau poate disp\u0103rea oric\u00e2nd.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Acum c\u0103 \u0219tim care sunt limitele, putem merge \u00een sec\u021biunea de Admin a propriet\u0103\u021bii de Google Analytics \u0219i de acolo \u00een sec\u021biunea <strong>Custom definitions<\/strong>. Aceast\u0103 pagin\u0103 are 3 tab-uri \u00een partea de sus: <em>Custom dimensions<\/em>, <em>Custom metrics<\/em> \u0219i, mai nou, <em><strong>Calculated metrics<\/strong><\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Acces\u00e2nd Calculated metrics, vom avea o eventual\u0103 lista cu metrice calculate (pot fi create de al\u021bi administraori sau editori ai propriet\u0103\u021bii de analytics). Tot aici avem \u0219i un buton cu textul <strong>Create calculated metric<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Urmeaz\u0103 un formular \u00een care trebuie s\u0103 definim noua metric\u0103, cu urm\u0103toarele c\u00e2mpuri:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Name<\/strong> &#8211; numele metricii, este cel care va ap\u0103rea \u00een rapoarte \u0219i dup\u0103 care o vom c\u0103uta \u00een lista de metrice; este un c\u00e2mp obligatoriu<\/li>\n\n\n\n<li><strong>API name<\/strong> &#8211; se populeaz\u0103 automat, plec\u00e2nd de la numele primit \u00een c\u00e2mpul anterior<\/li>\n\n\n\n<li><strong>Description<\/strong> &#8211; este un c\u00e2mp op\u021bional, dar este recomandat s\u0103 scriem un text care ne va ajuta mai t\u00e2rziu, c\u00e2nd vrem s\u0103 ne amintim detalii despre metric\u0103<\/li>\n\n\n\n<li><strong>Formula<\/strong> &#8211; este cel mai important c\u00e2mp; putem folosi majoritatea metricelor standard \u0219i personalizate, dar \u0219i operatori matematici (+, -, *, \/), paranteze pentru ordinea opera\u021biilor \u0219i valori numerice (totu\u0219i, nu va merge dac\u0103 punem doar valori numerice)<\/li>\n\n\n\n<li><strong>Unit of measurement<\/strong> &#8211; arat\u0103 cum va fi prezentat\u0103 metrica \u00een rapoarte \u0219i avem de ales dintre Standard, Valut\u0103, unit\u0103\u021bi pentru distan\u021b\u0103 (pa\u0219i, mile, metri, kilometri) \u0219i unit\u0103\u021bi pentru timp (milisecunde, secunde, minute, ore).<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Exemple de Metrice Calculate<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Partea bun\u0103 este c\u0103 fiecare dintre noi are nevoie de alte metrice calculate, dar putem pleca de la c\u00e2teva idei:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Veniturile \u00een diverse monede<\/strong> &#8211; putem calcula u\u0219or veniturile \u00een RON sau EUR, mai ales c\u0103 \u00een ultimii ani nu am avut curs valutar cu fluctua\u021bii majore; pe de alt\u0103 parte, aceste metrice ar fi doar estimative, av\u00e2nd \u00een vedere c\u0103 pe terme lung nu avem un curs valutar constant<\/li>\n\n\n\n<li><strong>Procent de utlizatori noi<\/strong> &#8211; nu exist\u0103 \u00een GA4, dar se poate calcula simplu, dac\u0103 decidem s\u0103 folosim una dintre metricele calculate pentru asta; formula este ({New users}\/{Total users})*100<\/li>\n\n\n\n<li><strong>Checkout rate pt utilizatori noi<\/strong> &#8211; putem calcula Checkout rate doar pentru un grup de utilizatori, dac\u0103 \u00eei avem deja delimita\u021bi dup\u0103 o dimensiune; \u00een exemplul nostru, plec\u0103m de la utilizatorii noi, caz \u00een care formula este {New Users}\/{Checkouts}*100<\/li>\n\n\n\n<li><strong>Rata de scroll pentru utilizatori<\/strong> &#8211; ne arat\u0103 procentul utilizatorilor care au dat scroll, iar formula este {Scrolled users}\/{Total users}*100<\/li>\n\n\n\n<li><strong>Rata de conversie pentru ecommerce, la nivel de utilizatori sau de sesiuni<\/strong> &#8211; unii vor spune c\u0103 avem ace\u0219ti indicatori \u00een API \u0219i este corect; \u00eei putem accesa u\u0219or din <a href=\"https:\/\/webanalyst.ro\/blog\/sectiune\/google-data-studio\/\" target=\"_blank\" rel=\"noreferrer noopener\">Google Looker Studio<\/a> sau din <a href=\"https:\/\/webanalyst.ro\/blog\/tag\/power-bi\/\" target=\"_blank\" rel=\"noreferrer noopener\">Microsoft Power BI<\/a>, \u00eens\u0103 nu avem aceast\u0103 posibilitate \u00een interfa\u021ba din Google Analytics, a\u0219a c\u0103 am vrut s\u0103 am \u0219i aici indicatorii, \u00een special pentru Explorations; pentru raportarea la sesiuni, formula este {Ecommerce purchases}\/{Sessions}*100<\/li>\n\n\n\n<li><strong>AOV sau valoarea medie a comenzii<\/strong> &#8211; este una dintre principalii KPIs \u00een eCommerce, iar formula metricei \u00een GA4 este {Gross item revenue}\/{Transactions}. Aten\u021bie, spre deosebire de metricele anterioare, unitatea de m\u0103sur\u0103 de aici nu mai este standard, ci valut\u0103 (<em>Currency<\/em>)<\/li>\n\n\n\n<li><strong>Veniturile la nivel produs dup\u0103 retur<\/strong> &#8211; dac\u0103 ave\u021bi implementate comenzile returnate \u00een Google Analytics 4, ar fi interesant de calculat suma \u00eencasat\u0103 de un produs, dar f\u0103r\u0103 unit\u0103\u021bile returnate, formula fiind {Gross item revenue}-{Item refund amount}. \u0218i aici exprim\u0103m unitatea tot \u00een <em>currency<\/em><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Metrice calculate \u00een API<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Scriam mai sus c\u0103 metricele calculate \u00eencep s\u0103 fie disponibile \u0219i prin Google Analytics API.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Metodele disponibile pentru <code>properties.calculatedMetrics<\/code> sunt <code>get<\/code>, <code>delete<\/code>, <code>get<\/code>, <code>list<\/code> \u0219i <code>patch<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">C\u00e2mpurile pe care le putem accesa prin API sunt <code>name<\/code>, <code>description<\/code>, <code>display_name<\/code>, <code>calculated_metric_id<\/code>, <code>metric_unit<\/code>, <code>restricted_metric_type[]<\/code>, <code>formula<\/code> \u0219i <code>invalid_metric_reference<\/code> (ultimul este un <em>boolean<\/em>, iar dac\u0103 are valoarea <code>True<\/code>, \u00eenseamn\u0103 c\u0103 avem de-a face cu o metric\u0103 cu referin\u021b\u0103 invalid\u0103).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen final, metricele calculate sunt o func\u021bionalitate bine-venit\u0103. Chiar \u0219i \u00een versiunile vechi de Google Analytics, aceast\u0103 func\u021bionalitate a fost introdus\u0103 t\u00e2rziu, mai exact \u00een <a href=\"https:\/\/webanalyst.ro\/blog\/2015\/google-analytics-in-2015\/\" target=\"_blank\" rel=\"noreferrer noopener\">noiembrie 2015<\/a>. \u00cen Google Analytics 4, calculated metrics sunt disponibile \u00een rapoartele standard, \u00een rapoartele personalizate (<em><a href=\"https:\/\/webanalyst.ro\/blog\/2022\/explorations-rapoarte-personalizate\/\" target=\"_blank\" rel=\"noreferrer noopener\">Explorations<\/a><\/em>) \u0219i prin API.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Anul trecut, Google a anun\u021bat c\u0103 introduce calculated metrics \u00een ultima sa versiune de analytics. Acestea au fost disponibile \u00een majoritatea conturilor de Google Analytics \u00een jurul vacan\u021bei de iarn\u0103. S\u0103pt\u0103m\u00e2na aceasta, calculated metrics management a devenit disponibil \u0219i \u00een Google Analytics Admin API. Deocamdat\u0103 le avem \u00een versiunea afla de API, dar asta \u00eenseamn\u0103 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3712,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[925,897,15],"class_list":["post-3711","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-google-analytics","tag-ga4","tag-gaaw","tag-metrics"],"_links":{"self":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3711","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=3711"}],"version-history":[{"count":3,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3711\/revisions"}],"predecessor-version":[{"id":3719,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3711\/revisions\/3719"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media\/3712"}],"wp:attachment":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media?parent=3711"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/categories?post=3711"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/tags?post=3711"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}