/
User Acceptance Testing (UAT) Status

User Acceptance Testing (UAT) Status

Owned by Chris Luken
Last updated: Apr 26, 2025
4 min read

This page provides an externally-facing summary of the current status of reported issues with the forthcoming 2025 annual dataset validation activities in STAGING as well as API/UI issues in both STAGING and PRODUCTION environments. The intended audience of this page are the members of the GEOPATH ANNUAL DATASET WORKING GROUP who are participating in User Acceptance Testing (UAT) activities.


UAT group: Please send all ‘new’ bugs to geekout@geopath.org, along with expected results, actual results, steps to reproduce, environment/URLs used, and additional business context.

 

PLEASE NOTE:

  • All market plans have a 1500 spot ‘cap’; Geopath cannot support market plans that exceed 1,500 spots

  • All inventory plans have a 15,000 spot ‘cap’; Geopath cannot support inventory plans over 15,000 spots

  • All spot-level CSV exports from the ‘Explore’ table view in the Insights Suite are limited to 15,000 spots

  • Summaries of changes in each API release can be seen on the Version 2.2 Release Notes page

 

Announcements (environment-wide updates):

  • Latest API release (2.2.12) deployed to PRODUCTION at 10pm ET on Friday, 9/13/24

  • Latest 2025 dataset update deployed to STAGING at 4:30pm ET on Friday, 4/25/25

  • Final 2024 dataset update released to PRODUCTION at 8pm ET on Friday, 4/11/25

  • Latest UI enhancements deployed to STAGING at 9am ET on Friday, 4/25/25

     

 

Reported issues for 20250501 Annual Dataset in STAGING and API/UI in STAGING or PRODUCTION:

Summary of Issue Observed

Status and Root Cause Summary

Next Step for UAT group (in STAGING)

Summary of Issue Observed

Status and Root Cause Summary

Next Step for UAT group (in STAGING)

Market Plans that use more than 20 unique media type groups will fail (GPPIS-5969)

Works as designed; API logic constraint is enforced due to performance limitations. Geopath will consider enhancing later.

WORK AROUND THE ISSUE WITH SMALLER MARKET PLANS AND RE-TEST (Geopath may enhance logic in 2H25+)

Some place-based spots may show missing or incorrect reach/frequency & impression estimates using the latest annual dataset

Underlying audience measurement data for a handful of places was aggregated incorrectly or absent from the initial data processing scope; Geopath has reprocessed and validated place-based outputs in the latest annual dataset

ISSUE RESOLVED; PLEASE RE-TEST

 

Known issues for 20250501 Annual Dataset in STAGING and API/UI in STAGING or PRODUCTION:

Summary of Issue Observed

Status and Root Cause Summary

Next Step for UAT group (in STAGING)

Summary of Issue Observed

Status and Root Cause Summary

Next Step for UAT group (in STAGING)

'ZCTA' prefix shown for 'top contributing postal codes' area of the spot summary screen in UI (GIS-487)

API serves ZIP-level home origin data with a ZCTA prefix for 2025 data product, which was not initially handled in the UI

ISSUE RESOLVED; PLEASE RE-TEST

“Opportunity Overview” section of the Inventory Detail Plan screen shows ‘N/A’ for any spot in the latest annual dataset

Only the 4 ‘core’ target audiences of P0+, P5+, P18+, P21+ are currently testable; additional data production will occur for all 700+ possible target audiences after integration of final Bentley data patch

NO ACTION REQUIRED YET (ETA 5/2)

Some inventory units do not show thumbnail images as expected (GPPIS-5986)

Content delivery network (CDN) infrastructure may not render certain images at certain dimensions

NO ACTION REQUIRED YET (ETA TBD - likely May)

Some named search requests may generate malformed JSON outputs (GPPIS-5951)

JSON output rendering defects may occur in rare cases when accessing specific inventory metadata for some queries

NO ACTION REQUIRED YET (ETA TBD - possibly May, likely 2H25)

Some Market Plans 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

NO ACTION REQUIRED YET (ETA TBD - possibly May); UAT USERS ARE ENCOURAGED TO RUN SIMPLIFIED MARKET PLANS AS A WORKAROUND

Some Market Plans using multiple media type groups may show incorrect aggregate reach estimates when multiple media classifications are used (GPPIS-5971)

API logic for complex market plans requires further improvements

NO ACTION REQUIRED YET (ETA TBD - possibly May); UAT USERS ARE ENCOURAGED TO RUN SIMPLIFIED MARKET PLANS AS A WORKAROUND

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)

API logic for complex market plans requires further improvements

NO ACTION REQUIRED YET (ETA TBD - possibly May); UAT USERS ARE ENCOURAGED TO RUN SIMPLIFIED MARKET PLANS AS A WORKAROUND

Market Plans using multiple operators/divisions in a single media type group show inconsistent results between operator/division-level reach and media type group reach (GPPIS-5967)

API logic for complex market plans requires further improvements

NO ACTION REQUIRED YET (ETA TBD - possibly May); UAT USERS ARE ENCOURAGED TO RUN SIMPLIFIED MARKET PLANS AS A WORKAROUND

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

NO ACTION REQUIRED YET (ETA TBD - possibly May); UAT USERS ARE ENCOURAGED TO RUN SIMPLIFIED MARKET PLANS AS A WORKAROUND

Related content