pushio_config.json(Distribution) in your project.
-all_loadlinker flags to the Other Linker Flags section in Xcode - this is necessary or your application won't target the CoreLocation frameworks properly:
Once these steps have been taken, add the necessary code in your project to enable PushIOManager to begin tracking location.
NOTE: PushIOManager's location tracking uses Apple's Significant Change functionality by default.
 Import the location manager in your
#import <PushIOManager/PushIOManager.h> statement can be deleted, as the location header file also contains code from the basic PushIOManager (hence PushIOManager+PushIOLocation.h).
 On the
@interface line in
AppDelegate.h, target the PushIOManagerLocationDelegate. This can replace the basic PushIOManagerDelegate, as this delegate will handle those tasks as well:
 In the
AppDelegate.m file, tell the application to begin tracking location on start-up (
Tip: The top portion of your
AppDelegate.m file should look something like this:
 Mandatory: Add one of two lines to your
Info.plist for necessary Location support, depending on the use-case of your application:
This concludes basic setup for location-based push notifications. On first start-up, your device should ask if you would like to enable location services for your application.
Responsys takes the longitude and latitude info sent by the mobile app and, using the GeoNames database, converts them into human-readable location attributes. These attributes are stored in the App Channel List in the fields
ADMIN_AREA2_. A marketer using Responsys creates filters using the location attributes in the App Channel List, and then uses those filters to define the audience for their campaign.
For more information about the App Channel List, see the Mobile App Channel Configuration Guide.