{"id":16818,"date":"2020-10-16T11:41:59","date_gmt":"2020-10-16T09:41:59","guid":{"rendered":"https:\/\/www.dase-analytics.com\/blog\/?p=16818\/"},"modified":"2021-10-26T13:17:34","modified_gmt":"2021-10-26T11:17:34","slug":"lookup-table-v-google-tag-manageri","status":"publish","type":"post","link":"https:\/\/www.dase-analytics.com\/blog\/sk\/lookup-table-v-google-tag-manageri\/","title":{"rendered":"Pou\u017e\u00edvate lookup table v GTM? Mo\u017eno by ste mali (+ 5 tipov pre v\u00e1\u0161 web)"},"content":{"rendered":"

Za prv\u00fd rok m\u00f4jho p\u00f4sobenia v DASE sa mi pod ruky dostali desiatky GTM kontajnerov. V nich som u\u017e videl kade\u010do, ale jednu vec som v nich nevidel ur\u010dite – lookup table premenn\u00fa<\/strong>. V tomto \u010dl\u00e1nku sa pozrieme, \u010do to vlastne t\u00e1 lookup table je, ako funguje a uk\u00e1\u017eeme si aj 5 tipov, kedy je dobr\u00e9 ju pou\u017ei\u0165.<\/p>\n

\u010co je to lookup table premenn\u00e1 a ako ju pou\u017e\u00edva\u0165?<\/h2>\n

Google definuje lookup table ako dynamick\u00fa premenn\u00fa, ktorej hodnota je definovan\u00e1 v p\u00e1rovej tabu\u013eke vstupn\u00fdch a v\u00fdstupn\u00fdch hodn\u00f4t. Teraz na t\u00fato vetu zabudneme a sk\u00fasim v\u00e1m to tu op\u00edsa\u0165 \u013eudskou re\u010dou.<\/p>\n

Predstavte si situ\u00e1ciu, kedy by ste nejak\u00fa zna\u010dku (napr\u00edklad konverzn\u00fa zna\u010dku pre Google Ads<\/a>) chceli odpa\u013eova\u0165 iba v pr\u00edpade slovenskej mut\u00e1cie webu. V pohode, nastav\u00edte si pr\u00edslu\u0161n\u00fd trigger iba na slovensk\u00fa mut\u00e1ciu a v\u0161etko dokonale funguje. \u010casom v\u0161ak expandujete na \u010desk\u00fd, nemeck\u00fd, franc\u00fazsky, holandsk\u00fd a severok\u00f3rejsk\u00fd trh a budete potrebova\u0165 odp\u00e1li\u0165 konverzn\u00e9 zna\u010dky s in\u00fdmi kombin\u00e1ciami Conversion ID a Conversion Label pre v\u0161etk\u00fdch 5 kraj\u00edn. \u010co urob\u00edte? Vytvor\u00edte si 5 samostatn\u00fdch konverzn\u00fdch zna\u010diek a ku ka\u017edej z nich vlastn\u00fd trigger? Nie. Odpove\u010fou je, ako u\u017e asi tu\u0161\u00edte, lookup table.<\/p>\n

Lookup table v\u00e1m umo\u017en\u00ed na z\u00e1klade vstupnej hodnoty, ktor\u00fa nesie in\u00e1 premenn\u00e1 (naj\u010dastej\u0161ie dataLayer premenn\u00e1, alebo vstavan\u00e1 premenn\u00e1), priradi\u0165 na v\u00fdstupe vlastn\u00fa hodnotu ak\u00fa potrebujete. V\u00fdstupn\u00e1 hodnota potom m\u00f4\u017ee by\u0165 pou\u017eit\u00e1 v podmienke pre trigger, ako parameter v \u013eubovo\u013enej zna\u010dke, ale napr\u00edklad aj ako premenn\u00e1 vo vlastnom JavaScripte<\/a>. Po\u010fme sa pozrie\u0165 na to, ako by lookup table vyzerala v pr\u00edklade s konverzn\u00fdmi zna\u010dkami.<\/p>\n

Pr\u00edklad 1: Konverzn\u00e9 zna\u010dky pod\u013ea jazykovej mut\u00e1cie<\/h2>\n

Dajme tomu, \u017ee aktu\u00e1lne pou\u017e\u00edvan\u00fa jazykov\u00fa mut\u00e1ciu posielate do dataLayera, odkia\u013e si potom hodnotu \u0165ah\u00e1te cez dataLayer premenn\u00fa {{DL - pageLanguage}}<\/code>. T\u00e1to premenn\u00e1 bude vstupom pre va\u0161u lookup table {{LT - Conversion ID}}<\/code>. Lookup table bude v tomto pr\u00edpade vyzera\u0165 nasledovne:<\/p>\n

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

V\u00fdstupom bude ID konverzie, ktor\u00e9 pou\u017eijete v jednom v\u0161eobecnom konverznom tagu pre v\u0161etk\u00fdch 6 jazykov\u00fdch mut\u00e1ci\u00ed a ktor\u00fd odp\u00e1lite jedn\u00fdm v\u0161eobecn\u00fdm triggerom. Tak\u00fdmto jednoduch\u00fdm hackom, ste pr\u00e1ve zredukovali po\u010det elementov v GTM z p\u00f4vodn\u00fdch 12 (6x tag + 6x trigger) na 3 (1x tag + 1x trigger + 1x lookup table variable). Gratulujem.<\/p>\n

Analogicky si m\u00f4\u017eete vytvori\u0165 druh\u00fa lookup table pre hodnotu Conversion Label. Va\u0161a konverzn\u00e1 zna\u010dka bude potom vyzera\u0165 nasledovne:<\/p>\n

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

Pr\u00edklad 2: N\u00e1zvy formul\u00e1rov pod\u013ea ID formul\u00e1ra<\/h2>\n

Predstavme si pr\u00edklad, kedy m\u00e1te na webe rozmiestnen\u00fdch nieko\u013eko formul\u00e1rov, ka\u017ed\u00fd so samostatn\u00fdm {{Form ID}}<\/code> v podobe re\u0165azca n\u00e1hodn\u00fdch znakov. V\u00e1\u0161 developer je, ako inak, zanepr\u00e1zdnen\u00fd a vy nechcete do Google Analytics posiela\u0165 ni\u010d nehovoriaci re\u0165azec. Budete op\u00e4\u0165 vytv\u00e1ra\u0165 samostatn\u00e9 tagy a triggery pre ka\u017ed\u00fd jeden formul\u00e1r? Nie. Rie\u0161en\u00edm je op\u00e4\u0165 lookup table:<\/p>\n

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

V\u00fdstup, teda premenn\u00fa {{LT - Form Name}}<\/code>n\u00e1sledne pou\u017eijete v evente namiesto natvrdo zadefinovanej hodnoty (napr. v eventLabel). V\u0161imnite si, \u017ee v tomto pr\u00edpade je nastaven\u00e1 defaultn\u00e1 hodnota pre pr\u00edpad, \u017ee vstupn\u00e9 {{Form ID}}<\/code>sa nebude zhodova\u0165 ani s jedn\u00fdm \u00fadajom v tabu\u013eke. V takom pr\u00edpade sa v\u00e1m do Google Analytics odo\u0161le chybov\u00e1 hl\u00e1\u0161ka, na ktor\u00fa si m\u00f4\u017eete nastavi\u0165 automatick\u00e9 upozornenie e-mailom<\/a>. Ak niekto na web prid\u00e1 nov\u00fd formul\u00e1r a nepovie v\u00e1m o tom, zist\u00edte to hne\u010f po jeho prvom vyplnen\u00ed. \u0160ikovn\u00e9, \u017ee?<\/p>\n

Pr\u00edklad 3: Odpa\u013eovanie zna\u010diek len na niektor\u00fdch str\u00e1nkach<\/h2>\n

Je mno\u017estvo tagov, ktor\u00e9 potrebujete odp\u00e1li\u0165 len na niektor\u00fdch str\u00e1nkach. Jedn\u00fdm z nich m\u00f4\u017ee by\u0165 aj Hotjar tag a to v pr\u00edpade, ak chcete zozbiera\u0165 nahr\u00e1vky iba z niektor\u00fdch konkr\u00e9tnych str\u00e1nok. Rie\u0161en\u00edm je v tomto pr\u00edpade pageview trigger s nastavenou podmienkou pre jednotliv\u00e9 {{Page Path}}<\/code>. To je, samozrejme, v poriadku, ale predstavte si, \u017ee po t\u00fd\u017edni potrebujete obmeni\u0165 zoznam relevantn\u00fdch str\u00e1nok. M\u00f4\u017eete pracne upravova\u0165 regex v triggeri, alebo pou\u017ei\u0165 preh\u013eadn\u00fa lookup table, resp. ide\u00e1lne regex table, ktor\u00e1 funguje podobne, ale umo\u017e\u0148uje zad\u00e1va\u0165 podmienky v regex z\u00e1pise. Viac o pou\u017e\u00edvan\u00ed regexu sa do\u010d\u00edtate v na\u0161om star\u0161om \u010dl\u00e1nku<\/a>.<\/p>\n

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

Trigger bude vyzera\u0165 ve\u013emi jednoducho – jedin\u00e1 podmienka bude, \u017ee{{LT - Hotjar Page Selector}}<\/code>sa rovn\u00e1 hodnote „yes“. Odpad\u00e1 teda nutnos\u0165 p\u00edsa\u0165 komplikovan\u00e9 regexy, kde sa m\u00f4\u017eete \u013eahko pom\u00fdli\u0165.<\/p>\n

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

Pr\u00edklad 4: R\u00f4zne meracie k\u00f3dy pre r\u00f4zne dom\u00e9ny<\/h2>\n

Ak m\u00e1te viacero toto\u017en\u00fdch webov pre r\u00f4zne krajiny, pravdepodobne nebudete potrebova\u0165 zvl\u00e1\u0161\u0165 GTM kontajner pre ka\u017ed\u00fd jeden z nich. Aj tu v\u00e1m m\u00f4\u017ee pom\u00f4c\u0165 lookup table. V tomto pr\u00edpade bude tabu\u013eka nies\u0165 jednotliv\u00e9 meracie k\u00f3dy (UA k\u00f3dy) a n\u00e1sledne na \u0148u budete odkazova\u0165 z jednej v\u0161eobecnej Google Analytics Settings premennej. Ak potom nastav\u00edte jeden tag, bude automaticky fungova\u0165 pre x va\u0161ich \u010fal\u0161\u00edch webov. Geni\u00e1lne, \u010do poviete?<\/p>\n

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

Pr\u00edklad 5: IP filter v GTM<\/h2>\n

Na\u0161\u00edm ob\u013euben\u00fdm pr\u00edkladom pou\u017eitia lookup table (resp. presnej\u0161ie regex table) je IP filter definovan\u00fd v Google Tag Manageri. Princ\u00edp je tak\u00fd, \u017ee cez API tretej strany z\u00edskate IP adresu n\u00e1v\u0161tevn\u00edka a t\u00fato adresu po\u0161lete do dataLayera. V regex table zadefinujete v\u0161etky intern\u00e9, resp. klientsk\u00e9 IP adresy a vr\u00e1tite slovn\u00e9 ozna\u010denie, ktor\u00e9 budete posiela\u0165 do vlastnej dimenzie, napr. „klient“, „agent\u00fara“, „developer“ a pod. Posledn\u00fdm krokom je zadefinovanie filtra v Google Analytics, v ktorom u\u017e ale nebudete musie\u0165 pou\u017e\u00edva\u0165 IP adresy a zlo\u017eit\u00e9 regexy, ale vlastn\u00fa dimenziu<\/a> a jej hodnoty. Regex table pre IP filter bude vyzera\u0165 nasledovne:<\/p>\n

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

V\u00fdhodou tak\u00e9hoto rie\u0161enia je okrem zjednodu\u0161enej spr\u00e1vy IP filtra (najm\u00e4 vo v\u00e4\u010d\u0161\u00edch spolo\u010dnostiach s mno\u017estvom intern\u00fdch IP) najm\u00e4 to, \u017ee m\u00f4\u017eete pou\u017ei\u0165 anonymiz\u00e1ciu IP adries a IP filtre v\u00e1m bud\u00fa na\u010falej fungova\u0165. Tak\u00e9to rie\u0161enie je v s\u00falade s nariaden\u00edm GDPR. Implemen\u00e1cia je mo\u017eno trochu n\u00e1ro\u010dnej\u0161ia, tak\u017ee ak by ste mali z\u00e1ujem o tak\u00e9to rie\u0161enie, nev\u00e1hajte n\u00e1s oslovi\u0165, radi v\u00e1m s t\u00fdm pom\u00f4\u017eeme<\/a>.<\/p>\n

Otestujte si, \u010di va\u0161a lookup table funguje spr\u00e1vne<\/h2>\n

Len t\u00fd\u017ede\u0148 po zverejnen\u00ed tohto \u010dl\u00e1nku Google obohatil lookup table o \u0161ikovn\u00fa funkciu – priamo v lookup table si m\u00f4\u017eete otestova\u0165, ak\u00fa hodnotu v\u00e1m premenn\u00e1 vr\u00e1ti. Sta\u010d\u00ed, ak do valid\u00e1tora zad\u00e1te konkr\u00e9tnu hodnotu a stla\u010d\u00edte enter. V nastaven\u00ed va\u0161ich lookup table premenn\u00fdch to vyzer\u00e1 nasledovne:<\/p>\n

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

\u010eal\u0161ie pou\u017eitie lookup table premennej<\/h2>\n

Ako vid\u00edte, mo\u017enost\u00ed pou\u017eitia lookup table premenn\u00fdch s\u00fa obrovsk\u00e9 a z\u00e1le\u017e\u00ed len na va\u0161ej kreativite, ako lookup table vyu\u017eijete vo va\u0161om \u00fa\u010dte. Tak \u010do, in\u0161pirovali sme v\u00e1s? Alebo u\u017e lookup table vyu\u017e\u00edvate? Ak \u00e1no, nap\u00ed\u0161te n\u00e1m dole do koment\u00e1rov, budeme radi za ka\u017ed\u00fa in\u0161pir\u00e1ciu.<\/p>\n","protected":false},"excerpt":{"rendered":"

Za prv\u00fd rok m\u00f4jho p\u00f4sobenia v DASE sa mi pod ruky dostali desiatky GTM kontajnerov. V nich som…<\/p>\n","protected":false},"author":70,"featured_media":16841,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[809,637],"tags":[602],"_links":{"self":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/16818"}],"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\/70"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/comments?post=16818"}],"version-history":[{"count":19,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/16818\/revisions"}],"predecessor-version":[{"id":17903,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/16818\/revisions\/17903"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media\/16841"}],"wp:attachment":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media?parent=16818"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/categories?post=16818"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/tags?post=16818"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}