WP Event Manager's Google Maps addon enriches the event_listing custom post type with location meta: _event_location (formatted address), geolocation_lat, and geolocation_long. The default admin shows event title and date, leaving address and coordinates inside the edit screen where they are not useful for any cross-event work.

SleekView reads event_listing and promotes the Google Maps meta keys to first-class columns. Address, latitude, longitude, city, and region (where the geocoder filled them in) all become sortable, filterable, exportable fields. Inline edits write back through update_post_meta on the same keys the front-end templates read, so a corrected address shows on the next page render.

The grid is the geo planning surface editorial teams need: filter to events in one city, sort by region for marketing rollouts, spot events with missing coordinates that broke the map widget. Saved views become per-region rituals, and a CSV export of a region-filtered set hands marketing or partner managers the exact event list they need.

The Google Maps addon enriches WP Event Manager with the exact data marketing and editorial need to segment events by place, and then hides that data inside each event's edit screen. The pattern is universal across event plugins: the meta exists, the front end consumes it, but the admin list cannot surface it. The cost shows up in two places.

First, events with broken geocoding silently fail to appear on the map widget, and the only way to find them is to scroll the public site or wait for someone to report it. Second, region-aware work like local newsletters or partner handoffs ends up in exported spreadsheets because the in-product list cannot filter by city. Both problems are solved by promoting _event_location and the geolocation meta keys to columns.

Saved views become the geo rituals editorial and marketing run weekly, and inline edits route through update_post_meta so the map widget stays in sync with what the grid did. The addon already does the heavy lifting; SleekView is the surface that makes its data operational.