{"id":17988,"date":"2021-11-10T16:49:41","date_gmt":"2021-11-10T14:49:41","guid":{"rendered":"https:\/\/www.dase-analytics.com\/blog\/?p=17988\/"},"modified":"2021-11-10T16:49:41","modified_gmt":"2021-11-10T14:49:41","slug":"identifikacia-pouzivatela-v-prostredi-google-analytics","status":"publish","type":"post","link":"https:\/\/www.dase-analytics.com\/blog\/sk\/identifikacia-pouzivatela-v-prostredi-google-analytics\/","title":{"rendered":"Identifik\u00e1cia pou\u017e\u00edvate\u013ea v prostred\u00ed Google Analytics 4"},"content":{"rendered":"<p><strong>V\u00e4\u010d\u0161ina z\u00e1kazn\u00edkov interaguje s va\u0161\u00edm webom, \u010di aplik\u00e1ciou prostredn\u00edctvom viacer\u00fdch zariaden\u00ed, \u010di prehliada\u010dov. Niekto si napr. r\u00e1no m\u00f4\u017ee pozrie\u0165 v\u00e1\u0161 e-shop na tablete, nesk\u00f4r na obed si urob\u00ed podrobnej\u0161\u00ed prieskum na PC v pr\u00e1ci, aby si nakoniec ve\u010der objednal v\u00e1\u0161 produkt, \u010di slu\u017ebu na svojom telef\u00f3ne. <\/strong><strong>Ka\u017ed\u00e1 z t\u00fdchto aktiv\u00edt je samostatnou rel\u00e1ciou. <\/strong><\/p>\n<p><strong>Ako teda nov\u00fd Google Analytics 4 identifikuje u\u017e\u00edvate\u013eov na va\u0161ej str\u00e1nke, \u010di aplik\u00e1cii?<\/strong><\/p>\n<p>Google Analytics 4 m\u00f4\u017ee pou\u017ei\u0165 tri typy identifik\u00e1torov, ktor\u00fdmi tieto rel\u00e1cie sp\u00e1ja pod jedin\u00e9ho u\u017e\u00edvate\u013ea. T\u00fdmito identifik\u00e1tormi s\u00fa:<\/p>\n<ul>\n<li>User ID<\/li>\n<li>Google Signals<\/li>\n<li>Device ID<\/li>\n<\/ul>\n<h2>Identity Spaces<\/h2>\n<p>V\u0161etky identifik\u00e1tory spomenut\u00e9 vy\u0161\u0161ie sa naz\u00fdvaj\u00fa Identity Spaces, pri\u010dom tie, ktor\u00e9 pou\u017e\u00edva va\u0161e GA4 vlastn\u00edctvo sa naz\u00fdvaj\u00fa <strong>Reporting Identity<\/strong>.<\/p>\n<h3>User-ID<\/h3>\n<p>Ak m\u00e1te na va\u0161ej str\u00e1nke\/e-shope mo\u017enos\u0165 registr\u00e1cie, m\u00f4\u017eete pou\u017ei\u0165 tento User-ID identifik\u00e1tor na sledovanie cesty u\u017e\u00edvate\u013ea naprie\u010d zariadeniami a prehliada\u010dmi. Aby ste ho mohli vyu\u017e\u00edva\u0165, je potrebn\u00e9, aby ste ho konzistentne prira\u010fovali zaregistrovan\u00fdm n\u00e1v\u0161tevn\u00edkom v\u00e1\u0161ho webu, alebo aplik\u00e1cie a odosielali ho v\u017edy spolu s ostatn\u00fdmi d\u00e1tami do Analyticsu. Tento identifik\u00e1tor je najpresnej\u0161\u00ed, preto\u017ee vyu\u017e\u00edva d\u00e1ta, ktor\u00e9 zbierate, na identifik\u00e1ciu u\u017e\u00edvate\u013ea.<\/p>\n<p>Viac sa o User ID identifak\u00e1tore dozviete na <a href=\"https:\/\/support.google.com\/analytics\/answer\/3123662?hl=en#zippy=%2Cin-this-article\" target=\"_blank\" rel=\"noopener noreferrer\">tomto linku<\/a>, pr\u00edpadne o jeho implement\u00e1cii <a href=\"https:\/\/support.google.com\/analytics\/answer\/3123666?hl=en#zippy=%2Cin-this-article\" target=\"_blank\" rel=\"noopener noreferrer\">tu<\/a>. Okrem in\u00e9ho sa d\u00e1 User ID vyu\u017ei\u0165 aj na p\u00e1rovanie d\u00e1t s backendom, ale o tom niekedy inokedy. \ud83d\ude42<\/p>\n<h3>Google Signals<\/h3>\n<p>Google sign\u00e1ly s\u00fa d\u00e1ta od pou\u017e\u00edvate\u013eov, ktor\u00ed s\u00fa prihl\u00e1sen\u00ed do svojho Google \u00fa\u010dtu. Ak s\u00fa tieto Google Signal Data u\u017e\u00edvate\u013eov aktivovan\u00e9 a konkr\u00e9tny pou\u017e\u00edvate\u013e je prihl\u00e1sen\u00fd v Google \u00fa\u010dte a tie\u017e dal s\u00fahlas k zdie\u013eaniu t\u00fdchto inform\u00e1ci\u00ed, Google Analytics 4 ich zaznamen\u00e1va spolu s d\u00e1tami pri ka\u017edej udalosti. Tento identifik\u00e1tor je menej presn\u00fd ako User ID.<\/p>\n<p>Na <a href=\"https:\/\/support.google.com\/analytics\/answer\/7532985?hl=en#zippy=%2Cin-this-article\" target=\"_blank\" rel=\"noopener noreferrer\">tomto odkaze<\/a> n\u00e1jdete n\u00e1vod, ako si aktivova\u0165 vo va\u0161om GA \u00fa\u010dte Google Signals.<\/p>\n<h3>Device-ID<\/h3>\n<p>Google Analytics 4 vie na identifik\u00e1ciu u\u017e\u00edvate\u013eov pou\u017ei\u0165 aj ID zariadenia. Na va\u0161om webe je priraden\u00e9 Device ID ka\u017ed\u00e9mu zariadeniu n\u00e1v\u0161tevn\u00edka na z\u00e1klade Client ID. V pr\u00edpade aplik\u00e1ci\u00ed sa zas Device ID zhoduje s App-instance ID. Zo spom\u00ednan\u00fdch identifik\u00e1torov ide o najmenej presn\u00e9 rie\u0161enie.<\/p>\n<h2>Ako Google Analytics 4 ur\u010duje Reporting Identity?<\/h2>\n<p>Sp\u00f4sob, ak\u00fdm Analytics prira\u010fuje k jednotliv\u00fdm udalostiam pou\u017e\u00edvate\u013ea, je ur\u010den\u00fd nastaven\u00edm Reporting Identity na \u00farovni vlastn\u00edctva vo va\u0161om \u00fa\u010dte. Na prira\u010fovanie existuje viacero mo\u017enost\u00ed.<\/p>\n<h3><strong>Pod\u013ea User-ID, Google sign\u00e1lov, n\u00e1sledne ID zariadenia<\/strong><\/h3>\n<p>Ak je dostupn\u00e9 User ID, pou\u017eije sa to. Ak nie je dostupn\u00e9, Analytics pou\u017e\u00edva inform\u00e1cie z Google Signals. Ak nie je dostupn\u00e9 ani User ID, ani Google Signals, potom Analytics na identifik\u00e1ciu u\u017e\u00edvate\u013ea pou\u017eije ID zariadenia.<\/p>\n<p>Aby ste t\u00fato mo\u017enos\u0165 mohli vyu\u017ei\u0165, je potrebn\u00e9 aktivova\u0165 Google Signals. Okrem toho je potrebn\u00e9 ma\u0165 dostato\u010dn\u00e9 mno\u017estvo registrovan\u00fdch pou\u017e\u00edvate\u013eov na str\u00e1nke, aby boli ich identity anonymizovan\u00e9. Ak nie je dostato\u010dn\u00e9 mno\u017estvo d\u00e1t z Google Signals, uvid\u00edte len \u010fal\u0161ie dve Reporting Identity mo\u017enosti.<\/p>\n<p>Ke\u010f aktivujete Google Signals, Analytics za\u010dne zbiera\u0165 d\u00e1ta o demografi\u00ed a z\u00e1ujmoch pou\u017e\u00edvate\u013eov, ak s\u00fa dostupn\u00e9. D\u00f4sledkom aktivovania Google Signals je to, \u017ee va\u0161e reporty za\u010dn\u00fa podlieha\u0165 tzv. <em>data thresholdom<\/em>, ktor\u00e9 s\u00fa definovan\u00e9 syst\u00e9movo a nie je mo\u017en\u00e9 ich upravova\u0165.<\/p>\n<p><em>Data thresholdy<\/em> s\u00fa aplikovan\u00e9 preto, aby sa v nejakom reporte, alebo exploration reporte, nedal na z\u00e1klade demografick\u00fdch d\u00e1t, \u010di z\u00e1ujmov identifikova\u0165 individu\u00e1lny pou\u017e\u00edvate\u013e.<\/p>\n<h3><strong>Pod\u013ea User ID a ID zariadenia<\/strong><\/h3>\n<p>Tieto reportovacie identity s\u00fa dostupn\u00e9 vtedy, ak ste si vo vlastn\u00edctve neaktivovali Google Signals. Vyu\u017e\u00edvaj\u00fa prim\u00e1rne User ID. Ak nie je User ID dostupn\u00fd, Analytics pou\u017eije na identifik\u00e1ciu u\u017e\u00edvate\u013ea ID zariadenia.<\/p>\n<h3><strong>Pod\u013ea ID zariadenia<\/strong><\/h3>\n<p>Na identifik\u00e1ciu u\u017e\u00edvate\u013ea sa pou\u017e\u00edva len ID zariadenia, a to aj v pr\u00edpade, ak je dostupn\u00e9 User ID.<br \/>\nV\u00fdber, resp. zmena nastaven\u00ed Report Identity je mo\u017en\u00fd kedyko\u013evek bez toho, aby sa t\u00fdm naru\u0161il proces zberu, \u010di spracovania d\u00e1t.<\/p>\n<p>&nbsp;<\/p>\n<p>Google Analytics 4 n\u00e1sledne vytv\u00e1ra celkov\u00fa cestu u\u017e\u00edvate\u013ea na z\u00e1klade v\u0161etk\u00fdch dostupn\u00fdch Identity Spaces. Ke\u010f\u017ee sa tieto Identity Spaces vyu\u017e\u00edvaj\u00fa vo v\u0161etk\u00fdch reportoch, poskytuj\u00fa v\u00e1m ucelenej\u0161\u00ed a lep\u0161\u00ed preh\u013ead o celkovej ceste a spr\u00e1van\u00ed pou\u017e\u00edvate\u013ea pri interakcii s va\u0161\u00edm webom, \u010di aplik\u00e1ciou.<\/p>\n<h2>Nastavenie Report Identity v\u00e1\u0161ho vlastn\u00edctva<\/h2>\n<ol>\n<li>\u00a0Prihl\u00e1ste sa do v\u00e1\u0161ho \u00fa\u010dtu Google Analytics 4<\/li>\n<li>\u00a0Kliknite na Admin a vyberte vlastn\u00edctvo, ktor\u00e9 chcete upravi\u0165<\/li>\n<li>\u00a0V st\u013apci pre vlastn\u00edctvo kliknite na Predvolen\u00e1 identita pre preh\u013eady<br \/>\n<a href=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/1-11.png\" data-rel=\"lightbox-image-0\" data-rl_title=\"\" data-rl_caption=\"\" title=\"\"><img decoding=\"async\" loading=\"lazy\" class=\"alignnone wp-image-17989 size-full\" src=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/1-11.png\" alt=\"Ako Google Analytics reportuje pouziatela? DASE\" width=\"1370\" height=\"674\" srcset=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/1-11.png 1370w, https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/1-11-300x148.png 300w, https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/1-11-1024x504.png 1024w, https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/1-11-600x295.png 600w\" sizes=\"(max-width: 1370px) 100vw, 1370px\" \/><\/a><\/li>\n<li>\u00a0Vyberte reportovaciu identitu, ktor\u00fa chcete pou\u017e\u00edva\u0165<\/li>\n<li>\u00a0Kliknite Ulo\u017ei\u0165<br \/>\n<a href=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/2-10.png\" data-rel=\"lightbox-image-1\" data-rl_title=\"\" data-rl_caption=\"\" title=\"\"><img decoding=\"async\" loading=\"lazy\" class=\"alignnone wp-image-17990 size-full\" src=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/2-10.png\" alt=\"Ako Google Analytics 4 reportuje pouzivatela? DASE\" width=\"1580\" height=\"651\" srcset=\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/2-10.png 1580w, https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/2-10-300x124.png 300w, https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/2-10-1024x422.png 1024w, https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/2-10-1536x633.png 1536w, https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/2-10-600x247.png 600w\" sizes=\"(max-width: 1580px) 100vw, 1580px\" \/><\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>V\u00e4\u010d\u0161ina z\u00e1kazn\u00edkov interaguje s va\u0161\u00edm webom, \u010di aplik\u00e1ciou prostredn\u00edctvom viacer\u00fdch zariaden\u00ed, \u010di prehliada\u010dov. Niekto si napr. r\u00e1no m\u00f4\u017ee&#8230;<\/p>\n","protected":false},"author":74,"featured_media":17992,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[803,806],"tags":[799,798,674,372,641],"_links":{"self":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/17988"}],"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\/74"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/comments?post=17988"}],"version-history":[{"count":6,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/17988\/revisions"}],"predecessor-version":[{"id":18000,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/17988\/revisions\/18000"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media\/17992"}],"wp:attachment":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media?parent=17988"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/categories?post=17988"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/tags?post=17988"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}