{"id":13604,"date":"2017-08-03T10:14:02","date_gmt":"2017-08-03T08:14:02","guid":{"rendered":"https:\/\/www.dase-analytics.com\/blog\/?p=13604"},"modified":"2020-01-23T18:00:07","modified_gmt":"2020-01-23T16:00:07","slug":"user-id-vs-client-id-alebo-preco-nie-je-google-analytics-dokonaly","status":"publish","type":"post","link":"https:\/\/www.dase-analytics.com\/blog\/sk\/user-id-vs-client-id-alebo-preco-nie-je-google-analytics-dokonaly\/","title":{"rendered":"User ID vs. Client ID alebo pre\u010do nie je Google Analytics dokonal\u00fd?"},"content":{"rendered":"

Na vysvetlenie tejto t\u00e9my si na za\u010diatok prejdeme z\u00e1klady fungovania Google Analytics, a teda jeho stavebn\u00e9 bloky. Google Analytics vyu\u017e\u00edva na organiz\u00e1ciu d\u00e1t 3 jednoduch\u00e9 komponenty: <\/span>Pou\u017e\u00edvate\u013eov<\/a>, Rel\u00e1cie<\/a><\/b> a\u00a0<\/span>Interakcie<\/b><\/a>. Tieto komponenty maj\u00fa medzi sebou vz\u0165ah a hierarchiu, ktor\u00fa m\u00f4\u017eete vidie\u0165 na obr\u00e1zku:<\/span><\/p>\n

\"\"<\/p>\n

Interakcie <\/b>(alebo hity) s\u00fa interakcie s Google Analytics scriptom. Spadaj\u00fa sem Pageviews<\/a> (zobrazenia str\u00e1nky), Eventy<\/a> a Transakcie.<\/span><\/p>\n

Rel\u00e1cia <\/b>je ur\u010dit\u00e9 mno\u017estvo interakci\u00ed z toho ist\u00e9ho zariadenia, zoskupen\u00e9 do jedn\u00e9ho \u010dasov\u00e9ho \u00faseku, v ktorom sa vykonali. V \u0161tandardnej konfigur\u00e1cii Google Analytics je nastaven\u00fd maxim\u00e1lny \u010dasov\u00fd r\u00e1mec medzi t\u00fdmito interakciami pre jednu rel\u00e1ciu 30 min\u00fat. Ak sa nevykon\u00e1 v tomto r\u00e1mci \u010fal\u0161ia interakcia, rel\u00e1cia kon\u010d\u00ed a po vykonan\u00ed interakcie za\u010d\u00edna nov\u00e1 rel\u00e1cia.<\/span><\/p>\n

Pou\u017e\u00edvatelia <\/b>s\u00fa rel\u00e1cie od t\u00fdch ist\u00fdch pou\u017e\u00edvate\u013eov spojen\u00e9 dokopy. Av\u0161ak, je potrebn\u00e9 pochopi\u0165 obmedzenia Google Analytics pre rozpoznanie pou\u017e\u00edvate\u013ea. Bez \u0161peci\u00e1lnej konfigur\u00e1cie (o ktorej budeme \u010falej v \u010dl\u00e1nku p\u00edsa\u0165), je pou\u017e\u00edvate\u013eov lep\u0161ie pomenova\u0165 ako \u201ezariadenia\u201c, preto\u017ee Google Analytics funguje na princ\u00edpe cookies<\/a>. T\u00fdm p\u00e1dom nevie automaticky sp\u00e1rova\u0165 r\u00f4zne zariadenia jedn\u00e9ho pou\u017e\u00edvate\u013ea (napr. laptop a mobiln\u00fd telef\u00f3n).<\/span><\/p>\n

\u010ci\u017ee pokia\u013e pou\u017e\u00edvate\u013e pr\u00edde na str\u00e1nku, na ktorej je umiestnen\u00fd Google Analytics a nech\u00e1 si ju v prehliada\u010di bez akcie otvoren\u00fa viac ako 30 min\u00fat a n\u00e1sledne sa niekde \u010falej preklikne, za\u010dne sa nov\u00e1 rel\u00e1cia. Aj ke\u010f nikdy zo str\u00e1nky neodi\u0161iel. Prv\u00e1 nedokonalos\u0165 Google Analytics. \ud83d\ude42<\/span><\/p>\n

Samozrejme, medzi komponenty patria e\u0161te aj <\/span>Produkty<\/b>, ale o t\u00fdch si nap\u00ed\u0161eme inokedy. \ud83d\ude42<\/span><\/p>\n

Cookies<\/b><\/h2>\n

Google Analytics funguje na princ\u00edpe cookies. Pou\u017e\u00edvate\u013e (zariadenie) pr\u00edde na str\u00e1nku, na ktorej je implementovan\u00fd Google Analytics. Script n\u00e1sledne zist\u00ed, \u010di zariadenie u\u017e jeho cookie obsahuje. Ak nie, do prehliada\u010da mu t\u00fato cookie vlo\u017e\u00ed, ak \u00e1no, na z\u00e1klade vlo\u017eenej cookie rozpozn\u00e1, ak\u00e9mu u\u017e\u00edvate\u013eovi m\u00e1 t\u00fato rel\u00e1ciu priradi\u0165. Ako? Na z\u00e1klade <\/span>Client ID.<\/b>
\n\"GA<\/p>\n

Na obr\u00e1zku m\u00f4\u017eete vidie\u0165, ako tak\u00e1to cookie vyzer\u00e1. Medzi in\u00fdmi vecami v sebe obsahuje: <\/span><\/p>\n

N\u00e1zov<\/b>: jednoducho n\u00e1zov cookie. Universal Google Analytics pou\u017e\u00edva <\/span>_ga<\/span><\/i>.<\/span><\/p>\n

Hodnotu<\/b>: tu sa naj\u010dastej\u0161ie uv\u00e1dza to najd\u00f4le\u017eitej\u0161ie: v pr\u00edpade Google Analytics cookie to je tak\u00fdto form\u00e1t, ktor\u00fd si \u010falej vysvetl\u00edme.<\/span><\/p>\n

Dom\u00e9nu<\/b>: dom\u00e9nu, na ktorej bola cookie umiestnen\u00e1 a ktor\u00e1 ju m\u00f4\u017ee pre\u010d\u00edta\u0165.<\/span><\/p>\n

Cestu<\/b>: cestu, pre ktor\u00fa bola cookie umiestnen\u00e1. Pokia\u013e je uveden\u00e9 iba <\/span>\/<\/span><\/i> , cookie bude pr\u00edtomn\u00e1 na celom webe. Pokia\u013e by bolo uveden\u00e9 napr. <\/span>\/blog<\/span><\/i> , cookie bude pr\u00edtomn\u00e1 iba na str\u00e1nkach obsahuj\u00facich <\/span>\/blog<\/span><\/i>.<\/span><\/p>\n

Expir\u00e1ciu<\/b>: d\u00e1tum, do ktor\u00e9ho ak sa cookie neobnov\u00ed, tak jednoducho zanikne a zma\u017ee sa.<\/span><\/p>\n

A \u010do sa stane v pr\u00edpade, ak si u\u017e\u00edvate\u013e vo svojom prehliada\u010di zma\u017ee cookies?<\/span><\/p>\n

\"delete<\/p>\n

Pri \u010fal\u0161ej n\u00e1v\u0161teve mu bude jednoducho pridelen\u00e1 nov\u00e1 Google Analytics cookie s nov\u00fdm Client ID, tak\u017ee sa v Google Analytics preh\u013eadoch bude spr\u00e1va\u0165 ako nov\u00fd pou\u017e\u00edvate\u013e.<\/span><\/p>\n

Client ID<\/b><\/h2>\n

Ka\u017ed\u00e1 Google Analytics cookie teda obsahuje tak\u00fato hodnotu (samozrejme, \u010d\u00edsla sa menia). \u010co jednotliv\u00e9 \u010dasti znamenaj\u00fa?<\/span><\/p>\n

\"client<\/p>\n

GA1<\/b> \u2013 toto sa nemen\u00ed. Ide skr\u00e1tka o GA verziu \u010d\u00edslo 1.<\/span><\/p>\n

2<\/b> \u2013 ak bola cookie vlo\u017een\u00e1 na dom\u00e9ne <\/span>.dase-analytics.com<\/span><\/i>, \u010d\u00edslo bude 2. Ak by bola vlo\u017een\u00e1 na <\/span>.subdomena.dase-analytics.com<\/span><\/i>, \u010d\u00edslo bude 3. V skratke ide o po\u010det komponentov v dom\u00e9ne oddelen\u00fdch bodkami. <\/span><\/p>\n

303899533 <\/b>\u2013 n\u00e1hodne vygenerovan\u00e9 \u010d\u00edslo.<\/span><\/p>\n

1501248220 <\/b>\u2013 takzvan\u00fd timestamp. Ide o presn\u00fd d\u00e1tum, ke\u010f bola cookie do prehliada\u010da vlo\u017een\u00e1. Ide o sekundy, ktor\u00e9 uplynuli od 1.1.1970. V na\u0161om pr\u00edpade je to po dek\u00f3dovan\u00ed: Fri, 28 Jul 2017 15:23:40 +02:00.<\/span><\/p>\n

Tieto dve posledn\u00e9 \u010disla, teda n\u00e1hodne vygenerovan\u00e9 \u010d\u00edslo spolu s timestamp, tvoria <\/span>Client ID<\/b>.<\/span><\/p>\n

Na \u010do sa teda d\u00e1 Client ID vyu\u017ei\u0165? Jedna z mo\u017enost\u00ed je pri Cross-Domain meran\u00ed. To, \u010do sa v skratke v tomto pr\u00edpade deje: str\u00e1nka A po prekliknut\u00ed na str\u00e1nku B zo svojej cookie odovzd\u00e1 Client ID str\u00e1nke B. Deje sa to v URL a Google Analytics si na str\u00e1nke B toto Client ID z URL pre\u010d\u00edta a rel\u00e1ciu pridel\u00ed rovnak\u00e9mu pou\u017e\u00edvate\u013eovi ako na str\u00e1nke A. Samozrejme, za predpokladu, \u017ee na oboch str\u00e1nkach m\u00e1me rovnak\u00fd Google Analytics merac\u00ed k\u00f3d. Ako si nastavi\u0165 tak\u00e9to Cross-Domain meranie si podrobnej\u0161ie prejdeme v \u010fal\u0161om \u010dl\u00e1nku. \ud83d\ude42<\/span><\/p>\n

User ID<\/b><\/h2>\n

Predstavte si nasleduj\u00facu situ\u00e1ciu:<\/span><\/p>\n

Ide o jedn\u00e9ho \u010dloveka, ktor\u00fd pri prvej rel\u00e1cii pri\u0161iel na va\u0161u str\u00e1nku na priamo, druh\u00fdkr\u00e1t cez porovn\u00e1va\u010d a tret\u00edkr\u00e1t cez platen\u00e9 vyh\u013ead\u00e1vanie, a nak\u00fapil. Ko\u013eko pou\u017e\u00edvate\u013eov v Google Analytics v tomto pr\u00edpade bude tento \u010dlovek predstavova\u0165?<\/span><\/p>\n

\"user<\/p>\n

To nebolo ta\u017ek\u00e9 \u2013 jedn\u00e9ho.<\/span><\/p>\n


\n<\/span>Ako to v\u0161ak bude vyzera\u0165 v tomto pr\u00edpade, ke\u010f pri druhej rel\u00e1cii pri\u0161iel cez mobil?<\/span>
\n\"user<\/p>\n

V tomto pr\u00edpade bude predstavova\u0165 dvoch pou\u017e\u00edvate\u013eov, aj ke\u010f ide o jedn\u00e9ho \u010dloveka. Takto \u00faplne str\u00e1came ve\u013emi d\u00f4le\u017eit\u00fa \u010das\u0165 konverznej cesty a ch\u00fdbaj\u00fa n\u00e1m \u00fadaje, aby sme mohli vyhodnoti\u0165 \u00faspe\u0161nos\u0165 invest\u00edci\u00ed do porovn\u00e1va\u010da. <\/span><\/p>\n

To ist\u00e9 by sa udialo v nasleduj\u00facom scen\u00e1ri, ke\u010f s\u00edce jeden a ten ist\u00fd \u010dlovek pristupuje z toho ist\u00e9ho zariadenia, ale cez r\u00f4zne prehliada\u010de:<\/span><\/p>\n

\"user<\/p>\n

Ako teda zlep\u0161i\u0165 na\u0161e d\u00e1ta? Pomocou spom\u00ednan\u00e9ho <\/span>User ID<\/b>.<\/span><\/p>\n

Aby ste User ID mohli pou\u017e\u00edva\u0165, potrebujete ma\u0165 pre pou\u017e\u00edvate\u013eov na str\u00e1nke login syst\u00e9m, kde sa m\u00f4\u017eu prihl\u00e1si\u0165. N\u00e1sledne nie\u010do m\u00e1lo nastavovania v k\u00f3de str\u00e1nky a v Google Analytics, pr\u00edpadne aj Google Tag Manageri (ktor\u00e9 si taktie\u017e prejdeme v \u010fal\u0161om \u010dl\u00e1nku) a v\u00fdsledok bude nasleduj\u00faci:<\/span><\/p>\n

V\u017edy, ke\u010f sa u\u017e\u00edvate\u013e na va\u0161ej str\u00e1nke prihl\u00e1si, str\u00e1nka odo\u0161le jeho ID, ktor\u00e9 je pridelen\u00e9 jeho prihlasovaciemu menu do Google Analytics. Ak sa teda u\u017e\u00edvate\u013e prihl\u00e1si najprv napr. cez po\u010d\u00edta\u010d a nesk\u00f4r cez mobil, v oboch pr\u00edpadoch sa odo\u0161le rovnak\u00e9 ID a Google Analytics t\u00fdchto pou\u017e\u00edvate\u013eov (zariadenia) bude vedie\u0165 spoji\u0165 do jedn\u00e9ho.<\/span><\/p>\n

Treba v\u0161ak poznamena\u0165, \u017ee aj po aktiv\u00e1cii tejto funkcie a prihl\u00e1sen\u00ed pou\u017e\u00edvate\u013ea, sa mu minul\u00e9 rel\u00e1cie sp\u00e4tne neprepoja. Prepojen\u00e9 bud\u00fa iba tie rel\u00e1cie, pri ktor\u00fdch je User ID pr\u00edtomn\u00fd. Google Analytics toti\u017eto nevie sp\u00e4tne meni\u0165 u\u017e raz zap\u00edsan\u00e9 d\u00e1ta.<\/span><\/p>\n

Po aktiv\u00e1cii funkcie a spr\u00e1vneho nastavenia v\u00e1m v \u00fa\u010dte pribudn\u00fa napr. tak\u00e9to preh\u013eady, kde m\u00f4\u017eete vidie\u0165 prieniky zariaden\u00ed, z ktor\u00fdch sa pou\u017e\u00edvatelia prihlasuj\u00fa:<\/span><\/p>\n

\"\"<\/p>\n

Alebo aj naj\u010dastej\u0161ie kombin\u00e1cie zariaden\u00ed:<\/span><\/p>\n

\"\"<\/p>\n

Budem r\u00e1d, ak pod \u010dl\u00e1nok nap\u00ed\u0161ete, \u010di Client ID alebo User ID vyu\u017e\u00edvate, a ak\u00e9 m\u00e1te s nimi sk\u00fasenosti. \ud83d\ude42<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Na vysvetlenie tejto t\u00e9my si na za\u010diatok prejdeme z\u00e1klady fungovania Google Analytics, a teda jeho stavebn\u00e9 bloky. Google…<\/p>\n","protected":false},"author":67,"featured_media":13614,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[200],"tags":[603,601,604,162,602,600,372],"_links":{"self":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/13604"}],"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\/67"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/comments?post=13604"}],"version-history":[{"count":15,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/13604\/revisions"}],"predecessor-version":[{"id":15124,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/13604\/revisions\/15124"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media\/13614"}],"wp:attachment":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media?parent=13604"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/categories?post=13604"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/tags?post=13604"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}