Phunware Data Release Notes - January 2020

Phunware Data Exchange - Audience Builder

The January 2020 release of the Phunware Data Exchange focused on incorporating valuable product feedback from our customers. This feedback was captured through our product listening feedback portal. The release included both enhancements and bug fixes to the Audience Builder feature.


This release delivered enhancements for building location-based audiences using polygons and refining the user experience.

Location audiences using polygons:

  • Map for polygons - when selecting to build a geography-based audience with polygons, the design surface now renders a larger, full-screen map for configuring custom polygons. This improves the user experience when the audience design requires the configuration of multiple polygons.
  • Intraday time windows - deriving an audience from a temporal event that happens between specific hours of a day is a valuable use case we have seen over the last few years. In addition to the calendar day, the audience builder now enables hour resolution for the start and end date/time for deriving the audience. For example, this is relevant for deriving an audience from people who visited a geographical region within a specific time window during a specific day.
  • Time windows for each polygon - for an audience design with more than one polygon, a start date/time and end date/time can be configured for each polygon. This enables a single audience to be derived from multiple polygons, each with their requirements.
  • Default lookback windows - default windows of 30/60/90 days were added as the time horizon to "look back" for mobile devices with location activity within this window.
  • User Time Zone - to ensure clarity of the time window, the time zone of the user was added to the date/time range dialog.
  • Polygon naming - the default name assigned to a polygon on creation, can be updated to a descriptive name to improve usability. This is especially handy when you have multiple polygons in an audience design.
  • Polygon configuration panel - a new polygons panel was added to the user experience to visually present the polygon configuration for the entire audience. This makes it very easy to edit polygon information such as the name, date/time range and remove polygons.
  • Polygon highlight - when the map included multiple polygons, it was not easy to understand which polygon configuration corresponded to a polygon on the map. To address this feedback, a polygon surface is rendered a darker blue when a polygon configuration is selected in the new polygon configuration panel.

Audiences summary view:

  • The audience landing page was simplified by removing the audience configuration details to improve usability. The audience configuration details such as segments and boolean logic operations were moved to the audience detail view.

Audience detail view:

  • Audience export to a file - our customers have scenarios where they want the ability to manually upload audiences to the advertising platform of their choice. We extended the audience export feature to now include the download of an audience to a local file. The CSV file is a list of mobile advertising ID's that can then be uploaded to the advertising platform for targeting criteria.
  • Audience design configuration - the segments and boolean logic are now available on the top of the audience detail view.
  • Download of audience usage - the "Download CSV" text was moved to the top right of the table that displays the daily audience usage (impressions, unique devices, the amount paid).

Data transparency label

  • The "Audience Count" - the size of unique devices in the audience segment - is now updated daily.

Bug Fixes