Push Notifications with Places Service

Last update: 2022-10-19
  • Topics:
  • Places
    View more on this topic

In this section, you will learn how to use historical geo-location information to target push notifications that are delivered through Adobe Campaign Standard.


Before you begin, complete the following tasks:

Create data elements in Experience Platform Launch

After verifying that the Places extension and a region monitoring solution (CoreLocation documentation for iOS, or Android location documentation) are working correctly in your application, you need to create data elements in Experience Platform Launch. Data elements allow you to read the information that was provided by the extensions coming through the Mobile SDK event hub and act as an alias to retrieve data from the client application. To retrieve data from the Places extensions and send the Places Service information to Campaign, you need to create a few data elements.

To create a data element:

  1. In your Experience Platform Launch mobile property, click the Data Elements tab and click Add Data Element.

  2. In the Extension drop-down list, select Places Service.

  3. From the Data Element Type drop-down list, select Name.

  4. In the right-hand side pane, you can select Current POI which retrieves the name of the POI in which the user is currently located.

    Last Entered retrieves the name of the POI that user last entered, and Last Exited provides the name of the POI that the user last left. In this example, we selected Last Entered and typed a name for the data element, such as Last Entered POI Name and clicked Save.

    "Push messaging in Campaign Standard"

  5. Repeat the steps 1-4 above and create data elements for Last Entered POI Latitude, Last Entered POI Longitude, and Last Entered POI Radius.

In addition to the data elements for Places Service, ensure that you create Mobile Core data elements for App ID and Experience Cloud ID.

Create a rule to send location data to Adobe Campaign Standard

Rules in Experience Platform Launch allow you to create complex, multi-solution workflows based on event triggers. With rules, you can create new rules or modify existing ones and have the updates dynamically deployed to your mobile applications. In the following example, the rule will be triggered when a user enters a geo-fenced POI. After the rule is triggered, an update is sent to Campaign Standard to record an entry to a specific POI for a particular user based on the Experience Cloud ID.

  1. In your Experience Platform Launch mobile property, on the Rules tab, click Add Rule.

  2. Under the Events section, click + and select Places Service as the extension.

  3. For the Event Type, select Enter POI.

  4. Name the rule, for example, User entered POI.

  5. Click Keep Changes.

  6. Leave the Conditions section blank.

    This section allows you to filter or place restrictions on when this rule should fire.

  7. Under the Actions section, click +.

  8. In the Extension drop-down list, select Mobile Core and in the Action Type drop-down list, select Send Postback.

  9. In URL, you need to construct your Campaign Standard locations endpoint.

    The URL should look similar to https:///rest/head/mobileAppV5//locations/.
    Ensure that you use the correct data elements that you created previously for your Campaign server and pKey.

  10. Click the box to add a post body and send the following:

     "locationData": {
     "distances": "{%%Last Entered POI Radius%%}",
     "poiLabel": "{%%Last Entered POI Name%%}",
     "latitude": "{%%Last Entered POI Lat%%}",
     "longitude": "{%%Last Entered POI Long%%}",
     "appId": "{%%AppID%%}",
     "marketingCloudId": “{%%ecid%%}”
  11. Ensure that you use data elements that you created in the previous section.

  12. In Content Type, type application/json.

  13. Click Keep Changes.

  • It might be helpful to have a Slack web hook set up as an additional action to validate that entries are being triggered and that the right data is being collected.
  • Remember to publish the recent changes to your app to make sure the rule and all of your data elements are deployed as part of your configuration. After you publish, launch the mobile application again to get the latest configuration updates.

Use location data to target Campaign Messages

Now that we have location data populated in Campaign, we can use POIs as an audience segment tool.

  1. In your Adobe Campaign Standard instance, click Create Push Notification.

  2. For the push notification type, select Send push to Campaign profiles.

  3. Click Next and type the general details.

  4. On the Audience screen, click Count to determine to how many estimated users the push notification will be sent.


    In this example, the count will be 3, because there are three installed devices on which the application is being tested.

  5. In the left pane, expand the Profile tab and drag the POI location filter to the main area.

  6. In the POI filter window, enter the exact name of the POI that you want to target.


    You can make additional selections to determine the period of time since the user’s previous visit to this POI.

    "Push messaging 2 in ACS"

  7. Click Confirm.

  8. Run the count again at the top to see your audience size change.

    If you do not see your count update, you might have entered a POI name for which no devices have triggered an entry. Having the Slack web hook becomes valuable in this situation, because you can see a listing of POI entries from various test devices.

  9. You can drag out additional POI location filters to include multiple POIs in your message.

  10. Click Next to finish creating the push notification for delivery.

    "Push messaging 3 in ACS"

Using Places Service with Adobe Campaign Standard gives you a powerful tool to segment and target your messaging to users based on geo-fence entries and exits. This integration helps you build more personalized and contextual use cases.

On this page