{"id":18149,"date":"2022-01-31T11:13:18","date_gmt":"2022-01-31T09:13:18","guid":{"rendered":"https:\/\/www.dase-analytics.com\/blog\/?p=18149\/"},"modified":"2022-01-31T12:10:47","modified_gmt":"2022-01-31T10:10:47","slug":"analytics-news-januar-2022","status":"publish","type":"post","link":"https:\/\/www.dase-analytics.com\/blog\/sk\/analytics-news-januar-2022\/","title":{"rendered":"Neleg\u00e1lny Analytics a m\u0155tvy FLoC. Za\u010diatok roka ako z ve\u013ekej knihy"},"content":{"rendered":"

Nov\u00fd Cross-channel Data-driven atribu\u010dn\u00fd model v Google Analytics 4<\/h2>\n

Ak sledujete atribu\u010dn\u00e9 reporty vo svojej GA4-ke, t\u00e1to novinka v\u00e1s neprekvap\u00ed. Nov\u00fd Cross-channel Data-driven<\/a> atribu\u010dn\u00fd model je odteraz dostupn\u00fd v oboch atribu\u010dn\u00fdch reportoch (Conversion Paths a Model Comparison) bez oh\u013eadu na to, ak\u00fd ve\u013ek\u00fd web spravujete. Ak n\u00e1hodou neviete, kde h\u013eada\u0165 atribu\u010dn\u00e9 reporty, tak ich n\u00e1jdete v sekcii Advertiser a nie medzi ostatn\u00fdmi reportami.<\/p>\n

Nov\u00fd atribu\u010dn\u00fd model<\/a> bol pridan\u00fd aj do selektora v sekcii nastavenie atrib\u00facie (Admin > Attribution Settings > Reporting attribution model). Pri zvolen\u00ed data-driven atribu\u010dn\u00e9ho modelu sa bud\u00fa v\u0161etky metriky s\u00favisiace s n\u00e1kupmi, t.j. Total Conversions, Total Revenue, Total Ad Revenue a Purchase Revenue pripisova\u0165 kan\u00e1lu pomerovo pod\u013ea data-driven atribu\u010dn\u00e9ho modelu. Nez\u013eaknite sa, ak va\u0161e PPC kampane vygeneruj\u00fa 13,7 n\u00e1kupov. Nie je to bug, je to feature.<\/p>\n

\"new<\/p>\n

Viac na: Google Support<\/a><\/p>\n

Pou\u017e\u00edvanie Google Analytics je protiz\u00e1konn\u00e9. Nastal \u010das na paniku?<\/h2>\n

V uplynul\u00fdch d\u0148och rozd\u00fachalo v\u00e1\u0161ne v analytickom svete rozhodnutie rak\u00faskeho s\u00fadneho dvora, pod\u013ea ktor\u00e9ho pou\u017e\u00edvanie Google Analytics poru\u0161uje eur\u00f3pske z\u00e1kony, konkr\u00e9tne rozhodnutie Eur\u00f3pskeho s\u00fadneho dvora (CJEU) z roku 2020. Eur\u00f3psky s\u00fadny dvor vtedy kon\u0161tatoval, \u017ee pou\u017e\u00edvanie americk\u00fdch analytick\u00fdch a marketingov\u00fdch n\u00e1strojov poru\u0161uje GDPR, ke\u010f\u017ee americk\u00e9 z\u00e1kony o doh\u013eade vy\u017eaduj\u00fa od americk\u00fdch poskytovate\u013eov ako Google alebo Facebook, aby poskytli osobn\u00e9 \u00fadaje americk\u00fdm \u00faradom.<\/p>\n

Zatia\u013e je situ\u00e1cia nejasn\u00e1 a to aj v odbornej komunite. Vzniklo mno\u017estvo r\u00f4znych interpret\u00e1ci\u00ed tohto rozhodnutia. V niektor\u00fdch sa ako hlavn\u00fd probl\u00e9m uv\u00e1dza, \u017ee d\u00e1ta o eur\u00f3pskych pou\u017e\u00edvate\u013eoch s\u00fa ukladan\u00e9 na serveroch v USA, v in\u00fdch zase \u017ee probl\u00e9mom je zdie\u013eanie IP adries<\/a> pou\u017e\u00edvate\u013eov s t\u00fdmito mimoeur\u00f3pskymi slu\u017ebami. Dokonca sa objavuje aj n\u00e1zor, \u017ee nez\u00e1le\u017e\u00ed na tom, kde s\u00fa d\u00e1ta ulo\u017een\u00e9 alebo spracovan\u00e9, ale z\u00e1le\u017e\u00ed na tom, kde m\u00e1 dan\u00e1 spolo\u010dnos\u0165 s\u00eddlo, tzn. ak m\u00e1 Google hlavn\u00e9 s\u00eddlo v USA, je irelevantn\u00e9, ak by aj d\u00e1ta o EU pou\u017e\u00edvate\u013eoch ost\u00e1vali v EU, st\u00e1le by tak\u00e9to zbieranie d\u00e1t bolo v rozpore s GDPR<\/a>. Toto by v\u0161ak bol katastrofick\u00fd scen\u00e1r vzh\u013eadom na to, \u017ee v\u0161etci ve\u013ek\u00ed svetov\u00ed hr\u00e1\u010di na trhu s online marketingov\u00fdmi n\u00e1strojmi s\u00fa z USA, \u010do by znemo\u017e\u0148ovalo ich pou\u017e\u00edvanie.<\/p>\n

Ka\u017edop\u00e1dne t\u00fato t\u00e9mu budeme na\u010falej sledova\u0165 za v\u00e1s.<\/p>\n

Viac na: NOYB<\/a><\/p>\n

FLoC je m\u0155tve, nech \u017eije Topics API<\/h2>\n

Nie je to tak d\u00e1vno, \u010do sme v\u00e1s informovali o technol\u00f3gii FLoC, ktor\u00e1 mala nahradi\u0165 cookies tret\u00edch str\u00e1n<\/a>. Dnes je op\u00e4\u0165 v\u0161etko inak. Nov\u00fdm \u0161tandardom m\u00e1 by\u0165 pod\u013ea Googlu Topics API. O \u010do vlastne ide?<\/p>\n

Princ\u00edp fungovania Topics API je v z\u00e1sade jednoduch\u00fd. Rozhranie Topics API<\/a> vyberie t\u00e9my, ktor\u00e9 n\u00e1v\u0161tevn\u00edka zauj\u00edmaj\u00fa (na z\u00e1klade hist\u00f3rie prehliadania pou\u017e\u00edvate\u013ea za posledn\u00e9 tri t\u00fd\u017edne) a prezdie\u013ea tieto t\u00e9my so z\u00fa\u010dastnen\u00fdmi str\u00e1nkami. Cel\u00e9 to prebehne bez zapojenia extern\u00fdch serverov, a teda bez cookies. Google v najbli\u017e\u0161\u00edch t\u00fd\u017ed\u0148och pl\u00e1nuje spusti\u0165 sk\u00fa\u0161obn\u00fa verziu, pri\u010dom sa zaviazal, \u017ee kone\u010dn\u00fa podobu z\u00edska Topics API po d\u00f4kladnom testovan\u00ed a na z\u00e1klade sp\u00e4tnej v\u00e4zby od u\u017e\u00edvate\u013eov.<\/p>\n

Tejto t\u00e9me sa budeme ur\u010dite venova\u0165 na na\u0161om blogu podrobnej\u0161ie. Zosta\u0148te naladen\u00ed, alebo sa prihl\u00e1ste na odber newslettera.<\/p>\n

Viac na: Search Engine Land<\/a><\/p>\n

JSON v BigQuery<\/h2>\n

Na z\u00e1ver jedna kr\u00e1tka spr\u00e1va aj zo sveta „ve\u013ek\u00fdch d\u00e1t<\/a>„. BigQuery<\/a> SQL odteraz podporuje nov\u00fd d\u00e1tov\u00fd typ, ktor\u00fdm je JSON. M\u00f4\u017eete tak uklada\u0165 svoje JSON d\u00e1ta, \u010do m\u00f4\u017ee by\u0165 v niektor\u00fdch pr\u00edpadoch ve\u013emi v\u00fdhodn\u00e9. \u0160trukt\u00farovan\u00e9 d\u00e1ta ulo\u017een\u00e9 v JSON toti\u017e nevy\u017eaduj\u00fa nastavenie d\u00e1tovej sch\u00e9my.<\/p>\n

Viac na: Google Support<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Nov\u00fd Cross-channel Data-driven atribu\u010dn\u00fd model v Google Analytics 4 Ak sledujete atribu\u010dn\u00e9 reporty vo svojej GA4-ke, t\u00e1to novinka…<\/p>\n","protected":false},"author":70,"featured_media":18153,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[669],"tags":[673,604,798],"_links":{"self":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/18149"}],"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=18149"}],"version-history":[{"count":6,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/18149\/revisions"}],"predecessor-version":[{"id":18157,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/18149\/revisions\/18157"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media\/18153"}],"wp:attachment":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media?parent=18149"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/categories?post=18149"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/tags?post=18149"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}