<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Eceminngg on Medium]]></title>
        <description><![CDATA[Stories by Eceminngg on Medium]]></description>
        <link>https://medium.com/@eceminngg?source=rss-411563e5fed0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Bz6kBrKK0L3qfaxV</url>
            <title>Stories by Eceminngg on Medium</title>
            <link>https://medium.com/@eceminngg?source=rss-411563e5fed0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:17:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eceminngg/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[GA4 Data Manager: Setup Guide & Duplicate Conversion Risks]]></title>
            <link>https://medium.com/@eceminngg/ga4-data-manager-setup-guide-duplicate-conversion-risks-2b96cd5520a2?source=rss-411563e5fed0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b96cd5520a2</guid>
            <category><![CDATA[google-analytics]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Eceminngg]]></dc:creator>
            <pubDate>Sun, 08 Nov 2026 21:08:24 GMT</pubDate>
            <atom:updated>2026-11-08T21:08:24.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bnTTHRqNJSNUE2Par6_nWA.png" /></figure><p>Google launched GA4 Data Manager (beta) on November 6, 2026. It brings data streams, product links, imports, and connection diagnostics into one place in Google Analytics 4. The headline feature may be easier access to Meta and TikTok ad costs, but the bigger story is managing the paths that carry your first-party data.</p><p>There is one important catch: activating the same data pipeline in GA4 and Google Ads can cause duplicate conversions. Here’s what Data Manager does, how to set it up, and how to audit your connections before switching anything on.</p><h3>What is GA4 Data Manager?</h3><p>GA4 Data Manager is a centralized management hub inside the Google Analytics Admin area. Instead of checking separate screens to understand your tracking setup, you can review:</p><ul><li>A data connection map showing sources, the GA4 property, and downstream destinations.</li><li>Connection health and alerts for broken or misconfigured connections.</li><li>Diagnostics and suggested fixes.</li><li>Existing data streams, product links, and data imports from a single interface.</li></ul><p>Existing GA4 imports appear automatically in Data Manager. The feature is currently in beta, and subproperties and roll-up properties do not support its landing page yet.</p><p>Google’s <a href="https://support.google.com/analytics/answer/9164320?hl=en">November 6 announcement</a> and <a href="https://support.google.com/analytics/answer/18107176?hl=en">Data Manager documentation</a> explain the rollout.</p><h3>GA4 Data Manager features at a glance</h3><p>CapabilityWhat it doesWhat to checkConnection mapShows incoming data sources and linked destinationsWhether each data source has only the intended routeConnection diagnosticsFlags broken connections and setup problemsAuthentication, permissions, and mapping errorsThird-party campaign cost importBrings ad cost, clicks, and impressions into GA4Matching UTMs, account scope, and historical overlapData source integrationsConnects supported files, cloud stores, and platformsRefresh schedules, permissions, and consent handlingLinked product managementGives visibility into connected Google productsDuplicate pathways into Google Ads or GMP</p><h3>Import Meta, TikTok, and other paid media costs</h3><p>GA4 supports importing campaign cost data from non-Google advertising platforms, including Meta, TikTok, Snap, Pinterest, and Reddit, through supported integration flows.</p><p>These imports supply metrics such as ad spend, clicks, and impressions. GA4 can combine those numbers with the revenue and key events it measures to support cross-channel reporting and ROAS analysis.</p><p>Important distinction: importing Meta campaign costs does not import Meta’s self-reported conversions as GA4 conversions. The conversion side of a GA4 report still depends on GA4’s own measurement and attribution.</p><p>Read Google’s <a href="https://support.google.com/analytics/answer/10071305?hl=en">campaign data import documentation</a>.</p><h3>Connect additional data sources</h3><p>Depending on the data type and connector availability, Data Manager can work with sources such as Google Sheets, CSV files, BigQuery, Amazon S3, Snowflake, databases, CRM data, and offline datasets. The connection map also covers web and app streams and connected Google products.</p><p>Connector availability and supported data types vary: not every connector can import every kind of data.</p><h3>The biggest risk: duplicate conversions between GA4 and Google Ads</h3><p>Google explicitly warns against activating identical pipelines in both interfaces:</p><blockquote><em>Don’t activate an identical data pipeline in both interfaces together, as this can log conversions twice.</em></blockquote><p>The reason is the direction of the data flow. Data ingested through GA4 Data Manager can flow downstream into linked Google Ads and Google Marketing Platform accounts. The reverse path is not provided by this arrangement.</p><h3>Example: the same CRM sale enters Google Ads twice</h3><ol><li>Your CRM already sends offline sales directly to Google Ads.</li><li>You connect that same CRM data to GA4 Data Manager.</li><li>The GA4 path makes the data available downstream to linked Google Ads.</li><li>The same sale now has two possible ingestion routes into Ads.</li></ol><p>This creates a duplication risk; it does not mean every configuration will always double-count. The result depends on the connection type, conversion setup, and deduplication behavior. Google’s overview does not document every deduplication rule for every connector, so do not rely on an assumed automatic fix.</p><p>Safer approach: keep one authoritative ingestion path per conversion dataset and destination. Audit existing Ads or GMP integrations before recreating anything in GA4.</p><h3>A different duplication risk: overlapping campaign costs</h3><p>Conversion duplication is not the only problem.</p><p>Suppose you already import Meta ad costs using a CSV upload or a third-party connector. If you then enable the native Meta connection for the same ad account and overlapping date range, you risk inconsistent or duplicated imported cost records.</p><p>Google recommends deleting overlapping previous Meta import datasets before enabling the new integration. The Meta connector attempts to retrieve at least 24 months of historical data, so checking just the current week is not enough.</p><p>See the <a href="https://support.google.com/analytics/answer/16536051?hl=en">official Meta connection guide</a>.</p><h3>Duplicate conversions vs duplicate cost data</h3><p>RiskTypical causeWhere to lookPreventionDuplicate conversionsSame CRM/offline events connected through GA4 and AdsGoogle Ads conversions and data connection mapUse one intended pipeline per event dataset and destinationOverlapping ad costsNative Meta import added over an old CSV/connector importGA4 campaign cost datasets and date rangesRemove overlapping datasets before switchingMissing or mismatched costsDifferent utm_source or utm_medium valuesCampaign tagging and import mappingsStandardize exact UTM valuesMisleading ROASCost data and measured conversions use inconsistent attribution or campaign keysGA4 advertising reportsValidate campaign matching and attribution definitions</p><h3>Four steps to prevent double counting</h3><h3>1. Build a data pipeline inventory</h3><p>List each existing GA4, Google Ads, and Google Marketing Platform connection. Record the source, destination, dataset, event type, owner, refresh schedule, and whether another path carries the same records.</p><h3>2. Leave existing Ads integrations where they are</h3><p>Google recommends continuing to manage existing connections in Google Ads or GMP instead of duplicating them inside GA4. Do not recreate an active pipeline just because a new screen offers a convenient connector.</p><h3>3. Create new connections through GA4 Data Manager</h3><p>For new connections, Google recommends initiating the setup in GA4 Data Manager, while checking the downstream product links before activation. Make sure an equivalent parallel route is not already active.</p><h3>4. Audit historical cost imports</h3><p>Before enabling native Meta or another ad platform integration, compare advertising account IDs, campaign identifiers, UTM mappings, and imported date ranges. Remove overlapping old datasets where Google’s connector guidance calls for it.</p><h3>How to set up GA4 Data Manager</h3><p>The main route is:</p><p>GA4 → Admin → Data Manager → Connect product → Select source → Choose use case → Begin setup</p><p>The labels shown may vary slightly by connector and rollout. You’ll need the appropriate GA4 property permissions.</p><p>For a Meta campaign cost import:</p><ol><li>Confirm you have at least the Editor role on the GA4 property.</li><li>Open Data Manager, or the Meta Links integration under Admin’s product links where that flow is exposed.</li><li>Authorize your Meta business and advertising account, then select the relevant ad account.</li><li>Verify that ad landing-page URLs use consistent utm_source and utm_medium values.</li><li>Prefer adding utm_campaign and utm_id for more reliable campaign matching.</li><li>Check existing historical imports for overlapping dates before starting the connection.</li><li>Monitor the connection status and validate the imported campaign metrics.</li></ol><p>Example URL tagging:</p><p>?utm_source=facebook&amp;utm_medium=paid_social&amp;utm_campaign=autumn_launch&amp;utm_id=12345</p><p>The values must align with the source/medium mapping used by the connector. The example is illustrative, not a universal required naming convention.</p><p>Google’s <a href="https://support.google.com/analytics/answer/16536051?hl=en">Meta setup instructions</a> are the final reference for the flow available to your property.</p><h3>Limits and implementation details to know</h3><ul><li>Refresh cadence: supported automatic campaign imports generally update daily; verify the connector-specific schedule.</li><li>Historical import: the native Meta integration attempts to retrieve at least 24 months of historical records.</li><li>Reporting delay: imported campaign metrics may take time to appear in GA4 reports, sometimes up to a day after processing.</li><li>UTM matching: inconsistent utm_source and utm_medium values can prevent correct campaign matching.</li><li>Property support: GA4 subproperties and roll-up properties currently do not support the Data Manager landing page.</li><li>Permissions and privacy: linking a platform doesn’t remove consent, data handling, or access-control obligations.</li></ul><h3>GA4 Data Manager vs Data Manager API</h3><p>The similar names describe different tools.</p><p>GA4 Data ManagerGoogle Data Manager APIAdmin interface inside Google Analytics 4Developer API for programmatic data ingestionVisualizes and manages connections, imports, streams, and diagnosticsSends supported first-party audience and event data to Google destinationsUsed by analysts and platform administratorsUsed by engineers and integration teamsIncludes a connection mapIncludes request-level ingestion and diagnostic responses</p><p>The API has its own release cycle. On November 4, 2026, Data Manager API v1.9 added support for Google Ads call conversions and record-level indices for processing errors and warnings. The API also exposes consent-related fields such as adUserData and adPersonalization; a connector does not replace a proper consent implementation.</p><p>See the <a href="https://developers.google.com/data-manager/api/reference">Data Manager API release notes</a>.</p><h3>Final takeaway: centralization is not measurement quality</h3><p>GA4 Data Manager makes it easier to see where your data comes from and where it goes. That is useful, especially for teams managing Meta, TikTok, CRM, offline, and Google Ads integrations at the same time.</p><p>But one centralized screen cannot answer every measurement question for you: Are events generated correctly? Is consent propagated through each route? Is a purchase sent twice? Can you trust the source and campaign keys?</p><p>Before enabling a new connector, draw one map: which data travels from which source to which destination, through which pipeline? A dependable first-party and server-side tracking architecture still starts there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b96cd5520a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GA4 Data Manager: Tüm Veri Bağlantıları Tek Ekranda, Ama Çift Sayıma Dikkat]]></title>
            <link>https://medium.com/@eceminngg/ga4-data-manager-t%C3%BCm-veri-ba%C4%9Flant%C4%B1lar%C4%B1-tek-ekranda-ama-%C3%A7ift-say%C4%B1ma-dikkat-8522d4f2e261?source=rss-411563e5fed0------2</link>
            <guid isPermaLink="false">https://medium.com/p/8522d4f2e261</guid>
            <category><![CDATA[ga4]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[google-analytics]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Eceminngg]]></dc:creator>
            <pubDate>Sun, 08 Nov 2026 21:06:17 GMT</pubDate>
            <atom:updated>2026-11-08T21:06:17.150Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bnTTHRqNJSNUE2Par6_nWA.png" /></figure><p>Google, 6 Kasım 2026&#39;da Google Analytics 4&#39;e yeni bir özellik ekledi: <strong>Data Manager</strong> (beta). İlk bakışta “Meta ve TikTok maliyetlerini GA4&#39;e alan bir araç” gibi görünüyor. Aslında daha kapsamlı GA4&#39;teki veri akışlarını, ürün bağlantılarını ve import’ları tek ekranda yöneten bir kontrol merkezi.</p><p>Bu yazıda Data Manager’ın ne getirdiğine, nasıl kurulduğuna ve Google’ın açıkça uyardığı çift sayım riskine bakıyoruz.</p><h3>Data Manager nedir?</h3><p>Data Manager, GA4&#39;ün yönetici ayarlarında bulunuyor ve veri bağlantılarını tek bir yerde topluyor. Burada şunları görebiliyorsunuz:</p><ul><li>Hangi kaynaktan hangi verinin geldiğini gösteren bir <strong>bağlantı haritası</strong></li><li>Her bağlantının <strong>sağlık durumu</strong></li><li><strong>Hata teşhisleri</strong></li></ul><p>Daha önce farklı ekranlara dağılmış olan importlar, ürün bağlantıları ve veri akışları artık tek yerden yönetiliyor. Mevcut GA4 importlarınız da kendiliğinden bu ekranda görünüyor.</p><h3>Neler getiriyor?</h3><h3>Reklam platformlarının maliyet verisi</h3><p>En çok konuşulan özellik bu. Meta, TikTok, Snap, Pinterest ve Reddit’ten günlük <strong>harcama, tıklama ve gösterim</strong> verilerini GA4&#39;e alabiliyorsunuz. GA4 bu verileri kendi ölçtüğü gelir ve key event verileriyle birleştiriyor. Böylece kanalları ve ROAS’ı tek raporda karşılaştırabiliyorsunuz.</p><p>Bir noktayı netleştirelim: Bu import platformların <strong>kendi raporladığı dönüşümleri</strong> getirmiyor. Gelen veri sadece maliyet, tıklama ve gösterim. Dönüşümleri yine GA4 kendisi ölçüyor.</p><h3>Diğer veri kaynakları</h3><p>Google Sheets, CSV, BigQuery, Amazon S3, Snowflake ve çeşitli veritabanları üzerinden de veri alınabiliyor. Bağlantı haritası CRM verilerini, offline dosyaları, web ve uygulama akışlarını ve bağlı Google ürünlerini de kapsıyor.</p><h3>Çift sayım riski: Google ne diyor?</h3><p>Data Manager’ın en kritik noktası bu. Google’ın uyarısı oldukça açık:</p><blockquote><em>“Don’t activate an identical data pipeline in both interfaces together, as this can log conversions twice.”</em></blockquote><p>Yani aynı veri akışını hem GA4&#39;te hem Google Ads’te kurmamanız gerekiyor, yoksa dönüşümler iki kez sayılabilir.</p><h3>Bu nasıl oluyor?</h3><p>GA4 Data Manager’a gelen veri, bağlı Google Ads ve Google Marketing Platform hesaplarına da aktarılabiliyor. Ters yönde böyle bir aktarım yok.</p><p>Örnek bir senaryo:</p><ol><li>CRM’deki satışlarınızı zaten doğrudan Google Ads’e gönderiyorsunuz.</li><li>Aynı CRM verisini GA4 Data Manager’a da bağlıyorsunuz.</li><li>GA4 bu veriyi bağlı Ads hesabına aktarıyor.</li><li>Sonuçta aynı satış Ads’e iki farklı yoldan ulaşıyor.</li></ol><p>Google’ın dokümanı her bağlantı türünde mükerrer kayıtların nasıl ayıklandığını ayrıntılı anlatmıyor. Bu yüzden en güvenli yol, aynı veriyi iki ayrı yoldan hiç göndermemek.</p><h3>Maliyet tarafındaki ayrı risk</h3><p>Dönüşümlerden bağımsız ikinci bir risk de var: Meta maliyetlerini zaten CSV ya da üçüncü parti bir connector ile GA4&#39;e alıyorsanız, üzerine doğrudan Meta bağlantısı eklemek aynı tarihlerin maliyetini iki kez yazabilir. Google, yeni bağlantıyı kurmadan önce tarihleri çakışan eski import’ların kaldırılmasını öneriyor.</p><h3>Çift sayımı önlemek için 4 adım</h3><ol><li><strong>Envanter çıkarın.</strong> Mevcut GA4 ve Google Ads bağlantılarınızı listeleyin: Hangi veri, hangi kaynaktan, hangi hedefe gidiyor?</li><li><strong>Ads bağlantılarını Ads’te bırakın.</strong> Google Ads’te zaten kurulu olan bağlantıların aynısını GA4&#39;te tekrar kurmayın.</li><li><strong>Yeni bağlantıları tek yerden başlatın.</strong> Yeni akışları GA4 Data Manager üzerinden kurun ve paralel bir hat açmayın.</li><li><strong>Maliyet import’larını kontrol edin.</strong> Yeni bir connector eklemeden önce eski import’larla tarih ve reklam hesabı çakışması olup olmadığına bakın.</li></ol><h3>Kurulum</h3><p>Kurulum oldukça basit:</p><p><strong>GA4 → Yönetici → Data Manager → “+Connect Product” → kaynağı seçin → kullanım amacını seçin → “Begin setup”</strong></p><p>Meta maliyet import’u için dikkat edilmesi gerekenler:</p><ul><li>GA4 property’sinde en az <strong>Editor</strong> yetkiniz olmalı.</li><li>Meta hesabınızı yetkilendirip reklam hesabını seçiyorsunuz.</li><li>Reklamlarınızdaki utm_source ve utm_medium değerleri <strong>birebir</strong> eşleşmeli. utm_campaign ve utm_id kullanmanız da öneriliyor.</li></ul><h3>Bilmeniz gereken sınırlar</h3><ul><li>Otomatik import günde bir kez çalışıyor ve yaklaşık 24 aylık geçmiş veriyi çekmeye çalışıyor.</li><li>Verilerin raporlara yansıması 24 saati bulabiliyor.</li><li>UTM değerleri tutarsızsa eşleşme bozuluyor. Bir platform için birden fazla source/medium kullanıyorsanız alternatif bir import yöntemi gerekebilir.</li><li>Subproperty ve roll-up property’ler şimdilik Data Manager’ı desteklemiyor.</li></ul><h3>Data Manager ile Data Manager API arasındaki fark</h3><p>İsimleri benzediği için karıştırılabiliyor:</p><ul><li><strong>GA4 Data Manager</strong>, GA4 içindeki bir yönetim ekranı.</li><li><strong>Data Manager API</strong>, first-party audience ve event verilerini Google ürünlerine kodla göndermek için kullanılan ayrı bir katman.</li></ul><p>API tarafında da yenilikler var. 4 Kasım’da çıkan v1.9 ile Google Ads call conversion desteği ve hatalı kayıtları satır bazında gösteren diagnostics geldi (<a href="https://developers.google.com/data-manager/api/reference">sürüm notları</a>). API’de consent için adUserData ve adPersonalization alanları bulunuyor. Bir connector kullanmak, consent yönetimini ortadan kaldırmıyor.</p><h3>Merkezileşme ölçüm altyapısının yerini tutmuyor</h3><p>Google veri bağlantılarını ve aktivasyonu giderek daha merkezi hale getiriyor. Bu, birçok ekip için yönetimi kolaylaştıracak. Ama merkezi bir ekran, ölçümün temel sorunlarını kendiliğinden çözmüyor:</p><ul><li>Event’ler doğru üretiliyor mu?</li><li>Consent bilgisi tüm hatlara doğru taşınıyor mu?</li><li>Aynı dönüşüm farklı yollardan tekrar gönderiliyor mu?</li><li>Veri kalitesi güvenilir mi?</li></ul><p>Data Manager’ı kullanmaya başlamadan önce atılacak en değerli adım, <strong>“hangi veri hangi yoldan hangi hedefe gidiyor?”</strong> haritasını çıkarmak. Sağlam bir first-party ve server-side ölçüm altyapısı, bu haritanın temeli olmaya devam ediyor.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8522d4f2e261" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Ads API v26: Enhanced Conversions Changes Explained]]></title>
            <link>https://medium.com/@eceminngg/google-ads-api-v26-enhanced-conversions-changes-explained-66689ce070ff?source=rss-411563e5fed0------2</link>
            <guid isPermaLink="false">https://medium.com/p/66689ce070ff</guid>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Eceminngg]]></dc:creator>
            <pubDate>Wed, 21 Oct 2026 07:01:34 GMT</pubDate>
            <atom:updated>2026-10-21T07:01:34.334Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WyiGWgYEg9yWJ6tdjNpB4Q.png" /></figure><p>Google Ads API v26 changes how teams inspect account-level Enhanced Conversions settings. Released on October 14, 2026, it replaces the old Enhanced Conversions for Leads enablement field with a unified configuration that distinguishes an account’s own setting from the setting that actually applies.</p><p>If you maintain a Google Ads API integration, this is a migration item. If you manage a standard Google Tag Manager implementation, the field change alone is not a reason to rebuild your tags.</p><p>The practical question is whether your monitoring can tell the difference between a feature being enabled and measurement working correctly.</p><h3>What changed in Google Ads API v26?</h3><p>Google’s <a href="https://developers.google.com/google-ads/api/docs/release-notes#v26">v26 release notes</a> confirm the removal of customer.conversion_tracking_setting.enhanced_conversions_for_leads_enabled. Two enum fields now expose the unified account-level Enhanced Conversions configuration:</p><p>API fieldPurpose in a v26 auditcustomer.conversion_tracking_setting.enablement_settingInspect the account&#39;s own Enhanced Conversions configuration.customer.conversion_tracking_setting.effective_enablement_settingInspect the setting that applies, including inheritance from a manager when cross-account conversion tracking is used.</p><p>The new fields use the <a href="https://developers.google.com/google-ads/api/reference/rpc/v26/EnhancedConversionsConfigEnum.EnhancedConversionsConfig">EnhancedConversionsConfig enum</a>, which includes ON, OFF, UNKNOWN, and UNSPECIFIED.</p><p>Update any integration that expects a simple boolean. In your own reporting logic, preserve unknown or unspecified values as separate states rather than silently treating them as OFF. Otherwise, a monitoring dashboard can create a misleading failure alert.</p><p>This release changes the configuration surface exposed by the API. It does not establish that conversion matching, reported revenue, or return on ad spend will automatically improve after migration.</p><h3>What are Enhanced Conversions?</h3><p><a href="https://support.google.com/google-ads/answer/9888656?hl=en">Enhanced Conversions</a> supplements conversion measurement with first-party information that a customer provides, such as an email address or phone number. That information can help Google associate eligible conversions with ad interactions when other measurement signals are incomplete.</p><p>For example, imagine an online store records 100 purchases in its order system. Google Ads may attribute only some of those purchases to advertising. Where the required conditions are met, Enhanced Conversions can help match additional purchases that already happened. It does not create additional orders.</p><p>At a high level, the process looks like this:</p><ol><li><em>A customer interacts with an ad and later converts.</em></li><li><em>During the conversion journey, the customer provides information such as an email address.</em></li><li><em>The implementation processes eligible user-provided data according to the collection method, applicable consent, and Google’s requirements.</em></li><li><em>Normalized identifiers are hashed with SHA-256 before being sent to Google; depending on the implementation, the tag or the integration handles hashing.</em></li><li><em>Google uses the eligible data to support matching and attribution.</em></li></ol><p>The v26 account fields describe configuration. They do not confirm that these steps have completed successfully for any particular conversion.</p><h3>Enhanced Conversions for Web vs. Enhanced Conversions for Leads</h3><p>ImplementationTypical use caseData flow to validateEnhanced Conversions for WebAn online purchase, registration, or form submissionThe website conversion and its eligible user-provided dataEnhanced Conversions for LeadsA website inquiry that becomes a qualified lead or sale laterWebsite lead data and subsequent offline conversion imports, often from a CRM</p><p>The account configuration is becoming more unified, but these journeys still need different implementation checks. A purchase tag audit does not tell you whether a CRM import contains the correct lead outcome.</p><h3>Why the effective setting matters for MCC accounts</h3><p>A Google Ads manager account, often called an MCC, can manage conversion tracking across client accounts. That makes the account you are inspecting different from the account that controls its conversion tracking configuration.</p><p>Google’s <a href="https://developers.google.com/google-ads/api/fields/v26/customer#customer.conversion_tracking_setting.effective_enablement_setting">v26 customer field reference</a> documents that the effective Enhanced Conversions setting is inherited from the manager when cross-account conversion tracking is used.</p><p>Consider an agency managing two brands. One brand owns its conversion tracking; the other uses conversion tracking managed through an MCC. Reading only each client’s local setting would leave out an important part of the second brand’s configuration.</p><p>For an account audit, I would record both new values alongside the conversion tracking owner. If they differ, investigate the account relationship before labeling the implementation as broken. The effective value is especially useful for understanding what applies to a client account today.</p><h3>Who needs to take action?</h3><h4>Teams using the Google Ads API</h4><p>Review custom scripts, account health dashboards, scheduled audits, and integrations that read Enhanced Conversions settings. A query that selects the removed field must be updated when that integration moves to v26.</p><p>Also inspect downstream code. Replacing a field name is not enough if the database, alert rules, or interface still expects true or false.</p><h4>Agencies and teams managing multiple accounts</h4><p>Include local and effective configuration in your audit output. Keep the conversion tracking owner visible so that the person investigating an issue knows where to review the controlling setting.</p><h4>Teams using standard GTM tags</h4><p>The documented API field replacement does not, by itself, require a new GTM Enhanced Conversions setup. Continue validating your existing tags and diagnostics, and check whether any separate monitoring tool depends on the API field that was removed.</p><p>If you are also reviewing container changes, my <a href="https://ecem.fyi/blog/google-tag-manager-october-2026-update">GTM October 2026 update guide</a> covers that separate workflow.</p><h3>Enhanced Conversions migration checklist</h3><p>I would split validation into two passes: configuration first, then the actual conversion data flow.</p><h4>1. Find dependencies on the removed field</h4><p>Search your API queries, reporting jobs, and integration configuration for enhanced_conversions_for_leads_enabled. Identify which API version each integration uses before changing it.</p><h4>2. Read both new account settings</h4><p>Replace the old field in v26 queries with the appropriate new fields. Confirm that your client library and response mapping support the version you are calling. Store the returned enum states without collapsing them into a boolean.</p><h4>3. Check the conversion tracking owner</h4><p>For cross-account conversion tracking, review the manager configuration and the client’s effective setting together. Compare the result with the intended account setup rather than assuming all clients manage conversions locally.</p><h4>4. Validate user-provided data and consent handling</h4><p>Check that eligible identifiers are available at the correct point in the conversion journey. Review normalization, hashing responsibilities, and consent handling for your collection method. An enabled account setting cannot compensate for missing or incorrectly processed identifiers.</p><p>For related implementation context, see my notes on <a href="https://ecem.fyi/blog/server-side-gtm-first-party-data">server-side GTM and first-party data</a>.</p><h4>5. Review diagnostics and offline imports</h4><p>Inspect Enhanced Conversions diagnostics in Google Ads. For lead implementations, also review import results, CRM field mappings, conversion actions, and whether the uploaded outcome corresponds to the intended stage of the lead journey.</p><p>Treat successful configuration checks and successful data delivery as separate evidence. Even accepted data does not mean every conversion can be matched.</p><h3>Frequently asked questions</h3><h4>Did Google Ads API v26 change how Enhanced Conversions matches users?</h4><p>The documented update concerns unified account configuration and the API fields used to inspect it. These changes alone do not demonstrate a new matching method or a guaranteed increase in attributed conversions.</p><h4>Which field replaces enhanced_conversions_for_leads_enabled?</h4><p>Google directs v26 integrations to customer.conversion_tracking_setting.enablement_setting for the account-level configuration. Read customer.conversion_tracking_setting.effective_enablement_setting as well when you need to understand the applied setting and manager inheritance.</p><h4>Do I need to reinstall Enhanced Conversions in GTM?</h4><p>The API field change alone does not require rebuilding your GTM tags. Review any API-based audits separately and continue testing the conversion implementation itself.</p><h4>Does an ON setting prove Enhanced Conversions is working?</h4><p>No. It indicates enablement, not the quality of identifiers, consent handling, conversion mapping, or matching. Use diagnostics and data-flow checks to assess those separately.</p><h4>What I would prioritize after this update</h4><p>For API integrations, update the removed field and preserve the new enum states throughout the reporting pipeline. For MCC audits, make the effective setting and conversion tracking owner visible. For measurement teams, keep validating the identifiers and conversion outcomes that reach Google Ads.</p><p>Enabling a measurement feature is one step. Verifying that the right data reaches it is the work that makes the setting useful.</p><h3>Official sources</h3><ul><li><a href="https://developers.google.com/google-ads/api/docs/release-notes#v26">Google Ads API release notes: v26, October 14, 2026</a></li><li><a href="https://developers.google.com/google-ads/api/fields/v26/customer">Google Ads API v26 customer fields</a></li><li><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/EnhancedConversionsConfigEnum.EnhancedConversionsConfig">EnhancedConversionsConfig enum reference</a></li><li><a href="https://support.google.com/google-ads/answer/9888656?hl=en">Google Ads Help: About enhanced conversions</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66689ce070ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Tag Manager October 2026 Update: What Changed and How to Check Your GTM Container]]></title>
            <link>https://medium.com/@eceminngg/google-tag-manager-october-2026-update-what-changed-and-how-to-check-your-gtm-container-eb6d170988d8?source=rss-411563e5fed0------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb6d170988d8</guid>
            <category><![CDATA[google-analytics]]></category>
            <category><![CDATA[google-tag-manager]]></category>
            <category><![CDATA[google-tag-maanger-update]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Eceminngg]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 08:30:22 GMT</pubDate>
            <atom:updated>2026-10-14T08:30:22.334Z</atom:updated>
            <content:encoded><![CDATA[<h3>Google Tag Manager October 2026 Update: What Changed and How to Check Your GTM Container</h3><p><strong>Google Tag Manager (GTM) is introducing a major update to how Google tags are managed, configured, and connected to measurement platforms such as Google Analytics 4 (GA4) and Google Ads.</strong></p><p>On October 12, 2026, Google announced a new container optimization capability that allows GTM to send measurement data directly to supported Google destinations without loading the additional gtag.js library.</p><p>The update aims to improve website performance, simplify tag configuration, and centralize measurement settings within Google Tag Manager.</p><p>But what exactly has changed? How will this affect existing tracking implementations? And how can you check whether your GTM container is ready for the update?</p><h3>What Changed in Google Tag Manager?</h3><p>Previously, Google Tag Manager could load an additional JavaScript library, gtag.js, to send measurement data to Google products.</p><p>Google tags could also maintain separate settings and permissions, making configuration management and troubleshooting more complicated, especially when multiple Google destinations were involved.</p><p>With the new optimized container experience, Google is bringing these configurations together.</p><h3>1. Direct Data Transmission Without Loading gtag.js</h3><p>One of the most important changes is how measurement data is transmitted.</p><p>Previously, GTM could load gtag.js as part of the process of sending data to Google destinations.</p><p>With optimized containers, GTM can send data directly to supported Google measurement products without loading the additional library.</p><p><strong>What does this mean?</strong></p><ul><li>Less JavaScript needs to be loaded on the website.</li><li>The measurement process can become more efficient.</li><li>Additional JavaScript loading delays can be reduced.</li><li>Data collection performance may improve.</li></ul><p>However, this does not guarantee a measurable page-speed improvement for every website. The actual impact depends on the existing implementation and the scripts already running on the page.</p><h3>2. Centralized Google Tag Settings</h3><p>Another major change is the introduction of centralized settings management.</p><p>Previously, separate Google tags could have their own configurations. When multiple measurement products were connected, maintaining consistent settings could become difficult.</p><p>With the optimized setup, Google tag settings can be consolidated at the GTM container level.</p><p>A new <strong>Settings</strong> section provides access to Google-related configurations, including connected destinations and data flow information.</p><p>For example, if a website sends measurement data to both GA4 and Google Ads, the updated structure can make it easier to manage shared settings and identify connected destinations.</p><p>This can reduce configuration complexity and make tracking implementations easier to maintain.</p><h3>3. Improved Visibility and Access Management</h3><p>The update also introduces a more unified relationship between Google Tag Manager and connected Google measurement products.</p><p>Container administrators can manage destination-related access and permissions more centrally.</p><p>This is particularly useful for organizations where analytics, marketing, and development teams collaborate on the same tracking implementation.</p><p>One important detail is that <strong>destination permissions are not versioned with GTM container changes</strong>. Administrators should therefore review access settings carefully during migration.</p><h3>4. A More Unified Google Tag and GTM Experience</h3><p>Google is also working toward bringing Google Tag and Google Tag Manager closer together.</p><p>According to Google’s documentation, the broader direction includes extending GTM capabilities such as interface-based tag configuration, debugging, and version control to websites using Google Tag.</p><p>This represents a shift toward a more unified tagging ecosystem rather than separate configuration experiences across Google products.</p><h3>How Will This Update Affect Existing Tracking Implementations?</h3><p>For websites already using GTM to manage GA4, Google Ads, and other marketing platforms, the main changes involve how Google-related settings are organized and how data is transmitted.</p><p>Importantly, Google states that existing event tags and triggers are maintained during the optimization process.</p><p>This means you should not need to recreate all your existing GA4 events or Google Ads conversion tags simply because you optimize your container.</p><p>However, maintaining the configuration does not eliminate the need for validation.</p><p>After migration, analytics teams should confirm that important measurement events still work as expected.</p><p>Examples include:</p><ul><li>page_view</li><li>view_item</li><li>add_to_cart</li><li>begin_checkout</li><li>purchase</li><li>Google Ads conversion events</li></ul><p>For e-commerce websites, it is particularly important to verify purchase transaction IDs, values, currencies, and other parameters used in reporting and attribution.</p><p>The update also does not automatically convert an existing client-side GTM implementation into a server-side GTM setup. Server-side tagging remains a separate implementation approach.</p><h3>How to Check the New Update in Google Tag Manager</h3><p>Google provides an optimization workflow directly within the GTM interface.</p><p>You can check whether your container is eligible and review the proposed changes before publishing anything.</p><h3>Step 1: Open Your GTM Container</h3><p>Visit <a href="https://tagmanager.google.com/">Google Tag Manager</a> and select the container you want to inspect.</p><p>Navigate to the <strong>Overview</strong> page.</p><p>If the optimization workflow is available for your container, you may see a banner labeled:</p><p><strong>Optimize your Tag Manager container</strong></p><p>The available action depends on your current configuration:</p><ul><li><strong>Review details:</strong> Typically appears when existing Google tag settings are already consistent.</li><li><strong>Get started:</strong> May appear when multiple Google tags have conflicting configurations that need to be resolved.</li></ul><p>The absence of a banner alone does not establish whether a container has already been optimized.</p><h3>Step 2: Check the Settings Section</h3><p>Navigate to the new <strong>Settings</strong> section in GTM.</p><p>Look for <strong>Google Destinations</strong>, where you can review connected measurement destinations.</p><p>Check the <strong>Optimized</strong> column.</p><p>If a destination displays <strong>No</strong>, you can hover over the value and select <strong>Get Started</strong> when that action is available.</p><p>This is another way to access the container optimization workflow.</p><p>The section also makes it easier to understand which Google measurement destinations are connected to your container.</p><h3>Step 3: Review the Proposed Changes</h3><p>Before applying the optimization, select <strong>Preview changes</strong>.</p><p>This step is especially important for containers with multiple Google tags.</p><p>Review the configuration changes carefully and verify which settings will be consolidated.</p><p>If your tags have different configurations, Google will guide you through selecting and confirming the settings to use.</p><p>Pay particular attention to measurement settings that may affect existing analytics or advertising implementations.</p><h3>Step 4: Add the Changes to Your Workspace</h3><p>Once you have reviewed the configuration, click <strong>Add to workspace</strong>.</p><p>This adds the proposed changes to your GTM workspace.</p><p><strong>The changes are not immediately published to your live website.</strong></p><p>You can review and test the updated configuration before making it active.</p><h3>Step 5: Test the Implementation Using GTM Preview Mode</h3><p>After adding the changes to your workspace, click <strong>Preview</strong> in GTM.</p><p>This launches Google Tag Assistant.</p><p>Enter your website URL and connect to the website.</p><p>Then test important user interactions, such as:</p><ol><li>Opening a product page.</li><li>Adding a product to the cart.</li><li>Starting the checkout process.</li><li>Completing a test purchase.</li></ol><p>In Tag Assistant, verify that expected tags fire at the correct stages and that the relevant event parameters are available.</p><p>You should also check GA4 DebugView, where applicable, to confirm that events are being received as expected.</p><p>For Google Ads, validate conversion firing and relevant conversion parameters.</p><p>Pay attention to duplicate events, missing parameters, and unexpected changes in tag behavior.</p><h3>Step 6: Publish Your Container</h3><p>After verifying the updated implementation, return to Google Tag Manager.</p><p>Click <strong>Submit</strong> to publish the container changes.</p><p>Use a descriptive version name, such as:</p><p>GTM Container Optimization - October 2026</p><p>Including a description of the changes makes it easier to identify the update in GTM version history.</p><p>If a problem is identified later, a previously published container version can be restored and republished.</p><p>Keep in mind that destination access permissions require separate review because they are not included in container version history.</p><h3>How to Verify That the Update Is Working Correctly</h3><p>After publishing the optimized container, it is useful to perform a final measurement audit.</p><p>AreaWhat to checkGTM SettingsConfirm Google destinations and optimization statusTag AssistantVerify tag firing and event executionGA4 DebugViewConfirm incoming events and event parametersGoogle AdsValidate conversion trackingE-commerce trackingCheck purchase values, currencies, and transaction IDsConsent ModeVerify consent states and consent-dependent behaviorBrowser NetworkInspect measurement requests and unexpected duplicate requestsGTM VersionsConfirm the correct container version is published</p><p>For a more technical validation, open your browser’s Developer Tools and inspect the <strong>Network</strong> tab.</p><p>Compare measurement behavior before and after optimization, ideally in a controlled test environment.</p><p>You can look for changes in script loading and measurement requests.</p><p>However, the presence or absence of a particular network request should not be used as the only indication of a successful migration. Actual event delivery and reporting must also be validated.</p><h3>What Does This Mean for Digital Analytics Teams?</h3><p>From a digital analytics perspective, the biggest advantage of this update is not simply reducing JavaScript loading.</p><p>It is the move toward a more centralized and manageable measurement architecture.</p><p>For analytics and marketing teams, this can mean:</p><ul><li>Less complexity when managing multiple Google measurement destinations.</li><li>Easier troubleshooting through more consistent configurations.</li><li>Improved visibility into connections between GTM and Google products.</li><li>More streamlined collaboration between analytics and advertising teams.</li><li>Potential improvements in measurement transmission performance.</li></ul><p>At the same time, teams should review existing Google tag settings before migration, especially when different products or properties require different configuration behavior.</p><h3>Conclusion</h3><p>The October 2026 Google Tag Manager update represents an important step toward unifying Google Tag and GTM.</p><p>By introducing direct measurement transmission, centralized container settings, and improved destination management, Google is simplifying how businesses manage their tracking infrastructure.</p><p>For websites already using GTM, the next step is to check whether container optimization is available, review existing configurations, and validate critical measurement events before publishing the changes.</p><p><strong>A more optimized tagging infrastructure is valuable, but reliable measurement still depends on correct implementation, testing, and ongoing monitoring.</strong></p><p><strong>Official Google documentation:</strong></p><ul><li><a href="https://support.google.com/tagmanager/answer/16659369">Optimize your Google Tag Manager container</a></li><li><a href="https://support.google.com/tagmanager/answer/4620708">Google Tag Manager Release Notes</a></li><li><a href="https://support.google.com/tagmanager/answer/17079602">Updates to Google Tag and Google Tag Manager</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb6d170988d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft Advertising UTM Update]]></title>
            <link>https://medium.com/@eceminngg/microsoft-advertising-utm-update-83b6386031cc?source=rss-411563e5fed0------2</link>
            <guid isPermaLink="false">https://medium.com/p/83b6386031cc</guid>
            <category><![CDATA[channel-sales]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[measurement]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Eceminngg]]></dc:creator>
            <pubDate>Thu, 10 Sep 2026 19:59:08 GMT</pubDate>
            <atom:updated>2026-09-10T19:59:08.432Z</atom:updated>
            <content:encoded><![CDATA[<p>Microsoft son günlerde hepimizi harekete geçiren bir güncelleme paylaştı. Kampanya izleme konusunda kritik bir değişikliğe gittiler.</p><p>Microsoft Advertising, tüm kampanyalar için standart tek bir şablon uyguluyordu. 2 Eylül itibariyle duyurulan bu güncelleme ile beraber her kampanya artık kendi özel UTM yapısına sahip olacak. Böylece daha doğru bir sınıflandırmanın önü açılmış oldu.</p><p><strong>Bu güncellemeyle hayatımızda ne değişiyor?</strong></p><p>Bu güncelleme, özellikle Google Analytics 4 (GA4) panellerindeki Default Channel Grouping (Varsayılan Kanal Gruplaması) mekanizmasını doğrudan etkiliyor. Uzun süredir Microsoft Ads trafiği genel olarak Paid Search grubunda toplanıyordu. Yeni yapıyla birlikte her kampanya türü GA4&#39;te hak ettiği doğru kanala yerleşmeye başlıyor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tw3zsMopaeymwMHWImuUQg.png" /></figure><p>Bu değişim performans raporlarında ani dalgalanmalar görünmesine neden olabilir. Örneğin önceden Paid Search altında görünen alışveriş veya display kampanyalarınız artık doğru kanallara ayrılacağı için search kampanya performansınız düşüş gösterebilir.</p><p><strong>Peki bu durumda ne yapmalıyız?</strong></p><p>Bu geçiş sürecinde veri bütünlüğünü korumak için ;</p><ul><li>Microsoft Advertising panelinizde Auto-Tagging ayarlarının aktif olduğundan ve yeni şablonların doğru yansıdığından emin olun.</li><li>Raporlarınızdaki ani düşüş veya artışları yanlış yorumlamamak adına, trafik kaynaklarının yukarıdaki tabloya göre doğru kategorize edilip edilmediğini GA4 “Traffic Acquisition” raporundan kontrol edin.</li></ul><p>Böylece değişime ayak uydurarak doğru sınıflandırma ile veri bütünlüğünü koruyabiliriz.</p><p><strong>Microsoft Advertising UTM Auto-Tagging Update</strong></p><p>Microsoft recently rolled out an update that impacts us all, marking a critical shift in how campaigns are tracked.</p><p>Previously, Microsoft Advertising relied on a single, standardized list for all campaigns. With this update announced on September 2nd campaigns will now feature their own specific UTM attributes, paving the way for more accurate tracking configurations.</p><p><strong>What changes for us with this update?</strong></p><p>This update directly affects the “Default Channel Grouping” classifications within Google Analytics 4 (GA4) dashboards. Previously, Microsoft Ads traffic was generally aggregated under the “Paid Search” group. Under the new structure, each campaign type is correctly assigned to its appropriate channel in GA4.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tw3zsMopaeymwMHWImuUQg.png" /></figure><p>This shift may cause sudden fluctuations in performance reports. For instance, Shopping or Display campaigns that previously appeared under “Paid Search” will now be categorized into their correct channels, potentially resulting in a noticeable drop in “Paid Search” metrics.</p><p><strong>So, what should we do?</strong></p><p>To maintain data integrity during this transition:</p><ul><li>Ensure that the Auto-Tagging system is enabled in your Microsoft Advertising dashboard and that the new information is being reflected correctly.</li><li>Check your GA4 “Traffic Acquisition” reports to verify how traffic is being categorized, preventing any misinterpretation of sudden drops or spikes in your data.</li></ul><p>By doing so, we can adapt to the change while ensuring accurate reporting and data integrity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83b6386031cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Tag Gateway]]></title>
            <link>https://medium.com/@eceminngg/google-tag-gateway-dfc987ac7f1b?source=rss-411563e5fed0------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfc987ac7f1b</guid>
            <category><![CDATA[google-analytics]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[measurement]]></category>
            <dc:creator><![CDATA[Eceminngg]]></dc:creator>
            <pubDate>Sun, 10 May 2026 20:16:04 GMT</pubDate>
            <atom:updated>2026-05-10T20:16:04.507Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QqTs4Af339eZcH3jgXbxYw.png" /></figure><h3>Google Tag Gateway nedir? Ne değildir?</h3><p>Dijital pazarlama ve veri analitiği dünyası, gizlilik düzenlemeleri ve tarayıcı kısıtlamaları (çerezlerin ölümü gibi) nedeniyle büyük bir değişimden geçiyor. Bu değişimde karşımıza çıkan en yeni kavramlardan biri Google Tag Gateway.</p><p>Bu yazıda, Gateway’in ne olduğunu, Server-Side GTM ile farklarını ve hangi işletme için hangi çözümün uygun olduğunu detaylandıracağız.</p><p><strong>Google Tag Gateway Nedir?</strong></p><p>Google Tag Gateway, Google’ın sunduğu ve istemci tarafı (client-side) ile sunucu tarafı (server-side) arasında bir “köprü” görevi gören, yönetilen bir altyapıdır. Temel amacı, web sitenizden gönderilen verileri doğrudan Google reklam ve analitik araçlarına göndermeden önce ilk taraf (first-party) bir bağlamda toplamanıza olanak tanımaktır.</p><p><strong>Google Tag vs. Google Tag Gateway: Fark Nedir?</strong></p><p>Bu iki kavram sıklıkla karıştırılsa da rolleri oldukça farklıdır.</p><p><strong>Google Tag (gtag.js):</strong> Web sitenize yerleştirdiğiniz kod kütüphanesidir. Veriyi toplar ve gönderilecek rotayı belirler. Pixel mantığıyla çalışıyor diyebiliriz.</p><p><strong>Google Tag Gateway:</strong> Bu kodun veriyi gönderdiği “durak”tır. Veri doğrudan Google sunucularına gitmek yerine, sizin kontrolünüzdeki (veya sizin alan adınız altındaki) Gateway’e uğrar. Server Side ölçümleme diyebiliriz.</p><h3>Google Tag Gateway Neden ve Nasıl Kullanılır?</h3><p><strong>Neden Kullanılır?</strong></p><ol><li><strong>Gizlilik ve Uyumluluk:</strong> Verileri Google’a iletmeden önce anonimleştirebilir veya filtreleyebilirsiniz.</li><li><strong>ITP ve Reklam Engelleyiciler:</strong> Veri sizin alt alan adınızdan (örneğin: metrics.siteniz.com) geçtiği için tarayıcı kısıtlamalarına daha az takılır.</li><li><strong>Performans:</strong> Tarayıcı üzerindeki yükü azaltarak sayfa hızına katkı sağlayabilir.</li></ol><p><strong>Nasıl Kullanılır?</strong> Google Tag Gateway genellikle Google Cloud üzerinde kurulan bir yapılandırmadır. Google Tag Manager (GTM) üzerinden bir “Gateway” hedefi belirleyerek verilerinizi bu uç noktaya (endpoint) yönlendirirsiniz.</p><h3>Google Tag Gateway vs. Server-Side GTM (sGTM)</h3><p>Bu iki teknoloji birbirine çok benzese de karmaşıklık ve yetenek açısından ayrılırlar:</p><p><strong>Server-Side GTM:</strong> Tam teşekküllü bir sunucu ortamıdır. Veriyi sadece Google’a değil, Facebook CAPI, TikTok veya kendi veri tabanınıza da gönderebilirsiniz. Veriyi her yönüyle manipüle etme (enrichment) şansınız vardır.</p><p><strong>Google Tag Gateway</strong>: Daha çok Google ekosistemine odaklanmış, sGTM’nin “hafifletilmiş” bir versiyonudur. Kurulumu daha kolaydır ancak sadece Google servisleri (Ads, GA4) için optimize edilmiştir.</p><p><strong>Kısaca</strong> Google Tag Gateway, Google ekosisteminde kalarak veri gizliliği ve kalitesini artırmak isteyenler için “tak-çalıştır” tadında bir çözümdür. Ancak tam kontrol ve çoklu platform desteği arıyorsanız, Server-Side GTM hala altın standarttır.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><h3>Google Tag Gateway: What Is It and What Is It Not?</h3><p>The world of digital marketing and data analytics is undergoing a massive transformation due to privacy regulations and browser restrictions (such as the death of cookies). One of the newest concepts emerging from this change is <strong>Google Tag Gateway</strong>.</p><p>In this article, we will detail what the Gateway is, its differences from Server-Side GTM, and which solution is suitable for which business.</p><h3>What is Google Tag Gateway?</h3><p><strong>Google Tag Gateway</strong> is a managed infrastructure provided by Google that acts as a “bridge” between the client-side and the server-side. Its primary purpose is to allow you to collect data sent from your website in a <strong>first-party</strong> context before it is sent directly to Google advertising and analytics tools.</p><h3>Google Tag vs. Google Tag Gateway: What’s the Difference?</h3><p>Although these two concepts are often confused, their roles are quite distinct:</p><ul><li><strong>Google Tag (gtag.js):</strong> This is the code library you place on your website. It collects data and determines the route it will be sent. We can say it works with a “pixel” logic.</li><li><strong>Google Tag Gateway:</strong> This is the “stop” where that code sends the data. Instead of the data going directly to Google servers, it stops by the Gateway under your control (or under your own domain). We can call this a form of <strong>Server-Side measurement</strong>.</li></ul><h3>Why and How to Use Google Tag Gateway?</h3><h4>Why Use It?</h4><ul><li><strong>Privacy and Compliance:</strong> You can anonymize or filter data before transmitting it to Google.</li><li><strong>ITP and Ad Blockers:</strong> Since the data passes through your own subdomain (e.g., metrics.yourwebsite.com), it is less likely to be caught by browser restrictions.</li><li><strong>Performance:</strong> It can contribute to page speed by reducing the processing load on the browser.</li></ul><h4>How to Use It?</h4><p>Google Tag Gateway is generally a configuration set up on <strong>Google Cloud</strong>. By defining a “Gateway” destination via Google Tag Manager (GTM), you route your data to this specific endpoint.</p><h3>Google Tag Gateway vs. Server-Side GTM (sGTM)</h3><p>While these two technologies are very similar, they differ in terms of complexity and capability:</p><ul><li><strong>Server-Side GTM:</strong> A full-fledged server environment. You can send data not only to Google but also to Facebook CAPI, TikTok, or your own internal database. You have the ability to manipulate and enrich the data in every aspect.</li><li><strong>Google Tag Gateway:</strong> A “lightweight” version of sGTM, focused more on the Google ecosystem. It is easier to set up but optimized exclusively for Google services (Ads, GA4).</li></ul><p>In short, <strong>Google Tag Gateway</strong> is a “plug-and-play” style solution for those who want to stay within the Google ecosystem while increasing data privacy and quality. However, if you are looking for full control and multi-platform support, <strong>Server-Side GTM</strong> remains the gold standard.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfc987ac7f1b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BigQuery’de Yeni AI Fonksiyonları]]></title>
            <link>https://medium.com/@eceminngg/bigqueryde-yeni-ai-fonksiyonlar%C4%B1-96d22cf115a3?source=rss-411563e5fed0------2</link>
            <guid isPermaLink="false">https://medium.com/p/96d22cf115a3</guid>
            <category><![CDATA[bigquery]]></category>
            <category><![CDATA[gemini]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[sql]]></category>
            <dc:creator><![CDATA[Eceminngg]]></dc:creator>
            <pubDate>Tue, 28 Apr 2026 06:29:40 GMT</pubDate>
            <atom:updated>2026-04-28T06:29:40.442Z</atom:updated>
            <content:encoded><![CDATA[<p>Veri dünyasında büyük bir devrim yaşanıyor. Ocak 2026&#39;da Google Cloud, BigQuery’de AI.GENERATE ve AI.GENERATE_TABLE fonksiyonlarının genel kullanıma açık hale geldiğini duyurdu. Bu gelişme, şirketlerin yapılandırılmamış verilerle çalışma biçimini kökten değiştiriyor. Artık resimler, videolar, ses kayıtları ve PDF&#39;lerdeki değerli bilgileri çıkarmak için karmaşık veri işleme hatlarına veya harici API&#39;lara ihtiyacınız yok.</p><p>Gemini 3.0 Pro ve Flash modellerini doğrudan BigQuery’ye entegre ederek, SQL kullanarak üretken yapay zeka ve vektör gömme (embedding) modelleri ile çalışmayı basitleştiren bu yeni yaklaşım, veri analistlerinin ve veri bilimcilerin iş akışlarını dramatik şekilde hızlandırıyor.</p><h4>1. AI.GENERATE Fonksiyonu</h4><p>AI.GENERATE fonksiyonu, Vertex AI Gemini modeline istekler göndererek, üretilen veriyi, tam model yanıtını ve işlem durumunu içeren bir STRUCT döndürür.</p><pre>SELECT <br>  title,<br>  AI.GENERATE(<br>    CONCAT(&quot;Bu haberi tek cümlede özetle: &quot;, body)<br>  ).result AS makale_ozeti<br>FROM bigquery-public-data.bbc_news.fulltext<br>LIMIT 3;</pre><p>BQML, üretken AI fonksiyonları için en yeni <strong>Gemini 3.0</strong> ailesini destekler. Düşük gecikme süreli işlemler için Flash, karmaşık akıl yürütme gerektiren görevler için Pro modelini şu şekilde çağırabilirsiniz:</p><pre>SELECT AI.GENERATE(<br>  &#39;BigQuery ML ve Gemini entegrasyonunun avantajlarını listeleyin&#39;,<br>  endpoint =&gt; &#39;gemini-3-flash&#39;<br>).result AS ai_yaniti;</pre><h4>2. AI.EMBED Fonksiyonu</h4><p>AI.EMBED fonksiyonu karmaşık verileri gömülü vektörlere (embedding) dönüştürür. Bu, semantik arama (anlamsal arama) ve tavsiye sistemleri kurmak için kritik bir adımdır.</p><pre>CREATE OR REPLACE TABLE veri_setim.haber_gomulu AS<br>SELECT <br>  baslik,<br>  icerik,<br>  AI.EMBED(<br>    icerik,<br>    endpoint =&gt; &#39;text-embedding-005&#39;,<br>    model_params =&gt; JSON &#39;{&quot;outputDimensionality&quot;: 768}&#39;<br>  ).result AS gomulu_vektor<br>FROM bigquery-public-data.bbc_news.fulltext;</pre><h4>3. Çok Modlu (Multimodal) Veri Analizi</h4><p>BigQuery AI fonksiyonlarının en güçlü yanı, sadece metinle sınırlı kalmamasıdır. SQL kullanarak Google Cloud Storage’daki (GCS) multimodal verileri (görüntü, ses, video ve PDF) doğrudan analiz edebilirsiniz.</p><p><strong>Örnek: Görüntüden Bilgi Çıkarımı</strong></p><pre>SELECT<br>  uri,<br>  AI.GENERATE(<br>    uri,<br>    &#39;Bu görüntüdeki ana öğeleri listele ve marka logosu varsa belirt.&#39;<br>  ).result AS goruntu_analizi<br>FROM `proje.veri_seti.nesne_tablosu`<br>LIMIT 5;</pre><h3>Geleceğin İşletme Zekası (BI)</h3><p>BigQuery’deki bu yeni AI fonksiyonları, veriyi “pasif bir kayıt” olmaktan çıkarıp “aktif bir içgörü kaynağına” dönüştürüyor. Artık veri ambarınız sadece rakamları topladığınız bir yer değil; videolarınızı izleyen, belgelerinizi okuyan ve müşterilerinizin duygularını anlayan bir yapay zeka merkezidir.</p><p>Gemini 3.0&#39;ın gücünü SQL’in basitliğiyle birleştirerek, işletmeniz için gerçek zamanlı ve derinlemesine analizler üretmeye hemen başlayabilirsiniz. Geleceğin veri analitiği artık kod bloklarında değil, doğru sorulmuş SQL sorgularında gizli.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><h3>New AI Functions in BigQuery</h3><p>A major revolution is taking place in the world of data. In January 2026, Google Cloud announced the general availability of the AI.GENERATE and AI.GENERATE_TABLE functions in BigQuery. This development fundamentally changes how companies work with unstructured data. You no longer need complex data processing pipelines or external APIs to extract valuable information from images, videos, audio recordings, and PDFs.</p><p>By integrating Gemini 3.0 Pro and Flash models directly into BigQuery, this new approach simplifies working with generative AI and vector embedding models using SQL, dramatically accelerating the workflows of data analysts and data scientists.</p><h3>1. AI.GENERATE Function</h3><p>The AI.GENERATE function sends requests to the Vertex AI Gemini model and returns a STRUCT containing the generated data, the full model response, and the processing status.</p><pre>SELECT <br>  title,<br>  AI.GENERATE(<br>    CONCAT(&quot;Summarize this news in a single sentence: &quot;, body)<br>  ).result AS article_summary<br>FROM bigquery-public-data.bbc_news.fulltext<br>LIMIT 3;</pre><p>BQML supports the latest Gemini 3.0 family for generative AI functions. You can call the Flash model for low-latency operations and the Pro model for tasks requiring complex reasoning as follows:</p><pre>SELECT AI.GENERATE(<br>  &#39;List the advantages of BigQuery ML and Gemini integration&#39;,<br>  endpoint =&gt; &#39;gemini-3-flash&#39;<br>).result AS ai_response;</pre><h3>2. AI.EMBED Function</h3><p>The AI.EMBED function converts complex data into embedded vectors (embeddings). This is a critical step for building semantic search and recommendation systems.</p><pre>CREATE OR REPLACE TABLE my_dataset.news_embedded AS<br>SELECT <br>  title,<br>  content,<br>  AI.EMBED(<br>    content,<br>    endpoint =&gt; &#39;text-embedding-005&#39;,<br>    model_params =&gt; JSON &#39;{&quot;outputDimensionality&quot;: 768}&#39;<br>  ).result AS embedded_vector<br>FROM bigquery-public-data.bbc_news.fulltext;</pre><h3>3. Multimodal Data Analysis</h3><p>The strongest aspect of BigQuery AI functions is that they are not limited to text. You can directly analyze multimodal data (images, audio, video, and PDFs) in Google Cloud Storage (GCS) using SQL.</p><p><strong>Example: Information Extraction from Image</strong></p><pre>SELECT<br>  uri,<br>  AI.GENERATE(<br>    uri,<br>    &#39;List the main elements in this image and specify if there is a brand logo.&#39;<br>  ).result AS image_analysis<br>FROM `project.dataset.object_table`<br>LIMIT 5;</pre><h3>The Future of Business Intelligence (BI)</h3><p>These new AI functions in BigQuery transform data from being a “passive record” into an “active source of insight.” Your data warehouse is no longer just a place where you collect numbers; it is an AI hub that watches your videos, reads your documents, and understands your customers’ emotions.</p><p>By combining the power of Gemini 3.0 with the simplicity of SQL, you can immediately start generating real-time and in-depth analyses for your business. The future of data analytics is no longer hidden in code blocks, but in correctly phrased SQL queries.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96d22cf115a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GA4 New User & Return User]]></title>
            <link>https://medium.com/@eceminngg/ga4-new-user-return-user-e0459ae2e728?source=rss-411563e5fed0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0459ae2e728</guid>
            <category><![CDATA[google-analytics]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[consent]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Eceminngg]]></dc:creator>
            <pubDate>Tue, 21 Apr 2026 06:45:34 GMT</pubDate>
            <atom:updated>2026-04-21T07:01:24.115Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ODMFhg3SPbOyppSUUMo71A.png" /></figure><p>Dijital analitikle uğraşan herkesin analizlerde en az bir ekre kafasını kurcalamış bir konu var. New user ile return user sayısı ile total user sayısı neden orantısız geliyor ?</p><p>Ufak teknik detaylarla bu konuyu inceleyelim.</p><p><strong>İlk etki eden alanımız date range</strong>. Seçilen metrikler tarih aralığına göre yeniden etiketlenirler. Senaryolaştırmamız gerekirse ;</p><ul><li>Bir kullanıcı ilk kez ocakta geldi ve first_visit eventi tetiklendi, daha sonra 20 ocakta tekrar geldi.</li><li>Ocak ayı raporunda bu kullanıcı hem new user hem de return user olarak hesaplanır.</li><li>15–25 ocak gibi spesifik bir aralıkta ise sadece returning user olarak hesaplanır.</li></ul><p>Aslında new user + return user ≠ total user :)</p><p><strong>İkinci etmenimiz first visit</strong> eventinin hesaplama yöntemi. GA4, bir kullanıcının “New” olup olmadığına bakarken sadece first_visit event’ine güvenir. Eğer bir session içinde bu event ateşlenmemişse, o kullanıcı o tarih aralığı için asla &quot;New&quot; olamaz.</p><p>Ancak burada bir <strong>“bad tracking”</strong> riski de var. Eğer sGTM (Server-Side) kurulumunuzda veya Consent Mode (Rıza Modu) yapılandırmanızda bir eksiklik varsa; kullanıcının cookie’si (çerezi) temizlenmişse, GA4 bu kişiyi her seferinde yeni biri sanıp tekrar first_visit tetikleyebilir. Bu da verinizin şişmesine neden olur.</p><p>Peki bunun önüne geçmek için napabiliriz?</p><p>Eğer “temiz veri” (clean insights) istiyorsak, GA4 arayüzünün sunduğu hazır metriklerle bir yere kadar gidebiliriz. Kendi iş mantığımızı (business logic) kurmak için <strong>BigQuery</strong> kullanmamız şart oluyor.</p><p>Neden mi?</p><ul><li><strong>User Pseudo ID</strong> üzerinden gerçek tekilleştirme yapabilirsiniz.</li><li>first_visit event&#39;inin tarihinden bağımsız olarak, kullanıcının tüm yaşam boyu yolculuğunu (lifetime value) analiz edebilirsiniz.</li><li>Tarih aralığına sıkışmadan, “Bu kullanıcı gerçekten ilk kez mi geldi yoksa sadece cihaz mı değiştirdi?” sorusuna User ID entegrasyonuyla cevap verebilirsiniz.</li></ul><h3>Sonuç Olarak…</h3><p>GA4 arayüzü hızlı bakışlar için iyidir ama derinlemesine bir kullanıcı analizi için yanıltıcı olabilir. Biz analistler için en güvenli liman, ham datayı çekip kendi SQL sorgularımızla kullanıcı tanımlarımızı yapmak.</p><p>Veri kayıplarını minimize etmek için <strong>Server-Side</strong> tarafında First-Party veri toplamanın önemini de unutmamak gerek. Çünkü tarayıcıların insafına kalan bir first_visit event&#39;i, her zaman doğruyu söylemeyebilir. ;)</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Anyone involved in digital analytics has likely been puzzled by this at least once: Why doesn’t the sum of <strong>New Users</strong> and <strong>Returning Users</strong> equal the <strong>Total User</strong> count?</p><p>Let’s dive into the technical details behind this discrepancy.</p><h3>1. The Impact of Date Ranges</h3><p>Metrics are re-labeled based on the specific date range you select. Let’s look at a scenario:</p><ul><li>A user visits for the first time on January 1st, triggering the first_visit event.</li><li>The same user returns on January 20th.</li></ul><p>In a report for the <strong>entire month of January</strong>, this individual is counted as <strong>both</strong> a New User and a Returning User. However, if you look at a specific range like <strong>January 15–25</strong>, they are counted <strong>only</strong> as a Returning User.</p><p>In short: <strong>New Users + Returning Users ≠ Total Users</strong> :)</p><h3>2. The first_visit Calculation Logic</h3><p>GA4 relies exclusively on the first_visit event to determine if a user is &quot;New.&quot; If this event is not fired within a session during your selected timeframe, that user can never be classified as &quot;New&quot; for that period.</p><p>However, there is a risk of <strong>“bad tracking.”</strong> If there are gaps in your <strong>sGTM (Server-Side)</strong> setup or <strong>Consent Mode</strong> configuration — or if a user clears their cookies — GA4 may mistakenly identify them as a new visitor every time, re-triggering the first_visit event. This leads to inflated data.</p><h3>3. How to Ensure Data Accuracy?</h3><p>If we want “clean insights,” the standard metrics in the GA4 interface can only take us so far. To apply true business logic, using <strong>BigQuery</strong> becomes essential.</p><p><strong>Why BigQuery?</strong></p><ul><li><strong>True Deduplication:</strong> You can perform accurate user deduplication using the User Pseudo ID.</li><li><strong>Lifetime Analysis:</strong> You can analyze a user’s entire lifetime journey regardless of the first_visit event date.</li><li><strong>Beyond Date Ranges:</strong> By integrating User ID, you can answer the critical question: &quot;Is this truly a first-time visitor, or did they simply switch devices?&quot;</li></ul><h3>Final Thoughts</h3><p>The GA4 interface is great for quick check-ins, but it can be misleading for deep-dive user analysis. For analysts, the “safe harbor” is pulling raw data and defining user segments through custom <strong>SQL queries</strong>.</p><p>It’s also vital to remember the importance of <strong>First-Party data collection</strong> via Server-Side tracking to minimize data loss. A first_visit event left to the mercy of browser restrictions doesn&#39;t always tell the truth. ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0459ae2e728" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Same Origin Deployment ve Server-Side Tracking İlişkisi]]></title>
            <link>https://medium.com/@eceminngg/same-origin-deployment-ve-server-side-tracking-i%CC%87li%C5%9Fkisi-2ded3fb93da8?source=rss-411563e5fed0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ded3fb93da8</guid>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[measurement]]></category>
            <category><![CDATA[server-side]]></category>
            <category><![CDATA[gtm-strategy]]></category>
            <dc:creator><![CDATA[Eceminngg]]></dc:creator>
            <pubDate>Thu, 26 Feb 2026 14:21:50 GMT</pubDate>
            <atom:updated>2026-02-26T14:21:50.520Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SmrR5pSPLFh2yQhqpRItVw.png" /></figure><h4>Modern Ölçümleme Mimarisinde Neden Birlikte Düşünülmelidir?</h4><p>Ölçümleme metodlarına artık en büyük değişiklik tracking olayının browser içinde değil server tarafında çözümlenmesi oldu. Server Side ölçümleme ile birlikte bu mimariyi ayakta tutan Same Origin Deployment hayatımıza girdi. Same Origin Deployment ve Server Side Tracking arasındaki ilişkiyi bu yazıda detaylı ele alacağız.</p><h4>Server-Side Tracking Nedir?</h4><p>Klasik tracking modelinde kullanıcının browserı üzerinden tüm veri gönderilirdi. Ad blocker, cookie engelleri, ITP, client side manipülasyon gibi durumlardan veri kaybı meydana gelirdi.</p><p>Bu gibi sorunlar Server Side Tracking modelinin kullanılmasına öncülük etti. Veri third party platformlara gitmeden önce data sahibinin yönetebildiği bir servera gider ve sonra filtrelenerek platformlara dağılır.</p><p>Server Side Tracking ile veri kontrolü, güvenlik, veri kayıplarının engellenmesi gibi konularda çözüme ulaşıldı.</p><h4>Server-Side Tracking’in Gizli Problemi</h4><p>Çoğu kurulum aşağıdaki şekilde yapılmaktadır ;</p><pre>Website: https://example.com<br>sGTM: https://gtm-server.run.app</pre><p>Browser ise bu kurulumu third party request olarak görür. Teknik olarak Server Side kullanırsınız ama hala third party durumuna düşersiniz.</p><p>Sonuç olarak böyle bir kurulumda hala sorunlarınız devam eder. Tam da bu anda devreye Same Origin Deployment girer.</p><h4><strong>Same Origin Deployment Nedir?</strong></h4><p>Same origin ;</p><ul><li>aynı protocol</li><li>aynı domain</li><li>aynı port</li></ul><p>Server Side Endpoint’ in site ile aynı origin altında olmasıdır.</p><pre>https://example.com        → Website<br>https://example.com/metrics → Tracking endpoint</pre><p>Browser için bu şekilde bir ölçümleme ise external tracking değil sitenin kendi endpointidir.</p><p><strong>Server-Side Tracking + Same Origin = Gerçek First-Party Tracking</strong></p><p>Server — Side Tracking veriyi servera taşırken Same Origin Deployment browserın buna güvenmesini sağlar.</p><p>Same Origin Deployment aslında bir routing mimarisidir. Kullanıcı domain değiştirmez ama request arka planda başka servera gider.</p><pre>                Kullanıcı<br>                    │<br>                    ▼<br>              CDN / Load Balancer<br>                    │<br>        ┌───────────┴───────────┐<br>        │                       │<br>        ▼                       ▼<br> Website Server          sGTM Server<br> (/home)                 (/metrics)</pre><p>Server-side tracking’i şöyle düşünebiliriz:</p><ul><li>Server-side → Veriyi arka kapıdan taşıyan kurye</li><li>Same origin → Kapının sizin evinize ait olduğunu gösteren adres</li></ul><p>Adres doğru değilse kurye içeri alınmaz.</p><p>Bugün modern measurement mimarisinde doğru soru artık şu değil: Server-side tracking kurmalı mıyız?</p><p>Asıl soru: Server-side tracking <strong>same origin</strong> mi çalışıyor?</p><p>Çünkü:</p><ul><li>Server-side tracking = altyapı</li><li>Same origin deployment = güven katmanı</li></ul><p>İkisi birlikte çalıştığında gerçek anlamda <strong>first-party tracking</strong> elde edilir.</p><h3>The Relationship Between Same Origin Deployment and Server-Side Tracking</h3><h3>Why Should They Be Considered Together in Modern Measurement Architecture?</h3><p>One of the biggest shifts in measurement methodologies today is that tracking is no longer resolved inside the browser but on the server side. Along with server-side measurement, <strong>Same Origin Deployment</strong> has emerged as a key architectural component that keeps this system sustainable.</p><p>In this article, we will explore the relationship between Same Origin Deployment and Server-Side Tracking in detail.</p><h3>What is Server-Side Tracking?</h3><p>In the traditional tracking model, all data was sent directly through the user’s browser. This often resulted in data loss due to ad blockers, cookie restrictions, Intelligent Tracking Prevention (ITP), and client-side manipulation.</p><p>These challenges led to the adoption of the <strong>Server-Side Tracking</strong> model. Instead of sending data directly to third-party platforms, data is first routed to a server controlled by the data owner, where it can be processed and filtered before being distributed to external platforms.</p><p>Server-side tracking provides solutions for:</p><ul><li>Data control</li><li>Security improvement</li><li>Reduction of data loss</li></ul><h3>The Hidden Problem of Server-Side Tracking</h3><p>Most implementations are configured as follows:</p><pre>Website: https://example.com<br>sGTM:    https://gtm-server.run.app</pre><p>From the browser’s perspective, this setup is still treated as a <strong>third-party request</strong>. Technically, you are using server-side tracking, but you still fall into a third-party context.</p><p>As a result, many of the original problems continue to exist.</p><p>This is exactly where <strong>Same Origin Deployment</strong> comes into play.</p><h3>What is Same Origin Deployment?</h3><p>Same origin means sharing:</p><ul><li>the same protocol</li><li>the same domain</li><li>the same port</li></ul><p>It refers to hosting the server-side tracking endpoint under the same origin as the website.</p><p>Example:</p><pre>https://example.com          → Website<br>https://example.com/metrics  → Tracking endpoint</pre><p>For the browser, this measurement is no longer external tracking — it becomes an endpoint belonging to the website itself.</p><h3>Server-Side Tracking + Same Origin = True First-Party Tracking</h3><p>While server-side tracking moves data processing to the server, <strong>Same Origin Deployment ensures that the browser trusts this communication</strong>.</p><p>Same origin deployment is essentially a routing architecture. The user never changes domains, but requests are routed to another server behind the scenes.</p><pre>User<br>                  │<br>                  ▼<br>          CDN / Load Balancer<br>                  │<br>        ┌─────────────┐<br>        │             │<br>        ▼             ▼<br> Website Server    sGTM Server<br>   (/home)          (/metrics)</pre><p>We can think of server-side tracking as:</p><p><strong>Server-side → The courier delivering data through a back door</strong></p><p><strong>Same origin → The address proving the door belongs to your house</strong></p><p>If the address is not correct, the courier will not be allowed inside.</p><h3>The Real Question in Modern Measurement Architecture</h3><p>Today, the right question is no longer:</p><blockquote>“Should we implement server-side tracking?”</blockquote><p>The real question is:</p><blockquote>“Is our server-side tracking running under the same origin?”</blockquote><p>Because:</p><ul><li><strong>Server-side tracking = infrastructure</strong></li><li><strong>Same origin deployment = trust layer</strong></li></ul><p>Only when both work together can true first-party tracking be achieved.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ded3fb93da8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Analytics 4 — Insights]]></title>
            <link>https://medium.com/@eceminngg/google-analytics-4-insights-b92871c795e5?source=rss-411563e5fed0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b92871c795e5</guid>
            <category><![CDATA[google-analytics]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[google-analytics4]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Eceminngg]]></dc:creator>
            <pubDate>Mon, 19 Feb 2024 20:35:51 GMT</pubDate>
            <atom:updated>2024-02-19T20:35:51.851Z</atom:updated>
            <content:encoded><![CDATA[<h3>Google Analytics 4 — Insights</h3><p>Google Analytics 4 panelinde karşımıza yeni bir özellik olarak Insights sayfası çıkmaktadır. Bu sayfada oluşturduğunuz ve aktif ettiğiniz insight özelinde bildirimler alabilirsiniz. Aksiyon almanız gereken zamanları size bildirerek hedefler doğrultusunda iyileşmeler yapılmasına yardımcı olacak öneriler sunmaktadır.</p><p>Bu özelliği verimli kullanabilmek için aylık, günlük, haftalık bazlı verilerinizi raporlayabilir ve bu değişimleri çıkararak üstünde veya altında değişimlerde anomalileri görebilirsiniz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*prmrK3Pc5IJjKGLN" /></figure><p>Transaction, total user, views, event revenue, conversions, engagement rate vb. metrikleri üzerindeki değişimleri inceleyebilirsiniz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/0*IfAwNkgfw_Vpj1Oq" /></figure><p>Değişim oranlarını aşağıdaki gibi seçebilir ve bu durumlarda mail üzerinden bildirimler alabilirsiniz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*e01BG-C2iJVbpU58" /></figure><p>Oluşturduğunuz insight durumları ile Google Analytics 4 paneli size bir Insights sayfası sunmaktadır. Bu sayfada geçmiş bildirimleri görebilir ve aksiyon almanız gereken alanları görebilirsiniz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/0*pgTdM2-zHww0z3M4" /><figcaption><a href="https://support.google.com/analytics/answer/9443595?hl=en">https://support.google.com/analytics/answer/9443595?hl=en</a></figcaption></figure><p>Bunların dışında Google Analytics 4 size otomatik oluşturduğu analizleri vererek anomali durumları hakkında sizi bilgilendirir.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Jdt8O3okdTDRt9dz" /><figcaption><a href="https://support.google.com/analytics/answer/9443595?hl=en">https://support.google.com/analytics/answer/9443595?hl=en</a></figcaption></figure><p>A new feature in the Google Analytics 4 panel is the Insights page. On this page, you can receive notifications specific to the insights you create and activate. It provides recommendations to help you make improvements in line with your goals by notifying you of times when action is needed.</p><p>To effectively use this feature, you can report your data on a monthly, daily, or weekly basis and identify anomalies by comparing these changes, whether they are above or below the changes.</p><p>You can examine changes in metrics such as transactions, total users, views, event revenue, conversions, engagement rate, and more.</p><p>You can select change rates as follows and receive notifications via email in these cases.</p><p>With the insights you create, the Google Analytics 4 panel provides you with an Insights page. Here, you can view past notifications and see areas where action is needed.</p><p>In addition to these, Google Analytics 4 informs you about anomaly situations by providing automatically generated analyses.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b92871c795e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>