{"id":14030,"date":"2020-11-26T10:00:41","date_gmt":"2020-11-26T08:00:41","guid":{"rendered":"https:\/\/www.dase-analytics.com\/blog\/?p=14030"},"modified":"2020-11-26T14:08:23","modified_gmt":"2020-11-26T12:08:23","slug":"5-metrik-v-google-analytics-ktorym-malokto-rozumie","status":"publish","type":"post","link":"https:\/\/www.dase-analytics.com\/blog\/sk\/5-metrik-v-google-analytics-ktorym-malokto-rozumie\/","title":{"rendered":"5 metr\u00edk v Google Analytics, ktor\u00fdm m\u00e1lokto rozumie"},"content":{"rendered":"<p><b>Jednou z hlavn\u00fdch v\u00fdhod Google Analytics je jeho jednoduch\u00e1 in\u0161tal\u00e1cia. Zalo\u017e\u00edte si \u00fa\u010det, vygenerovan\u00fd k\u00f3d vlo\u017e\u00edte na web a po\u010das nieko\u013ek\u00fdch min\u00fat zbierate mno\u017estvo d\u00e1t. Ni\u010d komplikovan\u00e9. Probl\u00e9m v\u0161ak nast\u00e1va vtedy, ke\u010f d\u00e1ta a reporty o\u010dividne nesedia a s\u00fa chybn\u00e9. Alebo nie s\u00fa?<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Za chybn\u00e9 reporty \u010di dokonca cel\u00e9 anal\u00fdzy v\u00e4\u010d\u0161inou<\/span><b> vin\u00edme zl\u00fa kvalitu d\u00e1t<\/b><span style=\"font-weight: 400;\">. Mnohokr\u00e1t je v\u0161ak ich probl\u00e9mom chybn\u00e1 interpret\u00e1cia. Pod\u013ea (\u010dasto zav\u00e1dzaj\u00faceho) n\u00e1zvu metriky v reporte si ur\u010d\u00edme, \u010do predstavuje, pri\u010dom jej <\/span><b>re\u00e1lny v\u00fdznam m\u00f4\u017ee by\u0165 trochu odli\u0161n\u00fd<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p>Pozrite si video, kde popisujeme 3 z 5 metr\u00edk:<br \/>\n<iframe loading=\"lazy\" src=\"https:\/\/www.youtube.com\/embed\/tpodnQWG1pM\" width=\"853\" height=\"480\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><\/iframe><\/p>\n<p>&nbsp;<\/p>\n<h2><span style=\"font-weight: 400;\">\u201e<\/span><span style=\"font-weight: 400;\">Blackbox\u201d metriky<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Toto je zjavn\u00e9 najm\u00e4 pri <\/span><span style=\"font-weight: 400;\">\u201e<\/span><span style=\"font-weight: 400;\">blackbox\u201d metrik\u00e1ch, ktor\u00e9 s\u00fa v Google Analytics k dispoz\u00edcii prakticky ihne\u010f, bez potreby ak\u00fdchko\u013evek \u010fal\u0161\u00edch nastaven\u00ed. Na jednej strane z\u00edskavame pr\u00edstup k ve\u013ek\u00e9mu mno\u017estvu d\u00e1t r\u00fdchlo a jednoducho, na druhej s\u00fa <\/span><b>niektor\u00e9 z metr\u00edk vyslovene zradn\u00e9, preto\u017ee nereprezentuj\u00fa presne to, \u010do si pod nimi predstavujeme<\/b><span style=\"font-weight: 400;\">. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Navy\u0161e sa k inform\u00e1ci\u00e1m, ako sa tieto metriky v skuto\u010dnosti r\u00e1taj\u00fa, dost\u00e1va celkom \u0165a\u017eko. Sme vtedy viac-menej <\/span><b>odk\u00e1zan\u00ed na blogy alebo diskusn\u00e9 f\u00f3ra<\/b><span style=\"font-weight: 400;\">, preto\u017ee<\/span> <span style=\"font-weight: 400;\">dokument\u00e1cia priamo od Googlu nie je v mnoh\u00fdch pr\u00edpadoch pr\u00edli\u0161 detailn\u00e1.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h2><span style=\"font-weight: 400;\">1. Sessions (Rel\u00e1cie)<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Rel\u00e1cie s\u00fa popri Hitoch a Pou\u017e\u00edvate\u013eoch jedn\u00fdm z troch <\/span><b>hlavn\u00fdch stavebn\u00fdch blokov organiz\u00e1cie d\u00e1t v Google Analytics<\/b><span style=\"font-weight: 400;\">. Najv\u00e4\u010d\u0161\u00ed vplyv na po\u010det Rel\u00e1ci\u00ed m\u00e1:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">\u010cas trvania rel\u00e1cie (Session Timeout),<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">zdroj n\u00e1v\u0161tevy,<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">prech\u00e1dzanie medzi viacer\u00fdmi dom\u00e9nami,<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">polnoc.<\/span><\/li>\n<\/ul>\n<h3><span style=\"font-weight: 400;\"><br \/>\n\u010cas trvania rel\u00e1cie (Session Timeout)<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">V Google Analytics je t\u00e1to <\/span><b>hodnota prednastaven\u00e1 na 30 min\u00fat<\/b><span style=\"font-weight: 400;\">. \u010co to presne znamen\u00e1? \u010cas trvania rel\u00e1cie predstavuje maxim\u00e1lny \u010das, ktor\u00fd m\u00f4\u017ee ubehn\u00fa\u0165 medzi dvoma hitmi, aby boli tieto Hity st\u00e1le zar\u00e1tan\u00e9 do rovnakej Rel\u00e1cie. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Ak medzi dvoma Hitmi uplynie viac \u010dasu, ako je t\u00e1to hodnota, vznik\u00e1 nov\u00e1 Rel\u00e1cia. To znamen\u00e1, \u017ee <\/span><b>\u010d\u00edm krat\u0161\u00ed \u010cas trvania rel\u00e1cie nastav\u00edme, t\u00fdm viac Rel\u00e1ci\u00ed zaznamen\u00e1me a opa\u010dne<\/b><span style=\"font-weight: 400;\">. Existuj\u00fa v\u0161ak aj \u010fal\u0161ie faktory, ktor\u00e9 vpl\u00fdvaj\u00fa na koniec akt\u00edvnej a za\u010diatok novej Rel\u00e1cie.<\/span><\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"aligncenter size-full wp-image-14036\" src=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/session-settings.png\" alt=\"\" width=\"385\" height=\"383\" srcset=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/session-settings.png 385w, https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/session-settings-150x150.png 150w, https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/session-settings-300x298.png 300w\" sizes=\"(max-width: 385px) 100vw, 385px\" \/><\/p>\n<h3><span style=\"font-weight: 400;\">Zdroj n\u00e1v\u0161tevy<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Nov\u00e1 rel\u00e1cia vznik\u00e1 aj vtedy, ak sa <\/span><b>zmen\u00ed zdroj n\u00e1v\u0161tevy<\/b><span style=\"font-weight: 400;\">. A to aj v pr\u00edpade, ke\u010f sa nov\u00e1 n\u00e1v\u0161teva uskuto\u010dn\u00ed v \u010dasovom \u00faseku rel\u00e1cie (30 min\u00fat). V praxi to m\u00f4\u017ee vyzera\u0165 nasledovne:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Pou\u017e\u00edvate\u013e pr\u00edde na web z organick\u00fdch v\u00fdsledkov vyh\u013ead\u00e1vania, <\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">str\u00e1nku opust\u00ed, <\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">n\u00e1sledne sa o 5 min\u00fat vr\u00e1ti z reklamy, ktor\u00e1 sa mu zobrazila na Facebooku.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Google Analytics tak\u00e9to spr\u00e1vanie vyhodnot\u00ed ako dve rozdielne rel\u00e1cie. <\/span><\/li>\n<\/ol>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">V okamihu prekliku z reklamy vznik\u00e1 nov\u00e1 Rel\u00e1cia, nako\u013eko sa zmenil zdroj z <\/span><i><span style=\"font-weight: 400;\">google\/organic<\/span><\/i><span style=\"font-weight: 400;\"> na <\/span><i><span style=\"font-weight: 400;\">facebook\/cpc<\/span><\/i><span style=\"font-weight: 400;\"> (ak ste to tak ozna\u010dili v UTM parametroch). V takomto pr\u00edpade <\/span><b>za\u010diatok novej rel\u00e1cie nie je \u017eiaden probl\u00e9m<\/b><span style=\"font-weight: 400;\">. Pr\u00e1ve naopak. Nov\u00e1 rel\u00e1cia s nov\u00fdm zdrojom pom\u00f4\u017ee pri vyhodnocovan\u00ed v\u00fdkonnosti jednotliv\u00fdch kan\u00e1lov.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Kedy to v\u0161ak probl\u00e9m je? Napr\u00edklad ak sa <\/span><b>UTM parametre pou\u017e\u00edvaj\u00fa priamo v linkoch na webe<\/b><span style=\"font-weight: 400;\">, ktor\u00e9 odkazuj\u00fa na ten ist\u00fd web (napr\u00edklad v r\u00e1mci intern\u00e9ho promovania produktov). Po\u010das Rel\u00e1cie tak umelo vznik\u00e1 nov\u00e1, pri\u010dom ak pou\u017e\u00edvate\u013e skonvertuje, nebudeme schopn\u00ed t\u00fato konverziu pripradi\u0165 (atribuova\u0165) ku skuto\u010dn\u00e9mu (p\u00f4vodn\u00e9mu) zdroju. <\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Prech\u00e1dzanie medzi viacer\u00fdmi dom\u00e9nami<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Ak v r\u00e1mci jednej n\u00e1v\u0161tevy pou\u017e\u00edvate\u013e prech\u00e1dza viacer\u00fdmi dom\u00e9nami a vy chcete, aby bola zaznamenan\u00e1 len jedna rel\u00e1cia, existuj\u00fa dve mo\u017enosti:<br \/>\n<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>1. V\u0161etky dom\u00e9ny patria v\u00e1m<\/b><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">T\u00e1to situ\u00e1cia nast\u00e1va ke\u010f <\/span><b>pou\u017e\u00edvate\u013e po\u010das svojej n\u00e1v\u0161tevy prech\u00e1dza medzi dvoma alebo viacer\u00fdmi rozdielnymi dom\u00e9nami<\/b><span style=\"font-weight: 400;\"> (nie subdom\u00e9nami). Pr\u00edkladom m\u00f4\u017ee by\u0165 preklik z Landing Page kampane na v\u00e1\u0161 web. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">V takomto pr\u00edpade by rozdelenie Rel\u00e1cie predstavovalo probl\u00e9m, nako\u013eko by sme v pr\u00edpade konverzi\u00ed na hlavnej dom\u00e9ne <\/span><b>neboli schopn\u00ed ur\u010di\u0165 origin\u00e1lny zdroj, ktor\u00fd priviedol pou\u017e\u00edvate\u013ea na Landing Page<\/b><span style=\"font-weight: 400;\">. Aby ste to vyrie\u0161ili, je potrebn\u00e9 <\/span><b>implementova\u0165 cross-domain tracking<\/b> <span style=\"font-weight: 400;\">\u2013<\/span> <a href=\"https:\/\/www.dase-analytics.com\/blog\/ako-na-cross-domain-tracking-kompletny-navod\/\"><span style=\"font-weight: 400;\">\u010dl\u00e1nok, ako na to, pripravil Tom\u00e1\u0161<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><b><\/b><b>2. Iba jedna z dom\u00e9n patr\u00ed v\u00e1m<\/b><\/p>\n<p><span style=\"font-weight: 400;\">T\u00e1to mo\u017enos\u0165 je \u010dast\u00e1 najm\u00e4 pri platbe na eshopoch. Vtedy sa <\/span><b>prech\u00e1dza z dom\u00e9ny eshopu na dom\u00e9nu platobnej br\u00e1ny<\/b><span style=\"font-weight: 400;\">. V tomto pr\u00edpade je tie\u017e ve\u013emi d\u00f4le\u017eit\u00e9, aby sa pri n\u00e1vrate z platobnej br\u00e1ny <\/span><b>neprep\u00edsal zdroj origin\u00e1lnej n\u00e1v\u0161tevy<\/b><span style=\"font-weight: 400;\">. Teda ak nechceme, aby boli v\u0161etky n\u00e1kupy atribuovan\u00e9 zdroju paypal.com\/referral (\u010do, tu\u0161\u00edte spr\u00e1vne, nechceme ;)). Aby sme tomu predi\u0161li, mus\u00edme <\/span><a href=\"https:\/\/www.dase-analytics.com\/blog\/vylucte-vasu-domenu-zo-zoznamu-odkazov-v-google-analytics\/\"><span style=\"font-weight: 400;\">vyl\u00fa\u010di\u0165 tieto dom\u00e9ny zo zoznamu odkazov<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"aligncenter size-large wp-image-14037\" src=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/referral-1024x236.png\" alt=\"\" width=\"1024\" height=\"236\" srcset=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/referral-1024x236.png 1024w, https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/referral-300x69.png 300w, https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/referral.png 1173w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/p>\n<h3><span style=\"font-weight: 400;\">Nastala polnoc<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Taktie\u017e je d\u00f4le\u017eit\u00e9 vedie\u0165, \u017ee <\/span><b>ka\u017ed\u00e1 rel\u00e1cia sa v\u017edy automaticky ukon\u010d\u00ed o polnoci<\/b><span style=\"font-weight: 400;\"> &#8211; pri\u010dom polnoc sa ur\u010duje \u010dasovou z\u00f3nou, ktor\u00e1 je nastaven\u00e1 v nastaveniach Zobrazenia. To znamen\u00e1, \u017ee ak budete ma\u0165 dve Zobrazenia s identick\u00fdmi nastaveniami, ktor\u00e9 sa l\u00ed\u0161ia iba v nastaven\u00ed \u010dasovej z\u00f3ny, budete vidie\u0165 rozdiely v po\u010dte zaznamenan\u00fdch Rel\u00e1ci\u00ed. Preto je<\/span> <span style=\"font-weight: 400;\">nesmierne d\u00f4le\u017eit\u00e9 (ak je to mo\u017en\u00e9) v\u017edy<\/span><b> nastavi\u0165 \u010dasov\u00fa z\u00f3nu pre Zobrazenie tak, aby do nej spadala \u010do najv\u00e4\u010d\u0161ia \u010das\u0165 pou\u017e\u00edvate\u013eov<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h2><span style=\"font-weight: 400;\">2. Users (Pou\u017e\u00edvatelia)<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Google Analytics vysvet\u013euje metriku Pou\u017e\u00edvatelia, ako po\u010det pou\u017e\u00edvate\u013eov, ktor\u00ed nav\u0161t\u00edvili str\u00e1nku v ur\u010ditom \u010dasovom obdob\u00ed. No, ako to u\u017e b\u00fdva, nie je to jednozna\u010dn\u00e9. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Google Analytics identifikuje pou\u017e\u00edvate\u013eov na z\u00e1klade <\/span><b>_ga cookie.<\/b><span style=\"font-weight: 400;\"> Probl\u00e9mom je, \u017ee t\u00e1to cookie je<\/span><b> ulo\u017een\u00e1 na zariaden\u00ed, ktor\u00e9 pou\u017e\u00edvate\u013e aktu\u00e1lne pou\u017e\u00edva<\/b><span style=\"font-weight: 400;\">. E\u0161te presnej\u0161ie, cookie je ulo\u017een\u00e1 v prehliada\u010di, ktor\u00fd pou\u017e\u00edvate\u013e pou\u017e\u00edva. To znamen\u00e1, \u017ee ak jeden pou\u017e\u00edvate\u013e nav\u0161t\u00edvi va\u0161u str\u00e1nku z r\u00f4znych zariaden\u00ed, alebo z r\u00f4znych prehliada\u010dov (hoci aj v r\u00e1mci toho ist\u00e9ho zariadenia), Google Analytics jedn\u00e9ho re\u00e1lneho pou\u017e\u00edvate\u013ea <\/span><span style=\"font-weight: 400;\">\u201e<\/span><span style=\"font-weight: 400;\">zaznamen\u00e1\u201d ako nieko\u013eko pou\u017e\u00edvate\u013eov. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Taktie\u017e, ak sa _ga cookie zma\u017ee, pri \u010fal\u0161ej n\u00e1v\u0161teve sa <\/span><b>vygeneruje nov\u00e1 cookie, a teda nov\u00fd pou\u017e\u00edvate\u013e v Google Analytics<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Viac na t\u00fato t\u00e9mu si m\u00f4\u017eete pre\u010d\u00edta\u0165 <\/span><a href=\"https:\/\/www.dase-analytics.com\/blog\/user-id-vs-client-id-alebo-preco-nie-je-google-analytics-dokonaly\/\"><span style=\"font-weight: 400;\">v \u010dl\u00e1nku o Client a User ID<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><a href=\"https:\/\/www.dase-analytics.com\/blog\/user-id-vs-client-id-alebo-preco-nie-je-google-analytics-dokonaly\/\"><img decoding=\"async\" loading=\"lazy\" class=\"aligncenter wp-image-13614\" src=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/dase-user-id-1024x536.png\" alt=\"\" width=\"481\" height=\"248\" \/><\/a><\/p>\n<h2><span style=\"font-weight: 400;\">3. New Users\/Returning Users (Nov\u00ed\/Vracaj\u00faci sa pou\u017e\u00edvatelia)<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Metrika Nov\u00ed pou\u017e\u00edvatelia je e\u0161te menej intuit\u00edvna ako metrika Pou\u017e\u00edvatelia. Mnoho \u013eud\u00ed ju vysvet\u013euje ako pou\u017e\u00edvate\u013eov, ktor\u00ed nav\u0161t\u00edvili web po prv\u00fdkr\u00e1t. To v\u0161ak nie je pravda.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Ve\u013ek\u00fd vplyv na \u0148u m\u00e1<\/span><b> \u010dasov\u00e9 obdobie<\/b><span style=\"font-weight: 400;\">, ktor\u00e9 je v reporte nastaven\u00e9. Ak sa dan\u00e9 client ID vo vybranom \u010dasovom obdob\u00ed vyskytuje len raz, pou\u017e\u00edvate\u013e bude zapo\u010d\u00edtan\u00fd medzi nov\u00fdch pou\u017e\u00edvate\u013eov. Av\u0161ak, ak \u010dasov\u00e9 obdobie pred\u013a\u017eime tak, \u017ee ten ist\u00fd pou\u017e\u00edvate\u013e bude ma\u0165 v danom obdob\u00ed aspo\u0148 dve rel\u00e1cie, nebude zapo\u010d\u00edtan\u00fd ako nov\u00fd pou\u017e\u00edvate\u013e.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Preto treba by\u0165 pomerne opatrn\u00fd pri reportovan\u00ed toho, ko\u013eko nov\u00fdch pou\u017e\u00edvate\u013eov priniesla dan\u00e1 kampa\u0148. Najm\u00e4 ak sa \u010dasov\u00e9 obdobie nastav\u00ed iba na dobu, po\u010das ktorej bola dan\u00e1 kampa\u0148 akt\u00edvna.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\"><br \/>\n4. Average Time on Page (Priemern\u00fd \u010das na str\u00e1nke)<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Probl\u00e9m tejto metriky je v tom, ak\u00fdm sp\u00f4sobom ju Google Analytics ur\u010duje. V princ\u00edpe ide o rozdiel dvoch \u010dasov. \u010casu, <\/span><b>kedy sa konkr\u00e9tna str\u00e1nka na\u010d\u00edta a \u010dasu posledn\u00e9ho interakt\u00edvneho eventu, ktor\u00fd sa odoslal<\/b><span style=\"font-weight: 400;\">. Ke\u010f teda rel\u00e1cia pozost\u00e1va len z nav\u0161t\u00edvenia jednej str\u00e1nky (rel\u00e1cia = bounce) a pou\u017e\u00edvate\u013e nepokra\u010duje na \u010fal\u0161iu, Google Analytics nem\u00e1 k dispoz\u00edcii druh\u00fd hit, na z\u00e1klade ktor\u00e9ho by ur\u010dil \u010das str\u00e1ven\u00fd na str\u00e1nke. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Tak\u00e9to spr\u00e1vanie je <\/span><b>be\u017en\u00e9 najm\u00e4 pri blogov\u00fdch \u010dl\u00e1nkoch<\/b><span style=\"font-weight: 400;\">. Ak je teda rel\u00e1cia = bounce, nebudeme schopn\u00ed ur\u010di\u0165 \u010das, ktor\u00fd na tejto blogovej str\u00e1nke pou\u017e\u00edvatelia str\u00e1vili. \u010cas na str\u00e1nke tie\u017e nebudeme schopn\u00ed ur\u010di\u0165 pre posledn\u00fa str\u00e1nku rel\u00e1cie (Exit page).<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u010eal\u0161\u00edm probl\u00e9mom tejto metriky je, \u017ee Priemern\u00fd \u010das na str\u00e1nke sa zvy\u0161uje aj vtedy, ke\u010f je str\u00e1nka zobrazen\u00e1 v neakt\u00edvnom tabe. Pravdepodobne m\u00e1te aj teraz otvoren\u00fdch nieko\u013eko tabov. \u010cas na str\u00e1nke sa v\u0161ak zvy\u0161uje pre v\u0161etky str\u00e1nky rovnako, hoci \u010d\u00edtate tento \u010dl\u00e1nok.<\/span><\/p>\n<p><b>Zatia\u013e \u010do priemern\u00fd \u010das na str\u00e1nke sa ner\u00e1ta z bouncov a z posledn\u00fdch str\u00e1nok, priemern\u00e9 trvanie rel\u00e1cie prira\u010fuje v\u0161etk\u00fdm bounce rel\u00e1ci\u00e1m \u010das 0 sek\u00fand.\u00a0<\/b><a href=\"https:\/\/www.dase-analytics.com\/blog\/realny-cas-straveny-na-stranke\/\"><span style=\"font-weight: 400;\">Tento \u010dl\u00e1nok od Majky<\/span><\/a><span style=\"font-weight: 400;\"> sa venuje vyslovene tejto metrike a tie\u017e poskytuje n\u00e1vod, ako docieli\u0165 jej presnej\u0161ie meranie.<\/span><\/p>\n<p><a href=\"https:\/\/www.dase-analytics.com\/blog\/realny-cas-straveny-na-stranke\/\"><img decoding=\"async\" loading=\"lazy\" class=\"aligncenter wp-image-14024\" src=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/obrazky-k-\u010dl\u00e1nkom2-1024x536.png\" alt=\"Re\u00e1lny \u010das str\u00e1ven\u00fd na str\u00e1nke\" width=\"488\" height=\"250\" \/><\/a><\/p>\n<h2><span style=\"font-weight: 400;\">5. Product Checkouts<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">V pr\u00edpade, \u017ee ste sa pustili do <\/span><b>implement\u00e1cie Enhanced Ecommerce<\/b><span style=\"font-weight: 400;\">, zrejme budete pozna\u0165 metriku <\/span><b>Product Checkouts<\/b><span style=\"font-weight: 400;\">. Metrika hovor\u00ed o tom, ko\u013ekokr\u00e1t sa dan\u00fd produkt nach\u00e1dzal v n\u00e1kupnom procese. Menej \u013eud\u00ed v\u0161ak vie, \u017ee na to, aby bola t\u00e1to metrika pre dan\u00fd produkt zapo\u010d\u00edtan\u00e1, sa mus\u00ed nach\u00e1dza\u0165 v zozname produktov u\u017e <\/span><b>v prvom kroku n\u00e1kupn\u00e9ho procesu<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Ner\u00e1taj\u00fa sa tam teda produkty, ktor\u00e9 sa prid\u00e1vaj\u00fa do <\/span><span style=\"font-weight: 400;\">\u201e<\/span><span style=\"font-weight: 400;\">ko\u0161\u00edka\u201d v neskor\u0161\u00edch krokoch n\u00e1kupn\u00e9ho procesu. \u010casto ide o poistenie alebo in\u00e9 dodato\u010dn\u00e9 produkty a slu\u017eby, ktor\u00e9 nemus\u00edte do merania prid\u00e1va\u0165. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">M\u00f4\u017eu sa tu v\u0161ak objavi\u0165 aj<\/span><b> be\u017en\u00e9 produkty, ktor\u00e9 sa v r\u00e1mci intern\u00e9ho promovania zobrazuj\u00fa v neskor\u0161\u00edch krokoch<\/b><span style=\"font-weight: 400;\"> (alebo tesne pred dokon\u010den\u00edm n\u00e1kupu). V tomto pr\u00edpade nast\u00e1va probl\u00e9m a pre takto pridan\u00fd produkt nebude metrika Product Checkouts zapo\u010d\u00edtan\u00e1, ke\u010f\u017ee v prvom kroku sa tento produkt nenach\u00e1dzal.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u010eal\u0161\u00edm probl\u00e9mom m\u00f4\u017ee by\u0165, ak<\/span><b> prv\u00fd krok odosielame u\u017e pri n\u00e1h\u013eade ko\u0161\u00edka<\/b><span style=\"font-weight: 400;\">. V tomto pr\u00edpade budeme ma\u0165, oproti metrike Add to Cart, <\/span><b>neprimerane vysok\u00fa metriku<\/b> <b>Product Checkouts.<\/b><\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">Ak m\u00e1te nejak\u00e9 ot\u00e1zky o zvl\u00e1\u0161tnych metrik\u00e1ch alebo ich kombin\u00e1cii s dimenziami, pode\u013ete sa s nimi v koment\u00e1roch pod \u010dl\u00e1nkom. \ud83d\ude42<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Jednou z hlavn\u00fdch v\u00fdhod Google Analytics je jeho jednoduch\u00e1 in\u0161tal\u00e1cia. Zalo\u017e\u00edte si \u00fa\u010det, vygenerovan\u00fd k\u00f3d vlo\u017e\u00edte na web&#8230;<\/p>\n","protected":false},"author":62,"featured_media":16454,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[637],"tags":[],"_links":{"self":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/14030"}],"collection":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/users\/62"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/comments?post=14030"}],"version-history":[{"count":12,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/14030\/revisions"}],"predecessor-version":[{"id":16908,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/14030\/revisions\/16908"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media\/16454"}],"wp:attachment":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media?parent=14030"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/categories?post=14030"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/tags?post=14030"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}