{% hint style="warning" %} This content has permanently moved to https://docs.adobe.com/content/help/en/places/using/release-notes.html, so that it can be in the same documentation system as other Adobe Experience Cloud content and be automatically translated into several languages.
Please update your bookmarks. {% endhint %}
Places UI Update
- Added a new list view that shows POIs without the map.
- Added POI filtering options for the city, the state, the country, and the metadata.
- The first library in an organization is automatically created.
- Added POI sorting to the List View.
- Moved the list and details panel to right side of UI.
- Added a new search panel to the top of the UI.
- If only one library is present, this library is automatically selected when you create a POI.
- Moved library management into a popup window.
- Added a POI count next to the filters.
Places Monitor Launch Extension 2.0.0
- Updated the Android and iOS installation instructions for the Places Monitor 2.0.
Places Monitor 2.0.0
- Monitoring status is now persisted between launches.
- The handling of the callback, which resulted from a location permission request no longer requires you to extend PlacesActivity.
- Changed an existing API, allowing developers to clear all Places data from the device :
- Old API:
public static void stop();
- New API:
public static void stop(final boolean clearData);
- Old API:
- Updated the use of the Places
getNearbyPointsOfInterest
API to handle error scenarios more effectively.
The following updates were made in this release:
ACPPlacesMonitor 2.0.0
-
To clear all Places data from the device,
in ACPPlacesMonitor, replaced an existing API (
+ (void) stop;
) with+ (void) stop: (BOOL) clearData;
. -
Updated the use of the ACPPlaces
getNearbyPointsOfInterest
API to handle error scenarios more effectively.
Android Places 1.3.0
- Added a new API that clears out all Places-related data from shared state, in-app memory, and Shared Preference.
- Fixed an issue where shared state was not getting updated during application start.
- Fixed a bug where
getNearbyPointsOfInterest
callback was returning error code SERVER_RESPONSE_ERROR instead of CONNECTIVITY_ERROR on no internet. getNearbyPointsOfInterest
API (without the errorCallback) will have thesuccessCallback
called with empty poi list, in case of error retrieving the nearby points of interest.
The following updates were made in this release:
iOS Places 1.2.0
- Added a new API that clears out all Places-related data from shared state, in-app memory, and NSUserDefaults.
The following updates were made in this release:
iOS Places Monitor 1.0.2
- Quality of life improvements, including better in-code documentation and logging.
The following updates were made in this release:
iOS Places 1.1.0
- Added a new API to return an error code when there is a failure retrieving nearby places.
- When privacy status changes to opt-out, all Places-related data will now be wiped from the device.
- Fixed an issue that, after a first launch, sometimes caused Places events to be lost due to bad network conditions.
- Fixed an issue where, when processing POI entry events in quick succession, token replacement via Rules Engine sometimes reference the incorrect POI.
Fixed the following issues in the Places UI:
- Updated the Solution Switcher in Places to align with the rest of the Experience Cloud.
- Fixed an issue where rank was saving in instances where no rank changes were made.
- Increased the minimum allowed radius in the UI to 10 meters.
- Fixed an issue where, if you delete all the numbers in the field, the radius field reset back to 20 meters.
This is the first release of Places, a set of tools that allows customers to enrich their users' experiences with real world location data. For the first release, our primary use case is to enable mobile apps to retrieve custom location data and act on that data through Experience Platform Launch.
Here are the key features in this release:
We have released a management UI where you can view and manage your points of interest (POIs). You also can organize your POIs into libraries. In addition to standard metadata such as city, state, and category, we also support the ability to add custom metadata to your POIs.
- To see the Places UI, go to https://places.adobe.com.
- To get started with the Places UI, see Getting Started.
Using the Places Extension, you can add your Places libraries to your mobile app and act on their POIs. Using the rule builder in Experience Platform Launch, you can trigger actions to fire when users enter and exit POIs.
In the Places extension:
- You can choose which POI libraries to include on your app.
- Rule events that trigger on POI entry or exit.
- Create data elements that point to the user's current POI.
For more information about the Places extension, see Places extension.
You can use the Places APIs do do the following:
- Allow developers to populate and update their list of POIs.
- Build your own UI or integrate with an existing POI database.
- Use the Places API
batch
endpoints to do a bulk import of POIs. A python utility is provided with the APIs.
For more information about the Places APIs, see API usage.
The Analytics Launch extension is being updated to automatically add location context data from your Places database to all outgoing Analytics calls when a user is within a POI (Passive calls). This update will also allow rule creation to fire Analytics track calls directly at POI entry or exit (Active calls).