Consent Mode rozli\u0161uje p\u00e4\u0165 typov \u00falo\u017e\u00edsk:<\/p>\n
- \n
- analytics_storage<\/strong><\/li>\n
- ad_storage<\/strong><\/li>\n
- functionality_storage<\/strong><\/li>\n
- personalization_storage<\/strong><\/li>\n
- security_storage<\/strong><\/li>\n<\/ul>\n
Pam\u00e4tajte, \u017ee Consent Mode je st\u00e1le v beta verzi\u00ed a je teda pravdepodobn\u00e9, \u017ee sa e\u0161te m\u00f4\u017eu veci zmeni\u0165 pred t\u00fdm, ne\u017e bude ofici\u00e1lne spusten\u00fd.<\/p>\n
Princ\u00edp fungovania<\/h2>\n
Pri na\u010d\u00edtan\u00ed webu je potrebn\u00e9 zadefinova\u0165 predvolen\u00fa \u00farove\u0148 consentu pre ka\u017ed\u00fd typ \u00falo\u017eiska. Ak tento krok vynech\u00e1te, predvolen\u00e1 hodnota bude \u201cgranted\u201d pre v\u0161etky typy \u00falo\u017e\u00edsk – to znamen\u00e1,. \u017ee sa bude jedna\u0165 o tzv. opt-out m\u00f3d, ke\u010f sa d\u00e1ta bud\u00fa odosiela\u0165 v \u0161tandardnom m\u00f3de a a\u017e po zak\u00e1zan\u00ed pr\u00edstupu k ist\u00fdm \u00falo\u017eisk\u00e1m sa bude logika meni\u0165.<\/p>\n
Ak chcete implementova\u0165 opt-in m\u00f3d (ktor\u00fd je odpor\u00fa\u010dan\u00fd), mus\u00edte nastavi\u0165 predvolen\u00e9 hodnoty manu\u00e1lne. V tomto pr\u00edpade bud\u00fa v\u0161etky \u00falo\u017eisk\u00e1 predvolene vypnut\u00e9 a pou\u017e\u00edvate\u013e sa m\u00f4\u017ee rozhodn\u00fa\u0165, ktor\u00e9 z nich povol\u00ed, a ktor\u00e9 ponech\u00e1 vypnut\u00e9.<\/p>\n
Aby ste zadefinovali predvolen\u00fa \u00farove\u0148 consentu, mus\u00edte zavola\u0165 nasleduj\u00facu funkciu (je pritom jedno, \u010di vyu\u017e\u00edvate GTM alebo gtag.js):<\/p>\n
gtag(\"consent\", \"default\", {\r\nad_storage: \"denied\",\r\nanalytics_storage: \"denied\",\r\nfunctionality_storage: \"denied\",\r\npersonalization_storage: \"denied\",\r\nsecurity_storage: \"granted\",\r\nwait_for_update: 2000\r\n});<\/pre>\nPri upraven\u00ed \u00farovne consentu je potrebn\u00e9 zavola\u0165 funkciu ni\u017e\u0161ie a upravi\u0165 \u00farove\u0148 consentu pre jednotliv\u00e9 \u00falo\u017eisk\u00e1 z \u201cdenied\u201d na \u201cgranted\u201d:<\/p>\n
gtag('consent', 'update', {\r\nad_storage: 'denied',\r\nanalytics_storage: 'granted'\r\n});<\/pre>\nTaktie\u017e m\u00e1te mo\u017enos\u0165 upravi\u0165 \u00farove\u0148 consentu len pre ur\u010dit\u00fd regi\u00f3n, pridan\u00edm atrib\u00fatu \u2018region\u2019:<\/p>\n
gtag('consent', 'default', {\r\nad_storage: 'denied',\r\nanalytics_storage: 'denied',\r\nwait_for_update: 2000,\r\nregion: ['US','UK']\r\n});<\/pre>\nSpr\u00e1vanie tagov<\/h2>\n
Zameriam sa na GAds a Floodlight tagy pre marketing a UA a GA4 tagy, nako\u013eko tieto tagy maj\u00fa sofistikovanej\u0161iu integr\u00e1ciu a nie s\u00fa automaticky blokovan\u00e9, ako in\u00e9 tagy.<\/p>\n
Google Ads a Floodlight<\/h3>\n
Google Ads a Floodlight tagy po\u017eaduj\u00fa ad_storage.<\/p>\n
![\"google](\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/Consent-mode-1.png\")
<\/a><\/p>\nConsent Mode pre Google Ads a Floodlight tagy.<\/em><\/p>\n
Ak ad_storage nie je povolen\u00fd, Google Ads a Floodlight tagy:<\/strong><\/p>\n
- \n
- Ak URL obsahuje gclid parameter, tento parameter nebude zap\u00edsan\u00fd do first-party cookie. Navy\u0161e, ak u\u017e nejak\u00e9 marketingov\u00e9 cookies existuj\u00fa, nebud\u00fa \u010d\u00edtan\u00e9<\/li>\n<\/ul>\n
\u00a0<\/strong><\/p>\n
Ak ad_storage nie je povolen\u00fd, m\u00e1te mo\u017enos\u0165 e\u0161te viac obmedzi\u0165, ak\u00e9 d\u00e1ta bud\u00fa do Google Ads alebo Doubleclick-u odosielan\u00e9 zavolan\u00edm funkcie:<\/p>\n
gtag('set', 'ads_data_redaction', true);<\/pre>\n\u00a0<\/strong>Ak je parameter ads_data_redaction nastaven\u00fd na hodnotu true, hity, ktor\u00e9 sl\u00fa\u017eia na marketingov\u00e9 \u00fa\u010dely bud\u00fa presmerovan\u00e9 z dom\u00e9n doubleclick.com a google.com cez googleadsindication.com. T\u00fdm sa nebud\u00fa uklada\u0165 \u017eiadne marketingov\u00e9 cookies (cookies tret\u00edch str\u00e1n). Navy\u0161e, z URL adresy bud\u00fa odstr\u00e1nen\u00e9 ak\u00e9ko\u013evek identifik\u00e1tory, ktor\u00e9 boli pridan\u00e9 po kliknut\u00ed na reklamu (napr. gclid).<\/strong><\/p>\n
Universal Analytics a GA4<\/h3>\n
Druhou sadou tagov, ktor\u00e9 maj\u00fa integr\u00e1ciu s Consent Mode-om priamo zabudovan\u00fa s\u00fa analytick\u00e9 tagy Google Analytics, a to ako pre Universal Analytics, tak pre Google Analytics 4. Tieto tagy okrem analytics_storage vy\u017eaduj\u00fa, podobne ako je to v pr\u00edpade Google Ads a Floodlight tagov, aj ad_storage.<\/p>\n
![\"Google](\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/Consent-mode-2.png\")
<\/a><\/p>\nConsent Mode pre Universal Analytics a GA4 tagy.<\/em><\/p>\n
V pr\u00edpade, \u017ee ad_storage nie je povolen\u00fd:<\/strong><\/p>\n
- \n
- Google Analytics nebude \u010d\u00edta\u0165 ani zapisova\u0165 marketingov\u00e9 cookies. Taktie\u017e cookies nebud\u00fa m\u00f4c\u0165 by\u0165 vyu\u017eit\u00e9 pre Google Signals.<\/li>\n<\/ul>\n
V pr\u00edpade, \u017ee analytics_storage nie je povolen\u00fd:<\/strong><\/p>\n
- \n
- Google Analytics script nem\u00f4\u017ee \u010d\u00edta\u0165 ani uklada\u0165 first-party cookies (_ga cookie). _ga cookie obsahuje Client ID – identifik\u00e1tor, ktor\u00fd Google Analytics vyu\u017e\u00edva na rozli\u0161ovanie hitov z toho ist\u00e9ho zariadenia a prehliada\u010da (\u010d\u00edm vytv\u00e1ra metriku Pou\u017e\u00edvatelia, alebo Users). Pokia\u013e je pr\u00edstup k analytick\u00e9mu \u00falo\u017eisku zamietnut\u00fd, t\u00e1to cookie nem\u00f4\u017ee by\u0165 ulo\u017een\u00e1, preto je identifik\u00e1tor Client ID vygenerovan\u00fd n\u00e1hodne pri ka\u017edom na\u010d\u00edtan\u00ed str\u00e1nky. Consent Mode teda nezabra\u0148uje odosielanie d\u00e1t do Google Analytics, ale zabra\u0148uje ukladaniu a \u010d\u00edtaniu cookies.<\/li>\n
- Hoci sa tieto d\u00e1ta to Google Analytics odosielaj\u00fa, nemus\u00edte sa b\u00e1\u0165, \u017ee v\u00e1m integrovan\u00edm Consent Mode-u rap\u00eddne vzrastie po\u010det pou\u017e\u00edvate\u013eov. Tieto d\u00e1ta s\u00fa odosielan\u00e9 s parametrom gcs – hity, ktor\u00e9 tento parameter obsahuj\u00fa sa nezobrazuj\u00fa v \u0161tandardn\u00fdch reportoch GA. Pre\u010do ich teda Google v\u00f4bec posiela? Je pravdepodobn\u00e9, \u017ee tieto d\u00e1ta bud\u00fa v bud\u00facnosti vyu\u017eit\u00e9 pri modelovan\u00ed spr\u00e1vania pou\u017e\u00edvate\u013eov – na z\u00e1klade d\u00e1t, ktor\u00e9 ste z\u00edskali od pou\u017e\u00edvate\u013eov s povolen\u00fdm analytick\u00fdm \u00falo\u017eiskom sa vytvor\u00ed model, ktor\u00fd odhadne metriky pre druh\u00fa skupinu pou\u017e\u00edvate\u013eov, ktor\u00fd consent neudelili. Je ot\u00e1zne kedy a ako bud\u00fa tieto d\u00e1ta spr\u00edstupnen\u00e9, ale som si ist\u00fd, \u017ee Google na nie\u010dom podobnom pracuje.<\/li>\n<\/ul>\n
Ostatn\u00e9 typy tagov<\/h3>\n
Pre ostatn\u00e9 typy tagov m\u00e1te mo\u017enos\u0165 nastavi\u0165 po\u017eadovan\u00e9 \u00farovne consentu v ka\u017edom jednom tagu osobitne. Na rozdiel od tagov od Google-u, ktor\u00e9 pod\u013ea \u00farovne consentu menia d\u00e1ta, ktor\u00e9 sa odosielaj\u00fa a znemo\u017e\u0148uj\u00fa \u010d\u00edta\u0165 a uklada\u0165 cookies, ostatn\u00e9 tagy bud\u00fa bez dostato\u010dnej \u00farovne consentu zablokovan\u00e9.<\/p>\n
![\"Google](\"https:\/\/www.dase-analytics.com\/blog\/wp-content\/uploads\/Consent-mode-3.png\")
<\/a><\/p>\n
- Google Analytics nebude \u010d\u00edta\u0165 ani zapisova\u0165 marketingov\u00e9 cookies. Taktie\u017e cookies nebud\u00fa m\u00f4c\u0165 by\u0165 vyu\u017eit\u00e9 pre Google Signals.<\/li>\n<\/ul>\n
- ad_storage<\/strong><\/li>\n