How to Analyze Traffic Distribution in StackCP

Traffic Distribution is the geographic view within StackCP's Statistics dashboard — it shows you where in the world your website's requests are coming from. Paired with the CDN Statistics overview covered in our companion guide, it gives you a genuinely useful picture of who's visiting your site and from where.

What Is Traffic Distribution, Specifically?

While the CDN Statistics overview shows bandwidth, hits, SSL adoption, and error rates, the Traffic Distribution view focuses specifically on the geographic breakdown of incoming requests to your site. It answers questions like:

• Which countries is my traffic actually coming from?
• Does this match where I expect my customers to be?
• Is there unexpected traffic from a region I don't do business in?

Step 1: Where to Find It

1. Log in to StackCP.
2. Go to Manage Hosting, then Manage on the package you want to view.
3. Select Statistics.
4. From the CDN Statistics overview, switch to the Traffic Distribution view.

Step 2: Reading the Geographic Breakdown

You'll see a map or chart-based geographic overview of incoming requests. You can toggle the time period between Last Hour, Last Day, and Last Week, and hover over any country to see the specific figures for that location.

A few things worth knowing about how this data is captured:

• It reflects the IP address associated with each request to determine the originating country.
• It only covers HTTP traffic processed through the CDN network — it doesn't include unproxied web hosts, so if a specific site or subdomain isn't routed through the CDN, its traffic won't appear here.
• Like the wider CDN Statistics dashboard, this includes all HTTP-level traffic — including bots and crawlers — not just human visitors, so it will naturally look different from a JavaScript-based analytics tool like Google Analytics.

Step 3: Spotting Patterns Worth Investigating

A healthy pattern for most small businesses looks like traffic concentrated in the countries you actually serve, with smaller, explainable amounts from elsewhere (search engine crawlers, occasional international interest, etc.).

Worth a closer look:

• A large, unexplained share of traffic from a country you don't serve and have no marketing presence in — cross-reference with your access logs to see whether this looks like genuine (if unusual) interest, or automated/bot traffic.
• A sudden shift in geographic distribution that doesn't correspond to anything you did (a campaign, a press mention) — worth checking your access logs for the specific requests involved.

Step 4: Connecting This to Your Business Decisions

This view can genuinely inform real decisions:

• Validating your marketing focus. If your traffic distribution closely matches the regions you're actively marketing to, that's a good sign your targeting is working as intended.
• Deciding whether Block Visitors country-level blocking makes sense. If you consistently see a meaningful share of traffic from a region with no realistic business value to you, and it's associated with spam or abuse, this data can support a decision to block that region (see our companion Block Visitors guide, including the SEO caution mentioned there).
• Informing where to focus your CDN or performance investment. If a meaningful share of your real, legitimate traffic comes from a region far from your origin server, that reinforces the value of features like Edge Caching and StackCache, which specifically address that distance problem.

Common Mistakes Beginners Make

• Treating every hit as a person. Remember this reflects HTTP-level requests, including bots and crawlers — not unique human visitors.
• Reacting to a single unusual hour of data. Use the Last Day or Last Week view for a more representative picture before drawing conclusions.
• Forgetting that unproxied hosts won't show data here. If a specific domain or subdomain isn't behind the CDN, its traffic won't be reflected in this view.

Troubleshooting

"I don't see any data for one of my domains." Confirm that domain or subdomain is actually proxied through the CDN — unproxied hosts aren't included in these statistics.

"The geographic data doesn't match what I see in Google Analytics." This is expected and normal — Google Analytics only counts visits that execute JavaScript in a browser, while this view captures all HTTP-level traffic including bots and crawlers, which typically inflates the raw numbers here relative to a human-visitor-focused tool.

"I'm seeing a lot of traffic from a country I don't recognize as relevant to my business." Cross-check against your access logs for the specific request pattern. If it looks automated (rapid, repeated requests to the same or unusual URLs), consider it a candidate for IP/CIDR or country-level blocking via the Block Visitors tool.

A Simple Monthly Routine for Reviewing Traffic Distribution

Rather than only checking this when something feels wrong, a short recurring habit helps you catch both problems and opportunities early:

1. Open the Traffic Distribution view and select Last Week. Look at the overall geographic spread — does it broadly match where your customers and marketing efforts are focused?
2. Note any country contributing an unexpectedly large share. Cross-check whether you recognize a reason (a campaign, a press mention, a referral) or whether it looks unexplained.
3. If unexplained, check your access logs for the specific requests from that region — a pattern of rapid, repeated requests to the same URLs is a strong signal of automated rather than genuine traffic.
4. Decide whether any action is warranted — most months, none will be, and that's a good outcome. Occasionally, you'll spot something worth addressing via the Block Visitors tool.

This routine takes only a few minutes but builds a real, ongoing sense of your site's normal traffic pattern, which makes it much easier to notice when something genuinely changes.

How Traffic Distribution Complements StackCP's Other Tools

This view works best as part of a small toolkit rather than in isolation:

• CDN Statistics (the overview view) gives you the bandwidth, hit-ratio, and error-rate context behind the same underlying traffic.
• Access/Error Logs give you granular, request-by-request detail behind any specific pattern you notice geographically.
• Block Visitors is where you act on a confirmed, unwanted geographic or IP-based traffic source.
• Edge Caching is the tool most directly informed by this data — if your traffic genuinely spans multiple distant regions, that's confirmation the CDN's distributed caching is delivering real value, since it's specifically solving the distance problem this view helps you see.

Why Reseller Hosting Businesses Should Pay Particular Attention Here

If you're managing hosting on behalf of customers, Traffic Distribution data is genuinely useful beyond your own curiosity — it's a concrete, screenshot-able piece of evidence you can share with customers who ask "is my website actually reaching people outside India?" or "why do I need a CDN if all my customers are local?" Showing a customer their own geographic traffic breakdown is often a more persuasive, tangible answer than explaining CDN benefits in the abstract, and it can support conversations about upgrading a customer to features like Edge Caching if they aren't already enabled.

Understanding the Limits of This Data

It's worth being clear-eyed about what this view can and can't tell you. It shows you where requests originate, based on IP-derived country data — it does not tell you visitor intent, conversion behaviour, or session-level detail the way a full analytics platform does. Treat it as one useful input alongside — not a replacement for — a proper analytics tool if you're making significant marketing or business decisions. Its particular strength is exactly what a JavaScript-based analytics tool struggles with: giving you visibility into the full range of HTTP-level traffic hitting your site, bots included, which is genuinely useful for security and infrastructure decisions even if it's less useful for marketing-specific questions.