Custom Plugin Case Study

Customer Map Plugin

See where customers are—without putting PII on a map

We built Customer Map so WooCommerce merchants can understand geographic demand with anonymous city-level aggregates—hashed identities, geocode caching, and privacy-first presentation.

Industry

eCommerce analytics

Stack

WooCommerce, Google Maps / Geocoding, Action Scheduler, HPOS

Services

Custom plugin, privacy-aware analytics, data pipelines

The Project

See where customers are—without putting PII on a map

Challenge

Merchants wanted geography without doxxing buyers

Plotting raw billing addresses on a map exposes personal data. Teams still needed city-level density insight for marketing and ops planning.

What We Built

A privacy-first city aggregate pipeline

Orders feed hashed customer keys and city stats through a resumable indexer and geocode cache. The map shows anonymous density—not names, emails, or street addresses.

Result

Demand geography you can actually share

Merchants see where buyers cluster while keeping personally identifiable information off the map and out of front-end payloads.

Highlights

What shipped

  • Anonymous city-level pins—no name, email, or street
  • Hashed customer keys and city_stats aggregates
  • Resumable order indexer with geocode cache
  • Google Maps API key settings and privacy copy
  • HPOS-aware WooCommerce data pipeline

Want something like this?

Tell us about the workflow you need. We will scope a fixed-fee path with a 100% US-based team.

Start a Project Explore Plugin Development