Show Menu
TOPICS×

Frequently asked questions

Here is some information and frequently asked questions about Location Service.

Size and reliability

Important to note for all geofences being used in region monitoring from a mobile app regardless of using Adobe or some other service. The Operating systems recommend some parameters to keep in mind when creating geofences. For maximum reliability, geofences should have a radius of at least 100 meters. It is okay to create smaller geofences, but entry and exit events may not be generated, or may be generated after the user stops moving for a period.
In addition, accuracy and reliability may be reduced based on hardware conditions such as wi-fi being turned off or unavailable, and also based on the device's location in relation to hampering GPS signals. For example, mountainous areas, urban settings, and indoor areas can reduce location accuracy from the iOS and Android operating systems.

How does an exit event trigger?

When the Places Monitor (SDK) gets a new list of nearby POIs, it registers a region with the operating system for each POI. The operating system is now responsible for notifying the SDK when the device crosses a boundary (entry or exit) for one of the monitored regions. The SDK only triggers an exit event when the operating system notifies the SDK that the event has occurred. The main reason for this notification is the time sensitivity of the location data.
If the operating system cannot deliver an exit event when the device leaves a region, it is safer for the SDK to just omit the exit event. If the SDK manufactures an exit event without the event being triggered by the operating system, there is a risk that the exit event might be processed well outside the time period during which the device was near the POI.

Adding a user to Location Service and Experience Platform Launch

To allow users to access the Launch Service UI , they need to be added to Places Core Service in the Admin Console as a user. To allow users to have access to Experience Platform Launch, configure mobile properties, and use Places with the Adobe Experience Platform SDK, they need to be added to Experience Platform Launch in the Admin Console and be given the following permissions for Experience Platform Launch:
  • All Property Rights:
    • Develop
    • Approve
    • Publish
    • Manage extensions
    • Manage environments
  • Manage Properties permission under Company Rights
If this is the first time you are adding a user, complete the following steps to add users to Experience Platform Launch and Location Service. If you have added users before, multiple profiles might be displayed, so ensure that you select the correct profile.
Only org administrators can access the Admin Console and add the users.

1. Verify that Location Service and Experience Platform Launch are provisioned

To verify that Location Service and Experience Platform Launch are provisioned:
  1. Log in to your Experience Cloud organization.
  2. In the top-right side, click the Experience Cloud shell switcher.
  3. Under Platform , click Administration .
    If you do not see Administration in the list, you are not an admin. You must contact your org admin to complete this procedure.
  4. In the Experience Cloud Administration page, on the Admin Console card, click Take me there .
  5. In the Admin Console, if you have access to several organizations, verify that the correct organization is selected in the top right side of the page.
    This is the organization to which you will add your users. If the correct org has not been selected, click on the org and select the org from the drop-down list.
    If you do not have access to an organization, it means that you do not have admin access to that organization.
  6. Verify that the cards for Adobe Experience Platform Launch and Places Core Services are displayed.
    If they are displayed, Location Service and Experience Platform Launch have been provisioned for your organization. If they are not displayed, they need to be provisioned for your organization.
    During the Beta period, after you complete the Beta survey , the request is made to the Provisioning team.

2. Set up the profile and add the permissions

To set up the profile and add the permissions:
  1. Set up a Experience Platform Launch profile, which allows the users who were added to the profile, use Experience Platform Launch and its mobile properties with the Experience Platform SDK.
    a. In the menu bar, click Product .
    b. In the left pane, in the list of products, click Adobe Experience Platform Launch .
    • The Experience Platform Launch profile(s) appear on the right.
    • Experience Platform Launch has a default profile called Launch - (org name) .
      If you previously added users to Experience Platform Launch, you might see multiple profiles listed.
  2. Select the correct profile:
    a. Click on the name of the default profile.
    b. Click the Permissions tab.
    c. Click Edit next to Property Rights .
    d. In the left pane, click + Add all .
    This step moves all of the available permissions to the included permissions list.
    e. Click Company Rights .
    f. In the left pane, click + Manage Properties .
    g. Click Save .
For Location Service, there is a default profile, but you do not have to add any permissions.
You have successfully added permissions to the profile that you created.

3. Add a user or a developer to your Location Service and Experience Platform Launch profiles

You can add a user and/or a developer to your Location Service and Experience Platform Launch profiles.

Add a user

To add a user to your Location Service and Experience Platform Launch profiles:
  1. Add a user to the Experience Platform Launch profile.
    a. In the menu bar, click Overview .
    b. On the Adobe Experience Platform Launch card, verify the following:
    • Two dots are displayed at the bottom of the card.
    • The dot on the left is black.
      If the dot on the right side is black, you can only add developers. To add a user, click the dot on the left.
    c. Click + Add Users .
    d. Enter the user’s Adobe ID.
    e. Complete one of the following steps:
    • If you are adding a new user, click New user , and enter the user’s first and last name.
    • If you are adding an existing user, click the user’s name that is displayed.
    f. In the Please select a profile for this product drop-down list, select the profile that you edited earlier.
    g. Click Save .
  2. Add a user to Places Core Services .
    Currently, all Location Service users have the same permissions, so you do not need to edit the permissions.
    a. On the Places Core Services card, verify the following:
    • Two dots are displayed at the bottom of the card.
    • The dot on the left is black.
    b. Click + Assign Users .
    c. Enter the user’s Adobe ID.
    d. Complete one of the following steps:
    • If you are adding a new user, click New user , and enter the user’s first and last name.
    • If you are adding an existing user, click the user’s name that is displayed.
    e. In the Please select a profile for this product drop-down list, select the Places profile.
    f. Click Save .

Add a developer

For users who also need access to the Web Service API, you need to add them as a Developer.
To add a developer:
  1. On the Places Core Services card, verify the following:
    • Two dots are displayed at the bottom of the card.
    • Click the dot on the right so Assign Developers appears at the bottom of the card.
  2. Click + Assign Developers .
  3. Enter the user’s Adobe ID.
  4. Complete one of the following steps:
    • If you are adding a new user, click New user and enter the user’s first and last name.
    • If you are adding an existing user, click the user’s name that is displayed.
  5. In the Please select a profile for this product drop-down list, select the Location Service profile.
  6. Click Save .
Users receive an email that notifies them that they have access to Experience Platform Launch. They can can log in to the Experience Platform Launch or the Places UIs for this organization. If you complete step 4 in the Add a developer procedure, the user can also log in to the Adobe I/O console to create a Places integration and use the Places REST API.