<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Umami on CSP Guide</title>
    <link>https://csp-guide.com/tags/umami/</link>
    <description>Recent content in Umami on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 22 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/umami/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Umami Analytics: Copy-Paste Policy Examples</title>
      <link>https://csp-guide.com/posts/csp-for-umami-analytics/</link>
      <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-umami-analytics/</guid>
      
      <description>&lt;p&gt;If you add Umami to a site with a locked-down Content Security Policy, it usually fails in one of two places:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;the script never loads&lt;/li&gt;
&lt;li&gt;the browser blocks the tracking requests&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;So the CSP work for Umami is usually pretty small: &lt;code&gt;script-src&lt;/code&gt; and &lt;code&gt;connect-src&lt;/code&gt;, sometimes &lt;code&gt;img-src&lt;/code&gt; if you use fallback behavior or custom setups.&lt;/p&gt;
&lt;p&gt;I like Umami because it’s simpler than the usual analytics stack. That also means the CSP is usually cleaner than the Google Tag Manager + Google Analytics + consent-manager soup you see in production.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
