Skip to main content

Location Notifications

Send automatic notifications when members are near your business.

Matt Thomas avatar
Written by Matt Thomas
Updated this week

Location notifications use geofencing to automatically display a message on your members' lock screens when they are near one of your business locations. Navigate to Engage > Location Notifications to set up and manage your locations.


How Geofencing Works

Apple Wallet and Google Wallet both support location-based notifications. When a member with your wallet pass installed enters the geographic area around one of your configured locations, their device automatically displays a notification on the lock screen. This happens without requiring the member to open any app — the wallet pass itself triggers the notification based on proximity.


Adding a Location

Click Add Location and configure the following details:

  • Name — A friendly name for the location (e.g., "Downtown Store" or "Main Street Cafe").

  • Address — Search for the address using the built-in Google Maps search. The address will be geocoded automatically.

  • Latitude / Longitude — Automatically populated from the address search, but can be adjusted manually for precision.

  • Radius — The geofence radius in meters. This determines how close a member needs to be before the notification triggers. A smaller radius is more precise; a larger radius catches members in a wider area.


Notification Message

Each location has its own notification message. This is the text that appears on the member's lock screen when they enter the geofence. Write something relevant and actionable — for example, "Welcome back! Show your pass for today's special." or "You're near our shop — stop in for 10% off!"


Audience Targeting

You can target location notifications to specific member segments using the same filters available across Pocket — wallet status, tags, tier, RFM segments, and custom properties. This lets you deliver different messages to different groups of members based on their profile.


Enabling and Disabling Locations

Each location can be individually enabled or disabled. Disabled locations will not trigger any notifications, even if a member is within the geofence radius. This is useful for temporarily pausing notifications at a location without deleting the configuration.


Triggered Count Statistics

Each location displays a triggered count showing how many times the geofence notification has been activated. Use this metric to understand foot traffic patterns and the effectiveness of your location-based messaging.


Managing Predefined Locations

In addition to the Engage section, you can also manage your business locations from Settings > Locations. Locations defined in Settings are available as predefined options when creating location notifications, making it easy to reuse your business addresses across features.


Important Notes

  • Geofencing accuracy depends on the member's device operating system, hardware, and environmental factors. Results may vary between devices and locations.

  • Apple Wallet supports up to 10 relevant locations per pass. Google Wallet also has location limits. Plan your locations accordingly.

  • Notifications are triggered by the device OS, not by Pocket directly. There may be slight delays depending on device settings and battery optimization.


Tips

  • Keep notification messages short, relevant, and actionable — members see these on their lock screen with limited space.

  • Use a radius that matches your location type. A small shop might use 100-200 meters, while a large venue might use 500 meters or more.

  • Test your geofences by visiting the location with a test wallet pass installed.

  • Combine location notifications with audience targeting to deliver personalized messages — for example, show a special welcome message to VIP-tier members.

  • Monitor triggered counts to identify your highest-traffic locations and optimize messaging accordingly.

  • Visit your Location Notifications dashboard to manage all your geofence configurations.

Did this answer your question?