<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Segmentation on Inês Garcia</title>
    <link>https://null-hypothesis.ines-garcia263.workers.dev/tags/segmentation/</link>
    <description>Recent content in Segmentation on Inês Garcia</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Inês Garcia</copyright>
    <lastBuildDate>Wed, 18 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://null-hypothesis.ines-garcia263.workers.dev/tags/segmentation/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Traffic-Based Customer Segmentation: A Practical Approach with Quantile Bucketing and k-NN Anomaly Detection</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/traffic-based-customer-segmentation/</link>
      <pubDate>Wed, 18 Jun 2025 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/traffic-based-customer-segmentation/</guid>
      <description>&lt;p&gt;Customer segmentation is one of those problems that sounds straightforward until you actually sit down with the data. In this post I&amp;rsquo;ll walk through an approach I built for segmenting customers based on their HTTP traffic patterns — the kind of traffic data that tells you not just how much a customer uses a service, but &lt;em&gt;how&lt;/em&gt; they use it.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
