#20 -- Breakdown Reports by Country, City, Device Type, and Environment

Priority: High Status: Partial (device shipped; country/city/environment pending) Category: Reporting Raised by: Trung Pham, Dec 2025

Problem

Humology wants reports broken down by:

• Country
• City
• Device type (done)
• Environment (desktop vs mobile)

Kevin's Assessment (Discord)

And I'm not too sure again, what to do with city? We could try to do per-IP geolocation against some geo DB, but it would add quite some cost on our side. Also comes with regulatory issues.. Can also get closes CDN POP, but that's rather innacurate. There's just about 300 cities across the globe for it Environment is most likely desktop vs mobile

What We Know

• Device type: shipped via custom analytics layer (Kevin 26 Mar)
• Country: Cavai can turn this on (already collecting)
• City: problematic -- see Kevin's assessment
• Environment: likely desktop vs mobile distinction -- should be straightforward
• GDPR compliance concern raised previously -- Humology must take responsibility for using geo analytics within Europe
• Lars committed (5 May) to dashboard MVP exposing custom events, devices, regions by end Q2 (30 Jun)

Cavai Feasibility Assessment

Can we fix this from our side? Mostly yes, with caveats.

Dimension	Feasibility	Notes
Device type	Done	Already in Bunny Analytics
Country	Easy	Already collecting, just needs to be surfaced
Environment	Easy	Desktop vs mobile, straightforward to add
City	Hard	Two options, both have issues

City options:

1. IP geolocation -- accurate but expensive (geo DB licensing) and regulatory concerns (GDPR)
2. CDN POP mapping -- free but very inaccurate (~300 cities globally, maps to nearest CDN node, not actual user location)

Open Questions

1. Is city-level data actually critical for Humology, or would country + device + environment be sufficient?
2. If city is needed, who bears the cost of geo DB integration?
3. Regulatory sign-off for geo analytics in European markets?

Next Steps

1. Ship country and environment -- should be quick wins in the analytics layer
2. Push back on city or get Humology to confirm it's truly needed
3. These dimensions should be surfaced through the reporting dashboard (#21, Linear project)
4. Cross-reference with Lars's Q2 commitment

Related Items

• #19 (device ID collection)
• #24 (bespoke analytics layer)
• #21 (report sharing -- Looker Studio API integration)
• Reporting Dashboard (Linear project -- natural home for these breakdowns)