{"id":4315,"date":"2026-05-16T12:00:59","date_gmt":"2026-05-16T09:00:59","guid":{"rendered":"https:\/\/webanalyst.ro\/?p=4315"},"modified":"2026-05-16T12:04:18","modified_gmt":"2026-05-16T09:04:18","slug":"google-ads-retentie-date","status":"publish","type":"post","link":"https:\/\/webanalyst.ro\/blog\/2026\/google-ads-retentie-date\/","title":{"rendered":"Google Ads \u0219terge datele istorice"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Mai sunt doar c\u00e2teva zile p\u00e2n\u0103 la <strong>1 iunie 2026<\/strong>, ziua \u00een care Google va introduce o limit\u0103 strict\u0103 la modul \u00een care platforma gestioneaz\u0103 istoricul campaniilor publicitare.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Mai exact, Google Ads nu va mai func\u021biona ca o arhiv\u0103 permanent\u0103 pentru datele detaliate. Cei care vor s\u0103 p\u0103streze \u0219i datele mai vechi, mai au la dispozi\u021bie aproximativ dou\u0103 s\u0103pt\u0103m\u00e2ni.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen continuare, voi detalia anun\u021burile de la Google \u0219i vom observa c\u0103 \u201edatele detaliate\u201d se refer\u0103 la multe informa\u021bii cu care suntem obi\u0219nui\u021bi s\u0103 le g\u0103sim \u00een contul de Ads.<\/p>\n\n\n\n<!--more-->\n\n\n\n<h2 class=\"wp-block-heading\">Noua politic\u0103 de reten\u021bie a datelor<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google introduce o limit\u0103 strict\u0103 de stocare, f\u0103c\u00e2nd o diferen\u021b\u0103 clar\u0103 \u00eentre datele <strong>granulare (detaliate)<\/strong> \u0219i cele <strong>agregate (generale)<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Datele granulare (orare, zilnice \u0219i s\u0103pt\u0103m\u00e2nale)<\/strong> &#8211; vor fi p\u0103strate \u0219i accesibile doar pentru <strong>37 de luni<\/strong> (un pic peste 3 ani); tot ce este mai vechi de at\u00e2t va fi \u0219ters definitiv din interfa\u021b\u0103 \u0219i API<\/li>\n\n\n\n<li><strong>Datele de Reach &amp; Frequency<\/strong> &#8211; indicatorii care m\u0103soar\u0103 impactul \u0219i frecven\u021ba (precum utilizatorii unici sau distribu\u021bia frecven\u021bei) vor avea o fereastr\u0103 \u0219i mai scurt\u0103, de fix <strong>3 ani<\/strong> (36 de luni)<\/li>\n\n\n\n<li><strong>Datele agregate (lunare, trimestriale \u0219i anuale)<\/strong> &#8211; din p\u0103cate, doar aceste date r\u0103m\u00e2n oarecum \u00een siguran\u021b\u0103, pentru c\u0103 Google le va p\u0103stra timp de <strong>11 ani<\/strong>, deci vom putea analiza \u00een continuare tendin\u021bele macro (de la lun\u0103 la lun\u0103 sau de la an la an) pentru ultimul deceniu;<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Cum sunt afecta\u021bi advertiserii<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Exist\u0103 3 zone principle prin care pot fi citite datele din Google Ads. Iat\u0103 cum vor fi afectate din luna iunie:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>\u00cen interfa\u021ba Google Ads<\/strong> &#8211; dac\u0103 vom dori s\u0103 compar\u0103m performan\u021ba unei zile specifice din 2022 cu o zi din prezent, platforma nu va mai permite acest lucru. <strong>Op\u021biunea de filtrare pe zile \u0219i chiar pe s\u0103pt\u0103m\u00e2ni va fi blocat\u0103 pentru perioade mai vechi de 37 de luni!<\/strong><\/li>\n\n\n\n<li><strong>\u00cen Scripturi \u0219i API-uri (rapoarte automate)<\/strong> &#8211; dac\u0103 folose\u0219ti dashboard-uri automate (ex. Looker Studio) sau scripturi personalizate care cer segmente zilnice (<code>segments.date<\/code> sau <code>segments.week<\/code>) pentru perioade mai vechi de 37 de luni, acestea nu vor mai func\u021biona \u0219i vor returna o eroare de tipul <code>DateRangeError.INVALID_DATE<\/code><\/li>\n\n\n\n<li><strong>\u00cen BigQuery<\/strong> &#8211; serviciul de transfer de date (<em>BigQuery Data Transfer Service<\/em>) pentru Google Ads, Search Ads 360 \u0219i GA4 nu va mai putea efectua procese de <em>backfill<\/em> (repopulare de date istorice) pentru perioade care dep\u0103\u0219esc cele 37 de luni<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Totu\u021bi, pentru cei care folosesc Google BigQuery, datele pe care le-ai transferat \u0219i stocat deja \u00een acest serviciu vor r\u0103m\u00e2ne intacte! \u00cen continuare, vom vedea \u0219i alte lucruri care ar trebui f\u0103cute \u00eenainte de 1 iunie 2026 pentru a p\u0103stra datele.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce trebuie s\u0103 faci p\u00e2n\u0103 la sf\u00e2r\u0219itul lunii<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Avem, a\u0219adar, un timp scurt \u00een care s\u0103 ne putem salva datele. S\u0103 nu uit\u0103m c\u0103 30 \u0219i 31 mai sunt zile de weekend, deci am putea spune c\u0103 mai avem maxim 2 s\u0103pt\u0103m\u00e2ni s\u0103 export\u0103m date. Dup\u0103 aceea, <strong>informa\u021biile nu vor mai fi disponibile<\/strong>!<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">La fel ca \u0219i la punctul anterior, putem folosi cele 3 surse de date pentru a salva datele istorice:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Export\u0103 datele istorice esen\u021biale<\/strong> &#8211; dac\u0103 e nevoie de rapoarte zilnice sau orare de acum c\u00e2\u021biva ani pentru analize complexe de sezonalitate, audituri sau raport\u0103ri interne, acestea pot fi manual din interfa\u021ba Google Ads \u00een format Excel\/CSV sau \u00eentr-o baz\u0103 de date extern\u0103<\/li>\n\n\n\n<li><strong>Actualizeaz\u0103 scripturile \u0219i integr\u0103rile API<\/strong> &#8211; verific\u0103 instrumentele automate pe care le folose\u0219ti! Modific\u0103 interog\u0103rile pentru perioadele mai vechi de 37 de luni, astfel \u00eenc\u00e2t s\u0103 solicite segmente lunare (<code>segments.month<\/code>), trimestriale sau anuale, \u00een loc de cele zilnice<\/li>\n\n\n\n<li><strong>Porne\u0219te backfill-urile \u00een BigQuery acum<\/strong> &#8211; dac\u0103 ai omis s\u0103 tragi anumite date istorice \u00een serverul t\u0103u din BigQuery, ini\u021biaz\u0103 aceste procese imediat, pentru a te asigura c\u0103 se finalizeaz\u0103 \u00eenainte de termenul limit\u0103 de 1 iunie<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Din p\u0103cate, Google a anun\u021bat t\u00e2rziu c\u0103 va \u0219terge aceste date. Sunt mul\u021bi advertiseri care nu sunt interesa\u021bi de datele mai vechi de 3 ani, deci nu vor fi afecta\u021bi. To\u021bi ceilal\u021bi ar trebui s\u0103 ac\u021bioneze de urgen\u021b\u0103!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Mai sunt doar c\u00e2teva zile p\u00e2n\u0103 la 1 iunie 2026, ziua \u00een care Google va introduce o limit\u0103 strict\u0103 la modul \u00een care platforma gestioneaz\u0103 istoricul campaniilor publicitare. Mai exact, Google Ads nu va mai func\u021biona ca o arhiv\u0103 permanent\u0103 pentru datele detaliate. Cei care vor s\u0103 p\u0103streze \u0219i datele mai vechi, mai au la [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4316,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13,4,8],"tags":[856],"class_list":["post-4315","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-display","category-marketing-and-advertising","category-search-engine-marketing","tag-google-ads"],"_links":{"self":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/4315","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=4315"}],"version-history":[{"count":4,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/4315\/revisions"}],"predecessor-version":[{"id":4320,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/4315\/revisions\/4320"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media\/4316"}],"wp:attachment":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media?parent=4315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/categories?post=4315"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/tags?post=4315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}