When performing an inventory summary operation via the /inventory/search/summary API endpoint for Place-Based OOH/DOOH inventory with a target geography set to DMA wide or Global scope returned reach and frequency were null. This has been corrected.
Remove visibility of 2023 data product from visibility of all endpoints
Aggregate reach was reported incorrectly in scenarios where an unusually large number of impressions are generated by out-of-market traffic in proportion to impressions by people domiciled in the target market. This could cause an aggregate reach to be returned that was less than the reach of the highest spot in the aggregated group. This has been corrected to ensure in all scenarios aggregated reach for groups of roadside spots are consistent with the reach of individual spots in the group.
v2.1 Schema update to maintain internal compatibility between v2.1 and v2.2 API Code
Three place-based data fields were added to the v2.1 database schema to maintain compatibility with the v2.2 API source code. This change only affected Geopath internal code and processes.
Reach and Frequency returned incorrect values at venues with multiple identical inventory records
https://geopath.atlassian.net/browse/GPAPI-491 Previously, users were observing unusually large frequency measures and unusually low reach measures when accessing aggregate measures via the /inventory/search/summary and the /inventory/plans API endpoints for Place-Based OOH/DOOH inventory installed at venues with multiple identical inventory records. Geopath has updated this API endpoint to return the correct values.
Reach and Frequency returned null or zero values when using a specific API endpoint
https://geopath.atlassian.net/browse/GPAPI-493 Previously, the API v2.1 /inventory/measures/summary endpoint would incorrectly return null values for the freq_avg, eff_freq_avg, eff_reach_net and eff_reach_pct fields as well as zero values for the reach_pct and reach_net fields. Geopath has updated this API endpoint to return the correct values.
The Market Plan endpoint is accepting null fields in a request as opposed to ignoring them, resulting in issues with the response given.
Place-based R/F still based on the entire market, not just venue inventory is located within.
This release was cancelled. Fixes moved to 2021-10-30
Default segment set in database per forecast. Previously the default segment that returns when no segment is provided was hardcoded. It will now be set in the database on a forecast basis.https://geopath.atlassian.net/browse/GPAPI-325
Additional hourly audiences made available. The 4 core audiences using Transport Foundry data that excludes group quarters populations will now be available when requesting hourly measures. https://geopath.atlassian.net/browse/GPAPI-311