{"id":18049,"date":"2021-12-08T11:41:03","date_gmt":"2021-12-08T09:41:03","guid":{"rendered":"https:\/\/www.dase-analytics.com\/blog\/?p=18049\/"},"modified":"2021-12-08T11:41:25","modified_gmt":"2021-12-08T09:41:25","slug":"ako-funguje-pocet-relacii-v-google-analytics-4","status":"publish","type":"post","link":"https:\/\/www.dase-analytics.com\/blog\/sk\/ako-funguje-pocet-relacii-v-google-analytics-4\/","title":{"rendered":"Ako funguje metrika po\u010det rel\u00e1ci\u00ed v novom Google Analytics 4"},"content":{"rendered":"

Pred t\u00fdm, ako si vysvetl\u00edme, ako funguje spom\u00ednan\u00e1 metrika, je dobr\u00e9 si pripomen\u00fa\u0165, za ak\u00fdch podmienok tak\u00e1 rel\u00e1cia za\u010d\u00edna. V Google Analytics 4 za\u010d\u00edna rel\u00e1cia, ke\u010f si u\u017e\u00edvate\u013e otvor\u00ed na popred\u00ed va\u0161u aplik\u00e1ciu, alebo nav\u0161t\u00edvi str\u00e1nku na va\u0161om webe v pr\u00edpade, \u017ee nie je st\u00e1le akt\u00edvna jeho predo\u0161l\u00e1 rel\u00e1cia. <\/strong><\/p>\n

Na rozdiel od star\u0161ieho Universal Analytics sa u\u017e rel\u00e1cia v novom GA4 \u201cnel\u00e1me\u201d o polnoci, no v tomto oh\u013eade s\u00fa tu st\u00e1le ur\u010dit\u00e9 \u201cnezrovnalosti\u201d, o ktor\u00fdch si m\u00f4\u017eete pre\u010d\u00edta\u0165 viac napr. na tomto linku<\/a>.<\/strong><\/p>\n

Vo v\u00fdchodzom nastaven\u00ed Google Analytics 4 sa rel\u00e1cia kon\u010d\u00ed po 30 min\u00fatach<\/strong> neaktivity u\u017e\u00edvate\u013ea, pri\u010dom tento limit je mo\u017en\u00e9 upravi\u0165 v nastaven\u00ed relevantn\u00e9ho streamu v \u201cmore tagging settings<\/strong>\u201d a n\u00e1sledne v \u201cadjust session timeout<\/strong> – postup je podrobnej\u0161ie pop\u00edsan\u00fd ni\u017e\u0161ie.<\/p>\n

Napr. v pr\u00edpade, \u017ee uverej\u0148ujete na va\u0161ej str\u00e1nke dlh\u0161ie vide\u00e1 (dlh\u0161ie ako 30 min\u00fat), je vhodn\u00e9 tento timeout pred\u013a\u017ei\u0165, aby v\u00e1m po\u010das sledovania videa u\u017e\u00edvate\u013eom, nevznikli viacer\u00e9 rel\u00e1cie. Pre tento timeout neexistuje \u017eiadny limit.<\/p>\n

Nastavenie timeoutu pre rel\u00e1cie v aplik\u00e1ci\u00e1ch<\/h2>\n

Rel\u00e1ci\u00e1m v aplik\u00e1ci\u00e1ch timeout za\u010d\u00edna, ke\u010f je aplik\u00e1cia presunut\u00e1 na pozadie. Je tu mo\u017enos\u0165 pred\u013a\u017ei\u0165 t\u00fato rel\u00e1ciu zahrnut\u00edm parametra extend_session<\/strong> s priradenou hodnotou 1 pri udalostiach – eventoch, ktor\u00e9 sa odosielaj\u00fa, k\u00fdm je aplik\u00e1cia na pozad\u00ed. Tento sp\u00f4sob je u\u017eito\u010dn\u00fd najm\u00e4 v pr\u00edpade, ak je va\u0161a aplik\u00e1cia \u010dasto pou\u017e\u00edvan\u00e1 pr\u00e1ve na pozad\u00ed. Jedn\u00e1 sa napr. o aplik\u00e1cie pre navig\u00e1ciu, \u010di prehr\u00e1vanie hudby a pod. V\u00fdchodzie nastavenie timeoutu na 30 min\u00fat je mo\u017en\u00e9 upravi\u0165 met\u00f3dou setSessionTimeoutDuration<\/strong>, pri\u010dom d\u013a\u017eka trvania sa ud\u00e1va v milisekund\u00e1ch (v\u00fdchodzie nastavenie je 1 800 000 ms (30 min\u00fat)).<\/p>\n

\u00daprava nastaven\u00ed timeoutu pre rel\u00e1cie na webe<\/h2>\n

Pre \u00fapravu v\u00fdchodzieho \u010dasov\u00e9ho limitu rel\u00e1ci\u00ed (30 min\u00fat) na webe postupujte pod\u013ea nasleduj\u00facich krokov:<\/p>\n

    \n
  1. Prihl\u00e1ste sa do svojho \u00fa\u010dtu<\/li>\n
  2. V sekci\u00ed Admin<\/strong> vyberte Vlastn\u00edctvo<\/strong> (Property), v ktorom chcete timeout upravi\u0165<\/li>\n
  3. Kliknite na Streamy \u00fadajov<\/strong> (Data Streams) a vyberte relevantn\u00fd web Data Stream<\/li>\n
  4. Pod \u010eal\u0161\u00edmi nastaveniami<\/strong> (Additional Settings), kliknite na \u010eal\u0161ie nastavenia zna\u010dkovania<\/strong> (More Tagging Settings) a n\u00e1sledne dolu na Upravi\u0165 \u010dasov\u00fd limit rel\u00e1cie<\/strong> (Adjust session timeout)
    \n    \"Ako<\/a>
    \n    \"Ako<\/a><\/li>\n
  5. Upravte \u010dasov\u00fd limit rel\u00e1cie<\/strong> (Session Timeout – zad\u00e1va sa v hodin\u00e1ch a min\u00fatach)<\/li>\n
  6. M\u00f4\u017eete tu tie\u017e upravi\u0165 \u010casova\u010d pre rel\u00e1cie interakci\u00ed<\/strong> (Timer for Engaged Sessions) – zadajte \u010das (v sekund\u00e1ch), po ktorom sa rel\u00e1cia vyhodnot\u00ed ako zapo\u010dat\u00e1 (mo\u017enosti od 10 do 60 sekund).
    \n    \"Ako<\/a><\/li>\n
  7. Kliknite na Ulo\u017ei\u0165<\/strong><\/li>\n<\/ol>\n

    Ako sa rel\u00e1cie po\u010d\u00edtaj\u00fa?<\/h2>\n

    Po\u010det rel\u00e1ci\u00ed sa m\u00f4\u017ee v novom Google Analytics 4 l\u00ed\u0161i\u0165 od po\u010dtu rel\u00e1ci\u00ed v star\u0161om Universal Analytics – m\u00f4\u017ee by\u0165 ni\u017e\u0161\u00ed…<\/p>\n

    Je to sp\u00f4soben\u00e9 u\u017e spom\u00ednan\u00fdm rozdielom v \u201cl\u00e1man\u00ed\u201d rel\u00e1ci\u00ed o polnoci. Nov\u00fd GA4 nevytv\u00e1ra nov\u00fa rel\u00e1ciu, ke\u010f sa o polnoci zmen\u00ed Campaign Source, pri\u010dom star\u0161\u00ed UA za tak\u00fdchto okolnost\u00ed nov\u00fa rel\u00e1ciu vytv\u00e1ra. Ak napr. rel\u00e1cia za\u010dne o 23:50 a skon\u010d\u00ed o 00:10 nasleduj\u00faceho d\u0148a, je pova\u017eovan\u00e1 za jedin\u00fa rel\u00e1ciu, pri\u010dom je ale po\u010d\u00edtan\u00e1 pre ka\u017ed\u00fd z dan\u00fdch dn\u00ed.<\/p>\n

    Tu je vhodn\u00e9 pripomen\u00fa\u0165 potrebu spr\u00e1vneho nastavenia krajiny v \u010casovom p\u00e1sme preh\u013eadov<\/strong> (Reporting Time Zone) v z\u00e1kladnom nastaven\u00ed relevantn\u00e9ho vlastn\u00edctva – odpor\u00fa\u010da sa nastavi\u0165 krajinu, z ktorej je str\u00e1nka\/aplik\u00e1cia naj\u010dastej\u0161ie nav\u0161tevovan\u00e1\/pou\u017e\u00edvan\u00e1.<\/p>\n

    \"Ako<\/a><\/p>\n

    Ako sa udalosti (eventy) pridru\u017euj\u00fa k rel\u00e1ci\u00e1m<\/h2>\n

    Eventy sa pridru\u017euj\u00fa k rel\u00e1ci\u00e1m dvoma sp\u00f4sobmi:<\/p>\n

      \n
    • ga_session_id :<\/strong> Unik\u00e1tny identifik\u00e1tor rel\u00e1cie pridru\u017een\u00fd ku ka\u017ed\u00e9mu eventu, ktor\u00fd sa udeje v priebehu danej rel\u00e1cie.<\/li>\n
    • ga_session_number :<\/strong> Parameter pridru\u017een\u00fd ku ka\u017edej udalosti, ktor\u00e1 sa udeje v priebehu rel\u00e1cie. Identifikuje poz\u00edciu poradia rel\u00e1cie vo vz\u0165ahu ku konkr\u00e9tnemu u\u017e\u00edvate\u013eovi, napr. 1. alebo 4. rel\u00e1cia. T\u00e1to inform\u00e1cia vie by\u0165 u\u017eito\u010dn\u00e1, ke\u010f sa objav\u00ed nejak\u00fd \u0161pecifick\u00fd typ udalosti, napr. zist\u00edme , \u017ee in_app_purchase<\/em> eventy sa objavia v 80% pr\u00edpadov v priebehu 5. a\u017e 8. rel\u00e1cie a pod.<\/li>\n<\/ul>\n

      Ak\u00fd je vz\u0165ah medzi u\u017e\u00edvate\u013eom, rel\u00e1ciami a udalos\u0165ami<\/h2>\n

      GA4 zara\u010fuje u\u017e\u00edvate\u013eov, rel\u00e1cie a eventy v nasledovnej hierarchii:<\/p>\n

        \n
      • User (u\u017e\u00edvate\u013e)<\/strong>\n
          \n
        • Session (rel\u00e1cia)<\/strong>\n
            \n
          • Event (udalos\u0165)<\/strong><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n

            Udalosti<\/strong> (eventy) s\u00fa individu\u00e1lne akcie, ktor\u00e9 vykon\u00e1vaj\u00fa u\u017e\u00edvatelia pri n\u00e1v\u0161teve va\u0161ej str\u00e1nky alebo vyu\u017e\u00edvan\u00ed va\u0161ej aplik\u00e1cie. Pre lep\u0161iu predstavu, m\u00f4\u017eu zah\u0155\u0148a\u0165 kliknutia na linky, kontakty, odoslanie formul\u00e1ra, prehratie videa, scrollovanie a pod.<\/p>\n

            V novom GA4 rozhran\u00ed pozn\u00e1me automaticky zaznamen\u00e1van\u00e9 udalosti<\/strong> (automatically collected events – s\u00fa zaznamen\u00e1van\u00e9 automaticky, ak je aktivovan\u00e9 zhroma\u017e\u010fovanie \u00fadajov), roz\u0161\u00edren\u00e9 meracie udalost\u00ed<\/strong> (enhanced measurement events – ak s\u00fa aktivovan\u00e9 v streame \u00fadajov). Pre pokro\u010dilej\u0161ie merania je mo\u017en\u00e9 prida\u0165 aj odpor\u00fa\u010dan\u00e9 udalosti<\/strong> (recommended events – je potrebn\u00e9 implementova\u0165, no maj\u00fa preddefinovan\u00e9 n\u00e1zvy a parametre) a vlastn\u00e9 udalosti<\/strong> (custom events – potrebn\u00e9 nazva\u0165 a implementova\u0165, v \u0161tandardn\u00fdch reportoch sa v\u00e4\u010d\u0161inou nezobrazuj\u00fa).<\/p>\n

            Tu je vhodn\u00e9 pripomen\u00fa\u0165, \u017ee niektor\u00e9 eventy ako je napr. zobrazenie prvku na str\u00e1nke, \u010di scrollovanie, sa m\u00f4\u017eu za ur\u010dit\u00fdch okolnost\u00ed \u201codp\u00e1li\u0165\u201d bez akejko\u013evek aktivity u\u017e\u00edvate\u013ea na str\u00e1nke – len samotn\u00fdm na\u010d\u00edtan\u00edm str\u00e1nky webu. Tento fakt treba bra\u0165 do \u00favahy, aby sa rel\u00e1cia nestala automaticky rel\u00e1ciou s interakciou a negat\u00edvne neovplyvnila t\u00fato \u0161tatistiku, ako aj Bounce rate (viac o tom, ako sa rel\u00e1cia s interakciou po\u010d\u00edta, je spomenut\u00e9 ni\u017e\u0161ie).<\/p>\n

            Rel\u00e1cie<\/strong> (sessions) s\u00fa zase individu\u00e1lne akcie, ktor\u00e9 u\u017e\u00edvate\u013e vykon\u00e1 v ur\u010ditom \u010dasovom r\u00e1mci. Napr\u00edklad u\u017e\u00edvate\u013e nav\u0161t\u00edvi va\u0161u str\u00e1nku, klikne na nejak\u00fd link a n\u00e1sledne si objedn\u00e1 produkt, alebo slu\u017ebu, ktor\u00fa pon\u00fakate. Google Analytics tieto vyhodnot\u00ed ako s\u00fa\u010das\u0165 jedinej rel\u00e1cie, ak u\u017e\u00edvate\u013e nezostane neakt\u00edvny po dlh\u0161iu dobu ako 30 min\u00fat (teda v pr\u00edpade, \u017ee ste nenastavili rel\u00e1ci\u00e1m in\u00fd timeout – pop\u00edsan\u00e9 vy\u0161\u0161ie). Ak bol u\u017e\u00edvate\u013e neakt\u00edvny po dobu dlh\u0161iu ako 30 min\u00fat, nasleduj\u00face akcie sa zar\u00e1taj\u00fa u\u017e do \u010fal\u0161ej rel\u00e1cie.<\/p>\n

            Pou\u017e\u00edvatelia<\/strong> (users) s\u00fa konkr\u00e9tni \u013eudia (ak to nie s\u00fa boti :), ktor\u00ed vykon\u00e1vaj\u00fa na va\u0161ej str\u00e1nke, alebo vo va\u0161ej aplik\u00e1cii akcie v jednej, alebo viacer\u00fdch rel\u00e1ci\u00e1ch.<\/p>\n

            Kde n\u00e1js\u0165 metriky rel\u00e1ci\u00ed<\/h2>\n

            V prvom rade treba zmieni\u0165, \u017ee v novom GA4 vlastn\u00edctve pozn\u00e1me 3 metriky relevantn\u00e9 pre rel\u00e1cie:<\/p>\n

              \n
            • Sessions<\/strong> (Rel\u00e1cie): Po\u010det rel\u00e1ci\u00ed, ktor\u00e9 za\u010dali na va\u0161om webe alebo vo va\u0161ej aplik\u00e1ci\u00ed (udalos\u0165 (event) session_start bola spusten\u00e1)<\/li>\n
            • Engaged sessions<\/strong> (Rel\u00e1cie s interakciou): Po\u010det rel\u00e1ci\u00ed, ktor\u00e9 trvali 10 sek\u00fand a dlh\u0161ie (v pr\u00edpade, \u017ee ste neupravili Timer for engaged sessions – spom\u00ednan\u00e9 vy\u0161\u0161ie), alebo po\u010det rel\u00e1ci\u00ed, ktor\u00e9 obsahovali 1 a viac konverzn\u00fdch eventov, alebo zah\u0155\u0148ali 2 a viac nav\u0161t\u00edven\u00fdch str\u00e1nok v\u00e1\u0161ho webu.<\/li>\n
            • Engaged sessions per user<\/strong> (Rel\u00e1cie s interakciou na pou\u017e\u00edvate\u013ea): Podiel po\u010dtu rel\u00e1ci\u00ed s interakciou a po\u010dtu u\u017e\u00edvate\u013eov<\/li>\n<\/ul>\n

              Spom\u00ednan\u00e9 metriky mo\u017eno n\u00e1js\u0165 v GA4 v nasleduj\u00facich reportoch:<\/p>\n

                \n
              • Preh\u013ead akviz\u00edci\u00ed (Acquisition overview)<\/li>\n
              • Akviz\u00edcia pou\u017e\u00edvate\u013eov (User acquisition)<\/li>\n
              • Akviz\u00edcia n\u00e1v\u0161tevnosti (Traffic acquisition)<\/li>\n
              • Preh\u013ead interakci\u00ed (Engagement overview)<\/li>\n
              • Demografick\u00e9 \u00fadaje (Demographic details)<\/li>\n
              • Technick\u00e9 detaily (Tech details)<\/li>\n<\/ul>\n

                 <\/p>\n

                 <\/p>\n","protected":false},"excerpt":{"rendered":"

                Pred t\u00fdm, ako si vysvetl\u00edme, ako funguje spom\u00ednan\u00e1 metrika, je dobr\u00e9 si pripomen\u00fa\u0165, za ak\u00fdch podmienok tak\u00e1 rel\u00e1cia…<\/p>\n","protected":false},"author":74,"featured_media":18054,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[803,639],"tags":[603,798,372,641],"_links":{"self":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/18049"}],"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=18049"}],"version-history":[{"count":4,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/18049\/revisions"}],"predecessor-version":[{"id":18058,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/18049\/revisions\/18058"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media\/18054"}],"wp:attachment":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media?parent=18049"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/categories?post=18049"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/tags?post=18049"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}