Known Issues in Geopath API
This page provides a summary of known issues with the current Geopath API v2.2.14 serving data in the PRODUCTION environment (api.geopath.org).
For any API user that is observing unexpected results, please email geekout@geopath.org, along with expected results, actual results, steps to reproduce, URLs used, and additional business context.
Known issues in Geopath’s API (current API version in PRODUCTION is v2.2.14):
Summary of Issue Observed | Status & Root Cause(s) | Guidance to Members |
|---|---|---|
Reach/Frequency estimates for aggregations using more than 30,000 spots may show different outputs for each request (GPPIS-6095) | Under investigation by Geopath API team (NO ETA AVAILABLE YET) | Any aggregations performed via inventory/search/summary for 30K+ unique spots that require reach/frequency metrics should be escalated to Geopath |
Some Market Plans using multiple media type groups may show incorrect aggregate reach estimates when multiple media classifications are used (GPPIS-5971) | Under investigation by Geopath API team (NO ETA AVAILABLE YET) | Do not run Market Plans with multiple media type groups until further API updates are made to the Market Plan function |
Market Plans using multiple media type groups show incorrect aggregate reach estimates when users manually specify counts of spots for each media type group (GPPIS-5968) | Under investigation by Geopath API team (NO ETA AVAILABLE YET) | Do not run Market Plans with multiple media type groups until further API updates are made to the Market Plan function |
Retrieving some large inventory plans (via the inventory/measures/summary endpoint) may not return data for some markets (GPPIS-6070, GPPIS-6040) | Under investigation by Geopath API team (NO ETA AVAILABLE YET) | Report any observed misalignments to Geopath (this symptom does not occur in all situations) |
Retrieving some Market Plans for place-based and fleet inventory without any operator name constraint may not yield any results (GPPIS-6080) | Under investigation by Snowflake (NO ETA AVAILABLE YET) | Report any observed misalignments to Geopath (this symptom does not occur in all situations) |
Processing named searches via inventory/search/named for NYC DMA (DMA501) may not yield any results (GPPIS-6087) | Under investigation by Snowflake (NO ETA AVAILABLE YET) | Report any observed misalignments to Geopath (this symptom does not occur in all situations) |
Some Market Plans using combined markets (i.e. combined target audience geographies in a single plan) may not allow users to add all available spots when using both multiple audience geographies and multiple inventory location geographies (GPPIS-5974) | API logic for complex market plans requires further improvements | WORKS AS DESIGNED (all spots used in market plan outputs must have nonzero contributions from each of the selected target geographies; will consider long-term enhancement later in 2H25+) |
Market Plans using multiple media type groups will declare that the goal cannot be met when only one of the media type groups cannot meet the goal (GPPIS-5952) | API logic for complex market plans requires further improvements | WORKS AS DESIGNED (each media type group is provisioned an even ‘fraction’ of the declared goal by default; users can override the count of spots to be used in each media type group; Geopath will consider as a long-term enhancement later in 2H25+) |