{"id":13735,"date":"2020-07-22T09:45:29","date_gmt":"2020-07-22T07:45:29","guid":{"rendered":"https:\/\/www.dase-analytics.com\/blog\/?p=13735"},"modified":"2020-08-26T14:39:14","modified_gmt":"2020-08-26T12:39:14","slug":"ako-na-cross-domain-tracking-kompletny-navod","status":"publish","type":"post","link":"https:\/\/www.dase-analytics.com\/blog\/sk\/ako-na-cross-domain-tracking-kompletny-navod\/","title":{"rendered":"Ako na Cross Domain Tracking: Kompletn\u00fd n\u00e1vod"},"content":{"rendered":"

M\u00e1te 2 (a viac) r\u00f4znych dom\u00e9n a chcete efekt\u00edvne vyhodnocova\u0165 prechod pou\u017e\u00edvate\u013eov medzi nimi? Je pre v\u00e1s vhodn\u00fd cross domain? Ak \u00e1no, ako ho nastavi\u0165, aby fungoval spr\u00e1vne?<\/strong><\/p>\n

Uk\u00e1\u017eme si pr\u00edklad. M\u00e1te webstr\u00e1nku, ktor\u00fa vyu\u017e\u00edvate ako landing page va\u0161ej novej kampane (<\/span>www.domenaA.sk)<\/span><\/i>. T\u00e1to str\u00e1nka obsahuje odkazy na v\u00e1\u0161 internetov\u00fd obchod, ktor\u00fd sa nach\u00e1dza na inej dom\u00e9ne (<\/span>www.domenaB.sk). <\/span><\/i>Na tejto dom\u00e9ne m\u00f4\u017ee pou\u017e\u00edvate\u013e nak\u00fapi\u0165. Ak by Cross Domain tracking nebol implementovan\u00fd, konverzia by sa atribuovala zdroju domenaA.sk \/ referral. To znamen\u00e1, prechodom z domenaA.sk na domenaB.sk sa str\u00e1ca inform\u00e1cia o origin\u00e1lnom <\/span>zdroji n\u00e1v\u0161tevy<\/span><\/a>, \u010do rob\u00ed vyhodnocovanie kampan\u00ed prakticky nemo\u017en\u00fdm. Navy\u0161e, ak by ste aj d\u00e1ta zbierali do jedn\u00e9ho Google Analytics Vlastn\u00edctva (no bez Cross Domain nastavenia), videli by ste dvoch r\u00f4znych pou\u017e\u00edvate\u013eov – jedn\u00e9ho na dom\u00e9ne A a druh\u00e9ho na dom\u0144e B. <\/span>Skr\u00e1tka, v\u00fdsledkom s\u00fa rozbit\u00e9 d\u00e1ta bez mo\u017enosti hlb\u0161ej anal\u00fdzy.<\/b><\/p>\n

V tomto \u010dl\u00e1nku<\/span><\/a> sme v\u00e1m vysvetlili, \u010do je to Client ID. Nako\u013eko sa Client ID pou\u017e\u00edva na identifik\u00e1ciu pou\u017e\u00edvate\u013eov (zariaden\u00ed), budete ho musie\u0165 nejak\u00fdm sp\u00f4sobom odosla\u0165 z dom\u00e9ny A na dom\u00e9nu B. Client ID sa odosiela v linku v podobe parametra. Na str\u00e1nke B je tento parameter pre\u010d\u00edtan\u00fd a spracovan\u00fd <\/span>Google Analytics<\/span><\/a> k\u00f3dom. N\u00e1sledne je tento identifik\u00e1tor z parametra ulo\u017een\u00fd do _ga cookie, \u010d\u00edm sa zabezpe\u010d\u00ed rovnak\u00fd identifik\u00e1tor naprie\u010d viacer\u00fdmi dom\u00e9nami.<\/span><\/p>\n

V pr\u00edpade, \u017ee potrebujete nastavi\u0165 meranie iba medzi sub-dom\u00e9nami, napr\u00edklad:<\/span><\/i><\/p>\n

obchod.domena.sk, www.domena.sk, admin.domena.sk,<\/span><\/i><\/p>\n

tak budete potrebova\u0165 Cross SubDomain Tracking. Ked\u017ee sa cookie medzi sub-dom\u00e9nami zdie\u013ea pri be\u017enom nastaven\u00ed automaticky, sta\u010d\u00ed ak z tohto n\u00e1vodu pou\u017eijete body 5 a 6. Prv\u00e9 4 vynechajte.<\/span><\/i><\/p>\n

Ako nastavi\u0165 Cross Domain Tracking<\/span><\/h2>\n

V tomto \u010dl\u00e1nku si prejdeme v\u0161etky potrebn\u00e9 kroky pre nasadenie Cross Domain Tracking-u pomocou<\/span> Google Tag Manager-a<\/span><\/a>:<\/span><\/p>\n

    \n
  1. Nastavenie rovnak\u00e9ho meracieho k\u00f3du Google Analytics na oboch (alebo viacer\u00fdch) dom\u00e9nach.<\/span><\/li>\n
  2. Vytvorenie Cross Domain Google Analytics tagov.<\/span><\/li>\n
  3. \u2018Auto Link Domains\u2019 nastavenie v Google Tag Manager-i.<\/span><\/li>\n
  4. \u2018allowLinker\u2019 nastavenie v Google Tag Manager-i.<\/span><\/li>\n
  5. Premenovanie cookie v Google Tag Manager-i.<\/span><\/li>\n
  6. Pridanie dom\u00e9n do \u2018Referral Exclusion List\u2019 v Google Analytics.<\/span><\/li>\n
  7. Pridanie filtra na spojenie n\u00e1zvu dom\u00e9ny a cesty v Google Analytics.<\/span><\/li>\n<\/ol>\n

     <\/p>\n

    1. Rovnak\u00fd merac\u00ed k\u00f3d Google Analytics na oboch dom\u00e9nach<\/b><\/p>\n

    Z\u00e1kladn\u00fdm predpokladom pre Cross Domain meranie je, \u017ee sa d\u00e1ta z oboch dom\u00e9n (pr\u00edpadne aj viacer\u00fdch) bud\u00fa zbiera\u0165 do toho ist\u00e9ho Google Analytics vlastn\u00edctva (Property). Ide\u00e1lnym rie\u0161en\u00edm je mera\u0165 ka\u017ed\u00fa dom\u00e9nu do svojho vlastn\u00e9ho GA vlastn\u00edctva a taktie\u017e ma\u0165 jedno spolo\u010dn\u00e9 Cross Domain vlastn\u00edctvo, pre v\u0161etky dom\u00e9ny s Cross Domain meran\u00edm. Teda na ka\u017edej dom\u00e9ne sa d\u00e1ta bud\u00fa odosiela\u0165 ako do dvoch vlastn\u00edctiev:<\/span><\/p>\n

      \n
    1. Do svojho vlastn\u00edctva danej dom\u00e9ny.<\/span><\/li>\n
    2. Do spolo\u010dn\u00e9ho Cross Domain vlastn\u00edctva.<\/span><\/li>\n<\/ol>\n

      Pre\u010do nie je vhodn\u00e9 pou\u017ei\u0165 u\u017e existuj\u00face vlastn\u00edctvo (Property) a nastavi\u0165 v nej Cross Domain tracking?<\/b> Ak by sme pou\u017eili jedno z u\u017e existuj\u00facich vlastn\u00edctiev je ve\u013ek\u00e1 pravedepodobnos\u0165, \u017ee by doch\u00e1dzalo k ne\u017eelan\u00e9mu prepisovaniu Client ID identifik\u00e1torov pre pou\u017e\u00edvate\u013eov, ktor\u00ed u\u017e v minulosti nav\u0161t\u00edvili dom\u00e9nu B. Ak by po implement\u00e1cii Cross Domain merania znova nav\u0161t\u00edvili dom\u00e9nu B (no tentoraz preklikom z dom\u00e9ny A), tak by ich p\u00f4vodn\u00e9 Client ID bolo prep\u00edsan\u00e9 nov\u00fdm Client ID z dom\u00e9ny A, \u010d\u00edm by vznikol nov\u00fd pou\u017e\u00edvate\u013e. Prep\u00edsan\u00edm Client ID by navy\u0161e zanikol predch\u00e1dzaj\u00faci identifik\u00e1tor, pre ktor\u00fd by sa u\u017e \u017eiadne nov\u00e9 d\u00e1ta nezbierali.<\/span><\/p>\n

      \"Cross-Domain<\/p>\n

      2. Vytvorenie Cross Domain Google Analytics tagov<\/b><\/p>\n

      Ak u\u017e vyu\u017e\u00edvate Google Tag Manager na posielanie tagov do osobitn\u00e9ho vlastn\u00edctva, v\u0161etky tieto tagy budete musie\u0165 skop\u00edrova\u0165, a vytvori\u0165 tak ich Cross Domain verziu (do \u2018Tracking ID\u2019 vyberte spolo\u010dn\u00e9 Cross Domain vlastn\u00edctvo). Nasleduj\u00face kroky aplikujte vo v\u0161etk\u00fdch novovytvoren\u00fdch Cross Domain tagoch.<\/span><\/p>\n

      3. \u2018Auto Link Domains\u2019 nastavenie v Google Tag Manager-i<\/b><\/p>\n

      Ako \u010fal\u0161\u00ed krok potrebujeme v Google Tag Manageri upravi\u0165 v\u00e1\u0161 Google Analytics tag (odpor\u00fa\u010dam vytvori\u0165 a pou\u017e\u00edva\u0165 Google Analytics Settings premenn\u00fa, ktor\u00e1 cel\u00fd proces v\u00fdrazne u\u013eah\u010d\u00ed). Pod \u2018More Settings\u2019 n\u00e1jdeme \u010das\u0165 \u2018Cross Domain Tracking\u2019 a do pol\u00ed\u010dka \u2018Auto Link Domains\u2019 je potrebn\u00e9 zap\u00edsa\u0165 v\u0161etky dom\u00e9ny, ktor\u00e9 chceme takto prepoji\u0165. Ka\u017ed\u00fa dom\u00e9nu odde\u013ete \u010diarkou.<\/span><\/p>\n

      \"Cross-Domain<\/p>\n

      Medzi t\u00fdmito dom\u00e9nami sa bude po prekliku z jednej na druh\u00fa prid\u00e1va\u0165 parameter _ga, obsahuj\u00faci Client ID a \u010dasov\u00e9 zna\u010dky (timestamps). \u010casov\u00e9 zna\u010dky sl\u00fa\u017eia na to, aby Google Analytics ur\u010dil, kedy bol preklik vykonan\u00fd, ak\u00e1 je expir\u00e1cia linku at\u010f.<\/span><\/p>\n

      \"Cross<\/p>\n

      4. \u2018allowLinker\u2019 nastavenie v Google Tag Manager-i<\/b><\/p>\n

      Vo v\u0161etk\u00fdch Cross Domain tagoch (alebo ide\u00e1lne Google Analytics Settings premennej) v \u010dasti \u2018More Settings\u2019 a \u2018Fields to Set\u2019 pridajte parameter \u2018allowLinker\u2019 a jeho hodnotu nastavte na \u2018true\u2019. T\u00fdmto nastaven\u00edm zabezpe\u010d\u00edme, \u017ee Google Analytics tag prijme parameter _ga, spracuje Client ID z tohto parametra a prep\u00ed\u0161e hodnotu v cookie.<\/span><\/p>\n

      \"\"<\/p>\n

      5. Premenovanie cookie v Google Tag Manageri<\/b><\/p>\n

      Ke\u010f\u017ee chcete zabr\u00e1ni\u0165 tomu, aby ste si prepisovali u\u017e pred t\u00fdm vytvoren\u00fa _ga cookie (\u010do by viedlo k rovnak\u00e9mu probl\u00e9mu, ktor\u00fd som pop\u00edsal v bode 1), mus\u00edte vytvori\u0165 vlastn\u00fa cookie, ktor\u00e1 bude uchov\u00e1va\u0165 identifik\u00e1tor pre Cross Domain Vlastn\u00edctvo. V GTM prid\u00e1te \u010fal\u0161\u00ed parameter s n\u00e1zvom \u2018cookieName\u2019 a ako jeho hodnotu nastav\u00edte n\u00e1zov cookie pre Cross Domain Vlastn\u00edctvo, napr. \u2018_gaCrossDomain\u2019. Teraz sa Client ID bude prepisova\u0165 len v tejto cookie a teda nebudete prich\u00e1dza\u0165 o \u017eiadne d\u00e1ta.<\/span>
      \n\"allowLinker<\/p>\n

      6. Pridanie dom\u00e9n do \u2018Referral Exclusion List\u2019 v Google Analytics<\/b><\/p>\n

      Rovnako d\u00f4le\u017eit\u00e9 je vlo\u017ei\u0165 v\u0161etky dom\u00e9ny, ktor\u00e9 ste vkladali do \u2018Auto Link Domains\u2019 aj do<\/span> Referral Exclusion List-u<\/span><\/a> v Google Analytics. Ak by ste to nespravili, Google Analytics s\u00edce korektne prep\u00ed\u0161e Client ID pre pou\u017e\u00edvate\u013ea, no prechodom medzi dom\u00e9nami by vznikla nov\u00e1 rel\u00e1cia (ke\u010f\u017ee do\u0161lo k zmene zdroja). Po pridan\u00ed dom\u00e9n do tohto zoznamu bude t\u00e1to zmena zdroja ignorovan\u00e1, \u010d\u00edm zabezpe\u010d\u00edte pokra\u010dovanie p\u00f4vodnej Rel\u00e1cie, ktor\u00e1 za\u010dala na dom\u00e9ne A. Toto nastavenie sa napr\u00edklad vyu\u017e\u00edva aj pre vyl\u00fa\u010denie platobn\u00fdch br\u00e1n, aby sa transakcie po presmerovan\u00ed na \u010fakovn\u00fa str\u00e1nku nepripisovali t\u00fdmto platobn\u00fdm br\u00e1nam, ale origin\u00e1lnemu zdroju n\u00e1v\u0161tevy.<\/span><\/p>\n

      \"Referral<\/p>\n

      7. Pridanie filtra na spojenie n\u00e1zvu dom\u00e9ny a cesty v Google Analytics<\/b><\/p>\n

      Ke\u010f\u017ee Google Analytics \u0161tandardne v preh\u013eadoch zobrazuje z URL iba cestu (path) bez dom\u00e9ny, zbieran\u00edm d\u00e1t z viacer\u00fdch dom\u00e9n by vznikol probl\u00e9m s agreg\u00e1ciou. To napr\u00edklad znamen\u00e1, \u017ee by sa v\u0161etky metriky (Time on Page, Pageviews, Bounce rate\u2026) pre cestu \u2018\/\u2019 (domovsk\u00fa str\u00e1nku dom\u00e9ny A a dom\u00e9ny B) agregovali naprie\u010d dom\u00e9nami A a B, \u010do ned\u00e1va zmysel. Aby ste takejto nechcenej agreg\u00e1cii d\u00e1t predi\u0161li, mus\u00edte prida\u0165 filter, ktor\u00fd k ceste (Request URI) pripoj\u00ed n\u00e1zov dom\u00e9ny (Hostname). Tento filter by sa mal prida\u0165 do v\u0161etk\u00fdch zobrazen\u00ed v Cross Domain vlastn\u00edctve.<\/span><\/p>\n

      \"advanced<\/p>\n

      Po t\u00fdchto krokoch m\u00e1te nastaven\u00fd Cross Domain Tracking so v\u0161etk\u00fdm potrebn\u00fdm.<\/b> E\u0161te je dobr\u00e9 poznamena\u0165, \u017ee pri tomto nastaven\u00ed bude, samozrejme, fungova\u0165 Cross Domain Tracking aj opa\u010dne. Teda nie len z dom\u00e9ny A na dom\u00e9nu B, ale aj z dom\u00e9ny B na dom\u00e9nu A.<\/span><\/p>\n

      Na konci odpor\u00fa\u010dam v\u0161etko d\u00f4kladne otestova\u0165.\u00a0<\/span><\/p>\n