v2.1 2023-01-25

Change Summary

• Summarizing placed based media at DMA or global scope returns null reach and frequency

• Remove visibility of 2023 data product from visibility of all endpoints

  GPAPI-619 Remove 2023 data product visibility from v2.1 API endpoints

  The 2023 data product is not supported by the v2.1 API and will no longer be visible through any v2.1 API endpoint.

v2.1 2022-08-29

Bug Fixes

• Aggregate Reach for Packages & Groups of Spots Calculated Incorrectly in Specific Scenarios

  GPAPI-524 Reach Aggregate Calculation Error

  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

  GPAPI-526 Add place based data fields for v2.2 compatibility

  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.

v2.1 2022-08-05

Bug Fixes

• Reach and Frequency returned incorrect values at venues with multiple identical inventory records

• Reach and Frequency returned null or zero values when using a specific API endpoint

v2.1 2021-12-09

Bug Fixes

• The Market Plan endpoint is accepting null fields in a request as opposed to ignoring them, resulting in issues with the response given. 

v2.1 2021-10-28

Bug Fixes

• Inventory/Search having certain issues with plant/operator spot and frame ids that had mixed cases GPAPI-349: inventory/search - ignore case for plant_frame_id and plant_spot_idDone

• R/F for place based locations will now be capped at the individual place level to prevent duplication from multiple inventory that are reaching the same audience. GPAPI-298: Calculate population ceiling for placesDone

  • Place-based R/F still based on the entire market, not just venue inventory is located within.

v2.1 2021-10-14

• This release was cancelled. Fixes moved to 2021-10-30

v2.1 2021-09-16

New Features

• 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.GPAPI-325: Default base segmentDone

• Proactive efficiencies introduced into tables used by the measures calculation process. GPAPI-308: Update gp_frame_circulations_by_census_tracts_b_ranked tableDone

• 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. GPAPI-311: Enable additional hourly audiences Done

Bug Fixes

• Default base audience was not matching the target segment provided in the /measures/summary(aka custom calc) endpoint. GPAPI-342: Custom Calc endpoint support of default base audiencesDone

• Summary Measures returning differently when using a target_segment_list in the request. GPAPI-285: Measures changing with Multiple AudiencesDone

• Summary Measures R/F returning differently based on summary level used. GPAPI-326: search/summary - reach and frequency issue - ceiling population vs summary levelDone

• Spots not being displayed for some inventory in the API documentation portal. GPAPI-300: Spots not displaying in documentation site endpointDone

Associated Non API Changes

• Reach & Frequency issues for periods longer than 84 days in the /measures/summary endpoint were hot fixed with notification on 8/28 GPAPI-343: Custom Calc returning different R/F than inventory searchDone

v2.1 2021-09-02

New Features

• Added ability to search by different representation types GPAPI-261: Enable search by different representation typesDone

• Added better sorting on the market search endpoint to sort by type of market and the market id GPAPI-272: Deterministic sort on market searchDone

• Added additional "open_date" field to better support future place based needs GPAPI-295: Add open date field into APIDone

• Additional error codes to better understand when failures are DB errors or DB timeouts https://geopath.atlassian.net/browse/GPAPI-306

• Additional access control headers added to responses when request errors happen to better accommodate user application error handling https://geopath.atlassian.net/browse/GPAPI-302

• Changes to how the fieldset parameter is used in the measures/summary endpoint to match other endpoints. https://geopath.atlassian.net/browse/GPAPI-210

Bug Fixes

• Error that was preventing certain string based operator IDs from being used in /search endpoints https://geopath.atlassian.net/browse/GPAPI-297

• Error that was showing more spots than requested when measures were not being requested https://geopath.atlassian.net/browse/GPAPI-303

• Error where non active operator records were being included in operator searches https://geopath.atlassian.net/browse/GPAPI-232

Associated Non API Changes

• Backend DB timeout better matches API timeout. https://geopath.atlassian.net/browse/GPAPI-309