<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Server-Side on Measure Addict</title><link>https://measureaddict.com/tags/server-side/</link><description>Recent content in Server-Side on Measure Addict</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Mon, 29 Jun 2026 23:22:37 +0100</lastBuildDate><atom:link href="https://measureaddict.com/tags/server-side/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Build a First-Party Analytics Proxy with Netlify Functions and Tealium Server-Side</title><link>https://measureaddict.com/post/first-party-analytics-proxy-netlify-tealium/</link><pubDate>Wed, 24 Jun 2026 00:00:00 +0000</pubDate><guid>https://measureaddict.com/post/first-party-analytics-proxy-netlify-tealium/</guid><description>&lt;h2 id="the-problem-ad-blockers-and-your-analytics-data"&gt;The Problem: Ad Blockers and Your Analytics Data&lt;/h2&gt;
&lt;p&gt;Here&amp;rsquo;s something worth thinking about if you run an analytics or tech blog: your readership is likely full of people who block ads — and with them, your tracking scripts.&lt;/p&gt;
&lt;p&gt;Browser extensions like uBlock Origin block requests to well-known analytics endpoints like &lt;code&gt;collect.tealiumiq.com&lt;/code&gt; or &lt;code&gt;google-analytics.com&lt;/code&gt; by matching against public block lists. Your tracking code fires on the page, the browser quietly drops the request, and you never see that visit.&lt;/p&gt;</description></item></channel></rss>