{"id":3722,"date":"2024-02-18T19:26:53","date_gmt":"2024-02-18T17:26:53","guid":{"rendered":"https:\/\/webanalyst.ro\/?p=3722"},"modified":"2026-06-21T16:24:24","modified_gmt":"2026-06-21T13:24:24","slug":"google-consent-mode","status":"publish","type":"post","link":"https:\/\/webanalyst.ro\/blog\/2024\/google-consent-mode\/","title":{"rendered":"Google Consent Mode"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Google \u0219i-a anun\u021bat clien\u021bii c\u0103, \u00eencep\u00e2nd cu martie 2024, trebuie s\u0103 implementeze \u00een site-uri \u0219i aplica\u021bii modulul de consim\u021b\u0103m\u00e2nt sau <strong>Consent Mode<\/strong>, \u00een englez\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Reglement\u0103rile europene (despre care voi detalia mai jos) le interzic companiilor de tehnologie s\u0103 proceseze date despre utilizatori f\u0103r\u0103 acordul acestora. Ca un exemplu, Meta (compania care de\u021bine Facebook, Instagram \u0219i WhatsApp) a anun\u021bat abonamente pl\u0103tite la serviciile sale pentru utilizatorii care nu sunt de acord s\u0103 \u00ee\u0219i ofere informa\u021biile c\u0103tre companie.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen schimb, Google le cere celor care folosesc Google Ads, Google Analytics sau Google Floodlight (necesar pentru Search Ads 360, Campaign Manager 360 sau Display &amp; Video 360) s\u0103 implementeze Consent Mode, prin care informa\u021biile de compotament \u00een aplica\u021bii \u0219i de conversie vor ajunge (oarecum) la Google, inclusiv pentru utilizatorii care nu \u0219i-au dat consim\u021b\u0103m\u00e2ntul \u00een acest sens. Cu o solu\u021bie asem\u0103n\u0103toare cu aceasta au venit \u0219i cei de la Microsoft pentru utilizarea Bing Ads \u0219i Clarity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Avertismenul a ap\u0103rut \u00een ultimele luni \u00een Google Ads, iar de c\u00e2teva zile apare \u0219i \u00een set\u0103rile din Google Analytics, \u00een pagina cu informa\u021biile despre data stream:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"937\" height=\"392\" src=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/ga-consent.png\" alt=\"\" class=\"wp-image-3747\" srcset=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/ga-consent.png 937w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/ga-consent-300x126.png 300w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/ga-consent-150x63.png 150w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/ga-consent-768x321.png 768w\" sizes=\"auto, (max-width: 937px) 100vw, 937px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">\u00centre timp, a ap\u0103rut \u0219i versiunea 2 de la Google Consent Mode, care aduce c\u00e2teva semnale noi, comparativ cu versiunea ini\u021bial\u0103, din 2020. Voi detalia \u00een continuarea acestui articol.<\/p>\n\n\n\n<!--more-->\n\n\n\n<h2 class=\"wp-block-heading\">Reglement\u0103ri europene<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Sunt c\u00e2teva regulamente europene care deja se aplic\u0103 \u0219i care au dus, printre altele, \u0219i la ce vedem ast\u0103zi legat de <em>cookie management<\/em> \u0219i de <em>consent management<\/em>. Acestea sunt:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>E-Privacy<\/strong> &#8211; impune reguli stricte privind utilizarea de cookie-uri \u0219i ofer\u0103 reguli despre ob\u021binerea consim\u021b\u0103m\u00e2ntului de la utilizatori, lucru care poate afecta site-urile<\/li>\n\n\n\n<li><strong>GDPR<\/strong> &#8211; impune faptul c\u0103 datele personale, inclusiv cele ob\u021binute din cookie-uri, trebuie s\u0103 aib\u0103 o baz\u0103 legal\u0103<\/li>\n\n\n\n<li><strong>Digital Market Act<\/strong> &#8211; \u00een pofida lucrurilor vehiculate \u00een ultimul timp, DMA nu afecteaz\u0103 partea de cookies &amp; consent management; aceasta se adreseaz\u0103 juc\u0103torilor foarte mari din zona de internet \u0219i \u021bine de corectitudinea acestora \u0219i de \u00eencurajarea competi\u021biei online<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Acestea sunt legile care se aplic\u0103 acum, dar trebuie s\u0103 \u0219tim c\u0103 \u00een viitorul apropiat vom avea \u0219i alte reglement\u0103ri europene privind spa\u021biul digital, care s-ar putea s\u0103 ne afecteze, precum:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Network and Information Security Directive<\/strong> &#8211; ini\u021bial a fost o recomandare (NIS1), dar din octombrie 2024 se va aplica NIS2, care este o directiv\u0103, deci va fi obligatorie \u0219i se refer\u0103 la securitatea digital\u0103 a organiza\u021biilor; impune \u0219i localizarea datelor, anun\u021barea public\u0103 a incidentelor \u0219i audituri<\/li>\n\n\n\n<li><strong>Digital Services Act<\/strong> &#8211; se adreseaz\u0103 protec\u021biei drepturilor fundamentale \u00een mediul online<\/li>\n\n\n\n<li><strong>Data Act<\/strong> &#8211; se refer\u0103 la distribuirea datelor<\/li>\n\n\n\n<li><strong>European Digital Identity<\/strong> -se refer\u0103 la identitatea online a cet\u0103\u021benilor, inclusiv documente digitale<\/li>\n\n\n\n<li><strong>Cyber Resilience Act<\/strong> &#8211; se refer\u0103 la reguli de securitate pentru to\u021bi produc\u0103torii de hardware \u0219i software<\/li>\n\n\n\n<li><strong>Chips Act<\/strong> &#8211; \u00eencurajeaz\u0103 produc\u021bia de semiconductoare \u00een UE<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Consent management<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Revenind la problema noastr\u0103 \u0219i implementarea pe care trebuie s\u0103 o facem pentru Google, trebuie \u00een primul r\u00e2nd s\u0103 facem distinc\u021bia dintre <em>consent management<\/em> \u0219i <em>consent mode<\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ceea ce ne ofer\u0103 Google drept Consent Mode <strong>nu este un instrument de consent management<\/strong>. Fiecare site sau aplica\u021bie trebuie s\u0103 aib\u0103 o solu\u021bie de consent management, prin care fiecare utilizator s\u0103 poat\u0103 decide ce se \u00eent\u00e2mpl\u0103 cu datele colectate de la acesta prin cookie-uri.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 ce avem o solu\u021bie func\u021bional\u0103 de <strong>consent management<\/strong>, putem \u00eencepe implementarea de Consent Mode de la Google.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen acest moment, Google are parteneriat cu 15 companii care ofer\u0103 <em>consent management<\/em>, deci confirm\u0103 c\u0103 solu\u021biile oferite de acestea sunt conforme cu propriul s\u0103u <em>consent mode<\/em>. Acestea produse sunt: <em>Commanders Act<\/em>, <em>Complianz<\/em>, <em>ConsentManager<\/em>, <em>Cookie First<\/em>, <em>Cookie Information<\/em>, <em>Cookie Script<\/em>, <em>Cookiebot<\/em>, <em>CookieYes<\/em>, <em>Didomi<\/em>, <em>iubenda<\/em>, <em>OneTrust<\/em>, <em>Osano<\/em>, <em>Sirdata<\/em>, <em>Termly<\/em> \u0219i <em>Usercentrics<\/em>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Semnale \u00een Consent mode<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru utilizatorii care nu \u0219i-au dat acordul ca datele lor s\u0103 fie proceaste, Google folose\u0219te Consent mode, prin care \u00eencearc\u0103 s\u0103 primeasc\u0103 acelea\u0219i date. Nu vor reu\u0219i de la to\u021bi nici av\u00e2nt implementat consent mode, dar urmeaz\u0103 modelarea datelor, prin care Google \u00eencearc\u0103 s\u0103 estimeze comportamentul online al celorlal\u021bi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen prima versiune de Consent mode oferit\u0103 de Google, existau 2 semnale:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>ad_storage<\/code> &#8211; pentru cookie-uri de publicitate<\/li>\n\n\n\n<li><code>analytics_storage<\/code> &#8211; pentru cookie-uri web \u0219i ID-ul dispozitivului la aplica\u021bii mobile, folosite pentru analytics<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen versiunea a doua (V2) de Consent mode, acestora li se adaug\u0103 \u0219i:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>ad_user_data<\/code> &#8211; con\u021bine r\u0103spunsul utilizatorului legat de publicitate<\/li>\n\n\n\n<li><code>ad_personalization<\/code> &#8211; con\u021bine r\u0103spunsul utilizatorului dac\u0103 vrea s\u0103 fie remarketat<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Tot \u00een V2 exist\u0103 \u0219i alte semnale, dar <strong>op\u021bionale<\/strong>. Prefer s\u0103 nu intru \u00een detalii, dar cei interesa\u021bi pot citi mai multe despre acest lucru \u00een documenta\u021bia tehnic\u0103 de la Google. \u00cen plus, acestea pot fi diferite \u0219i \u00een func\u021bie de instrumentul de <em>Consent management<\/em> folosit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Tipuri de Consent mode<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Versiunea 2 de Consent mode vine cu dou\u0103 tipuri diferite de implementare:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>De baz\u0103<\/strong> &#8211; va colecta date doar despre persoanele care \u0219i-au dat acordul<\/li>\n\n\n\n<li><strong>Avansat<\/strong> &#8211; este asem\u0103n\u0103tor \u0219i cu prima versiune de Consent mode, adic\u0103 va colecta date despre persoanele care \u0219i-au dat acordul, dar \u0219i despre cei care nu \u0219i-au dat acordul<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte de a trece la detalii despre implementarea Consent Mode, cred c\u0103 to\u021bi ne \u00eentreb\u0103m ce se \u00eent\u00e2mpl\u0103 dac\u0103 nu set\u0103m Google Consent Mode, eventual \u0219i versiunea pe care ar trebui s\u0103 o implement\u0103m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce se \u00eent\u00e2mpl\u0103 dac\u0103 nu set\u0103m Consent Mode<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">La \u00eenceputul articolului, am scris c\u0103 Google le-a cerut clien\u021bilor s\u0103 implementeze modulul de consim\u021b\u0103m\u00e2nt. Desigur, fiecare proprietar de site sau de aplica\u021bie decide dac\u0103 vrea acest lucru. Legea spune c\u0103 utilizatorii pot alege dac\u0103 vor <em>cookies<\/em> sau nu, dar acet lucru se poate face \u0219i f\u0103r\u0103 Google, Microsoft, Meta, TikTok etc.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen schimb, utilizatorii serviciilor de publicitate \u0219i analytics de la Google vor avea mai pu\u021bine date \u00een conturi dac\u0103 nu implementeaz\u0103 Consent Mode. Mai exact, dac\u0103 <strong>nu este implementat\u0103 nicio versiune de Consent mode, atunci nu vor mai avea date de la utilizatorii care nu \u00ee\u0219i dau acordul pentru <em>cookies<\/em>.<\/strong> <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen acest caz, nu vom avea acces la audien\u021bele de utilizatori. C\u00e2nd spun audien\u021be m\u0103 refer la multe func\u021bionalit\u0103\u021bi diferite, mai ales din Google Ads, care nu vor mai fun\u021biona, precum:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Remarketing<\/strong><\/li>\n\n\n\n<li>Audience Insights<\/li>\n\n\n\n<li>Audience Customization<\/li>\n\n\n\n<li>Lookalike Audiences<\/li>\n\n\n\n<li>Customer Match<\/li>\n\n\n\n<li>Conersion Modeling<\/li>\n\n\n\n<li>New Customer Acquisition <\/li>\n\n\n\n<li>Cross Device Tracking<\/li>\n\n\n\n<li>Dynamic Shopping Ads (la r\u00e2ndul s\u0103u, folose\u0219te \u0219i remarketing)<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru a avea acces la datele utilizatorilor la fel ca p\u00e2n\u0103 acum, inclusiv pentru a crea audien\u021be, suntem nevoi\u021bi s\u0103 implement\u0103m Consent Mode V2, versiunea avansat\u0103, dup\u0103 cum voi detalia \u00een continuare.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pe e alt\u0103 parte, site-urile \u0219i aplica\u021biile care nu sunt promovate prin publicitatea de la Google nu prea au nevoie de versiunea avansat\u0103 de la Consent mode.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Implementarea Consent Mode \u00een Google Tag Manager<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen primul r\u00e2nd, <a href=\"https:\/\/webanalyst.ro\/blog\/2023\/google-tag-in-gtm\/\">Google Tag<\/a> din GTM va trebui s\u0103 ruleze c\u00e2t mai rapid posibil la \u00eenc\u0103rcarea paginii. \u00cen acest sens, \u00een Google Tag Manager exist\u0103 un trigger special setat \u00een acest sens, numit <strong>Consent Initialization<\/strong>.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"925\" height=\"185\" src=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/gtm-consent-initialization.png\" alt=\"\" class=\"wp-image-3727\" srcset=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/gtm-consent-initialization.png 925w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/gtm-consent-initialization-300x60.png 300w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/gtm-consent-initialization-150x30.png 150w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/gtm-consent-initialization-768x154.png 768w\" sizes=\"auto, (max-width: 925px) 100vw, 925px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">A\u0219adar, dac\u0103 vrem s\u0103 rul\u0103m versiunea avansat\u0103 din Consent mode V2, tag-ul nu ar mai trebui s\u0103 apar\u0103 la <em>All pages<\/em>, ci la <em>Consent Initialization &#8211; All Pages<\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">La setarea unui Google Tag \u00een GTM, avem op\u021biunea de a seta <strong>Consent Settings<\/strong>, ascuns\u0103 \u00een <em>Advanced Settings<\/em>. Dac\u0103 ne uit\u0103m la un tag deja existent, vom vedea c\u0103 acesta deja verific\u0103 <code>ad_storage<\/code> \u0219i <code>analytics_storage<\/code>, semnalele ini\u021biale de care scriam mai sus.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"801\" height=\"838\" src=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/google-tag-consent.png\" alt=\"\" class=\"wp-image-3729\" style=\"width:801px;height:auto\" srcset=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/google-tag-consent.png 801w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/google-tag-consent-287x300.png 287w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/google-tag-consent-143x150.png 143w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/google-tag-consent-768x803.png 768w\" sizes=\"auto, (max-width: 801px) 100vw, 801px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A\u0219a cum scriam mai sus, pentru versiunea 2 avem de implementat \u00eenc\u0103 dou\u0103 semnale. Acestea vor trebui setate folosind op\u021biunea <em>Require additional consent for tag to fire<\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Observ ast\u0103zi c\u0103 toate cele 4 semnale sunt deja implementate. Verifica\u021bi acest lucru \u00een conturile de GTM \u0219i s-ar putea s\u0103 observa\u021bi c\u0103 <strong>Google deja s-a ocupat de implementarea tag-ului pentru to\u021bi utilizatorii de Tag Manager<\/strong>! \u00cen acest caz, mai trebuie doar setat <em>trigger<\/em>-ul corect pentru tag, a\u0219a cum am scris mai sus \u0219i setarea tag-urilor \u00een Google Tag Manager e gata \u00een doar c\u00e2teva secunde.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cum verific\u0103m dac\u0103 am implementat corect<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 \u00eenc\u0103rc\u0103m o pagin\u0103 din site, ne putem uita \u00een browser la sec\u021biunea <strong>Inspect<\/strong>, tab-ul <strong>Network<\/strong>. Pentru a verifica dac\u0103 versiunea de baz\u0103 este implementat\u0103, c\u0103ut\u0103m parametrul <code>&amp;gcs<\/code>. Dac\u0103 este implementat\u0103 versiunea avanst\u0103 de Consent Mode, ar trebui s\u0103 g\u0103sim \u0219i parametrul <code>&amp;gcd<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru a c\u0103uta mai u\u0219or \u00eentre <em>network requests<\/em>, avem \u00een <em>Network<\/em> o c\u0103su\u021b\u0103 de c\u0103utare care ne va ajuta. Dac\u0103 le g\u0103sim aici, \u00eenseamn\u0103 c\u0103 implementarea a fost realizat\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">La un click pe numele acestui request din rezultatele c\u0103ut\u0103rii de mai sus, vom vedea informa\u021biile formatate mai simplu \u0219i u\u0219or de citit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ideal ar fi ca \u00een noua fereastr\u0103 s\u0103 vedem cei doi parametri de mai sus, \u00eempreun\u0103 cu valori pentu fiecare.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"519\" height=\"198\" src=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/consent-mode-inspect.png\" alt=\"\" class=\"wp-image-3731\" srcset=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/consent-mode-inspect.png 519w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/consent-mode-inspect-300x114.png 300w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/consent-mode-inspect-150x57.png 150w\" sizes=\"auto, (max-width: 519px) 100vw, 519px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Valori pe care le poate avea parametrul <code>&amp;gcs<\/code>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>G100<\/code> &#8211; pentru utilizatorii care nu \u0219i-au dat consim\u021b\u0103m\u00e2ntul<\/li>\n\n\n\n<li><code>G111<\/code> &#8211; \u0219i-au dat acordul pentru Google Analytics \u0219i Google Ads<\/li>\n\n\n\n<li><code>G101<\/code> &#8211; \u0219i-au dat acordul pentru Analytics, dar nu \u0219i pentru Ads<\/li>\n\n\n\n<li><code>G110<\/code> &#8211; \u0219i-au dat acordul pentru Ads, dar nu \u0219i pentru Analytics<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Parametrul <code>&amp;gcd<\/code> va afi\u0219a ca valoare un \u0219ir de caractere, care va transmite pentru fiecare semnal dac\u0103 \u0219i-au dat sau nu acordul, \u0219i c\u00e2nd s-a \u00eent\u00e2mplat acest lucru. Dac\u0103 acordul era dat de la \u00eenceput va ap\u0103rea \u00een comanda <code>default<\/code>, iar dac\u0103 l-a acordat ulterior va ap\u0103rea la comanda <code>update<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen \u0219irul de caractere ini\u021bial, vom avea cifre \u0219i litere. De exemplu, litera <code>q<\/code> \u00eenseamn\u0103 c\u0103 nu \u0219i-au dat acordul \u00een niciunul dintre cazuri, litera <code>r<\/code> \u00eenseamn\u0103 c\u0103 ini\u021bial nu \u0219i-au dat acordul, \u00eens\u0103 dup\u0103 <em>update<\/em> au fost de acord, <code>n<\/code> \u00eenseamn\u0103 c\u0103 ini\u021bial nu avea un default, dar dup\u0103 <em>update <\/em>\u0219i-au dat acordul sau litera <code>v<\/code> \u00eenseamn\u0103 c\u0103 \u0219i-au dat acordul \u0219i <em>default<\/em>, dar \u0219i dup\u0103 <em>update<\/em>. Sunt doar c\u00e2teva dintre variantele posibile, pentru a avea o idee despre variabila de la <code>&amp;gcd<\/code>. <\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"507\" height=\"236\" src=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/litere-gcd.png\" alt=\"\" class=\"wp-image-3730\" srcset=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/litere-gcd.png 507w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/litere-gcd-300x140.png 300w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/litere-gcd-150x70.png 150w\" sizes=\"auto, (max-width: 507px) 100vw, 507px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>O alt\u0103 modalitate de a verifica implementarea de Consent Mode<\/strong> este folosind <a href=\"https:\/\/tagassistant.google.com\/\" target=\"_blank\" rel=\"noreferrer noopener\">Goo<\/a><a href=\"https:\/\/tagassistant.google.com\/\">gle Tag Assistant<\/a>, unde putem alege evenimentul dorit, iar de acolo intr\u0103m \u00een tab-ul numit Consent, care ne arat\u0103 cam acelea\u0219i lucruri de mai sus, dar \u00eentr-o vizualizare mai pl\u0103cut\u0103. Iat\u0103 un exemplu de la un site din eCommerce dale \u00eent\u00e2mpl\u0103tor:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"771\" height=\"394\" src=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/consent-tag-assistant.png\" alt=\"\" class=\"wp-image-3735\" style=\"width:771px;height:auto\" srcset=\"https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/consent-tag-assistant.png 771w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/consent-tag-assistant-300x153.png 300w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/consent-tag-assistant-150x77.png 150w, https:\/\/webanalyst.ro\/blog\/wp-content\/uploads\/2024\/02\/consent-tag-assistant-768x392.png 768w\" sizes=\"auto, (max-width: 771px) 100vw, 771px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Ce facem dup\u0103 Consent Mode<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A\u0219a cum am ar\u0103tat mai sus, implementarea Consent Mode prin Google Tag \u0219i Google Tag Manager este simpl\u0103. Mai dificil este ca fiecare organiza\u021bie s\u0103 ia intern decizia dac\u0103 dore\u0219te sau nu s\u0103 implementeze acest lucru, mai ales c\u0103 au nevoie \u0219i de un instrument de Consent Management, pentru care trebuie s\u0103 pl\u0103teasc\u0103 o tax\u0103 lunar\u0103 (asta dac\u0103 nu \u00ee\u0219i programeaz\u0103 singuri unul).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 totu\u0219i rezolva\u021bi cu Consent Mode, nu mai trebuie dec\u00e2t s\u0103 v\u0103 g\u00e2ndi\u021bi la celelalte lucruri care pot opri datele utilizatorilor s\u0103 ajung\u0103 \u00een conturile voastre de analytics sau ads. De exemplu, \u00eencep\u00e2nd de s\u0103pt\u0103m\u00e2na aceasta, semnalele Google Signals nu mai sunt raportate \u00een Google Analytics. Am scris recent aici despre limitele <a href=\"https:\/\/webanalyst.ro\/blog\/2023\/firefox-120\/\" target=\"_blank\" rel=\"noreferrer noopener\">Firefox<\/a> \u0219i <a href=\"https:\/\/webanalyst.ro\/blog\/2023\/tracking-ios-17\/\" target=\"_blank\" rel=\"noreferrer noopener\">iOS<\/a> pentru raportare, dar trebuie \u0219tiut c\u0103 toate browser-ele mari \u0219i majoritatea sistemelor de operare importante au anun\u021bat c\u0103 vor lua acelea\u0219i decizii \u00een viitorul apropiat, dac\u0103 nu le-au luat deja.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen final, \u00eenainte de a v\u0103 auca de treab\u0103, ar fi bine s\u0103 \u0219ti\u021bi diferen\u021bele dintre Google Analytics (\u0219i diferen\u021bele intre GA4 \u0219i versiunile anterioare), Google Tag Manager (care are dou\u0103 versiuni), Google Tag (tot cu dou\u0103 versiuni), Google Tag Assistant, Google Signals, \u0219i asta ca s\u0103 m\u0103 opresc la intrumentele de la Google.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google \u0219i-a anun\u021bat clien\u021bii c\u0103, \u00eencep\u00e2nd cu martie 2024, trebuie s\u0103 implementeze \u00een site-uri \u0219i aplica\u021bii modulul de consim\u021b\u0103m\u00e2nt sau Consent Mode, \u00een englez\u0103. Reglement\u0103rile europene (despre care voi detalia mai jos) le interzic companiilor de tehnologie s\u0103 proceseze date despre utilizatori f\u0103r\u0103 acordul acestora. Ca un exemplu, Meta (compania care de\u021bine Facebook, Instagram \u0219i [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3740,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[730],"tags":[994],"class_list":["post-3722","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-google-tag-manager-2","tag-consent-mode"],"_links":{"self":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3722","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/comments?post=3722"}],"version-history":[{"count":15,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3722\/revisions"}],"predecessor-version":[{"id":4352,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/3722\/revisions\/4352"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media\/3740"}],"wp:attachment":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media?parent=3722"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/categories?post=3722"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/tags?post=3722"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}