Geolocated Notifications

Surface a pass message when a customer is near a configured store or venue, using the relevance locations stored on the pass.

Geolocated notifications show a contextual message near a location. Apple Wallet or Google Wallet can surface it when a customer is nearby. Use it for reminders (“don’t forget your card”) and on-site information (“gate changed”).

Check that the message reads clearly at a glance, since it appears on the lock screen.

This works for stores and any venue. Typical venue examples are stadiums, concert halls, theaters, and pop-ups.

Real-world examples

• Remind loyalty members to scan their card at checkout.

• Display a voucher reminder only if a voucher is available.

• Announce a store opening to customers near that location.

• Remind ticket holders of gate/door info when approaching the venue.

• Surface a “your ticket is ready” message near the venue entrance.

Geolocated notifications appear only if the customer enables location features for their wallet app.

On iOS: Settings → Privacy & Security → Location Services → Wallet.

On Android: check Google Wallet permissions in the device Settings (location must be allowed).

How it works

Wallet passes can store a small set of “relevance” locations. The phone compares the device position to those locations. When the customer enters the configured radius, the wallet app can surface the pass and its message.

The Wallet Crew configures these locations on the pass based on the brand's location dataset. Most brands use store addresses. For venues, the venue is usually modelled as a “store” record so it can be geolocated the same way.

What customers will see (varies by platform)

Apple Wallet (iOS)

iOS can surface a lock screen suggestion when the customer is near one of the configured locations. The suggestion can include the message configured on the template.

Google Wallet (Android)

Android can surface a “nearby pass” experience when the customer is near one of the configured locations. The exact UI depends on Android version and device manufacturer.

Limits to design for

These platform limits apply:

• Up to 10 GPS coordinates per pass.

• Up to 300 m radius per coordinate.

Message visibility is controlled by the OS. In practice, the message can remain visible while the customer stays in the area.

Geolocation vs “push notifications”

Geolocated notifications are not “sent” at a specific time by The Wallet Crew. They are triggered by the customer’s phone when it detects proximity.

For a server-triggered message, use standard wallet notifications instead. Start with Push notifications.

Prerequisites

Locations (addresses) must be configured in The Wallet Crew. The platform uses those addresses to compute GPS coordinates.

Locations are managed through the Stores dataset, which covers both retail stores and venues. Example: create a store entry for Stadium - Gate A or Concert hall - Main entrance.

When locations are not set up yet, start with Stores.

Addresses are used to compute GPS coordinates (stores or venues).

Set up the message in The Wallet Crew

Configure the message directly on the pass template. Use Liquid for personalization.

1

Open the notification settings on a template

Go to Templates. Open the template More options menu, then select Notifications.

2

Write the message (Geo notification tab)

Open the Geo notification tab. Write the message. Add Liquid variables if needed.

Keep it short. Aim for ≤ 140 characters to avoid truncation.

3

Configure translations (optional)

When the template is translated, update the geo notification message for each language.

4

Save and test

Click Send notification to save. Then test with a device near a configured location.

Validate both the location behavior and the Liquid rendering.

Geo notification messages are configured per template and can be translated.

How The Wallet Crew selects locations per customer

The location selection logic depends on the use case. Loyalty programs typically rely on “home store” logic. Event tickets typically rely on the venue location assigned to the pass.

For a retail-style setup, geolocated notifications are commonly computed for:

• The customer’s home store.

• The 9 closest locations to that home store (or to the customer address).

This keeps the pass within the 10-location limit while covering nearby locations.

Automatic updates of location coordinates

When a pass update is performed via The Wallet Crew, location coordinates can be recalculated:

• If the customer’s home store changes, the “closest locations” list is recalculated.

• If the customer address changes, the “closest locations” list is recalculated.

• When new stores are added (with an address), they can become eligible as “closest locations”.

This keeps location triggers aligned with the latest location data.

Liquid examples for geo notification messages

Use Liquid to show a message only to relevant customers. Typical inputs are store identifiers, customer profile data, and voucher availability.

Example 1 — show a voucher reminder only if a voucher exists

{%- if y2.bons.loyaltyCertificates.size > 0 -%}
Your €20 loyalty voucher is available. Use it in store today.
{%- else -%}
Don’t forget to scan your loyalty card at checkout.
{%- endif -%}

Example 2 — store-specific message

{%- if storeId == "013" -%}
This store is permanently closed. Visit our other nearby stores.
{%- else -%}
Welcome back. Your store is nearby. Come discover our latest arrivals.
{%- endif -%}

FAQ

Can we track how many customers received the geolocated message?

No. This is not a message that The Wallet Crew actively sends at a given time. The customer’s phone triggers it locally when it gets near the configured coordinates.

Do we know if the customer is inside the store or venue?

No. Geolocation triggers do not send “entered” or “in-store” events back to The Wallet Crew.

Why didn’t the geo notification show up on an iPhone?

Start with iOS settings. The customer must enable location access for Wallet in Settings → Privacy & Security → Location Services → Wallet.

Then validate the pass data. The pass must include location coordinates. The customer must be close enough to the configured radius.

Why didn’t the geo notification show up on Android (Google Wallet)?

Start with Android settings. The customer must allow location features for Google Wallet (and not restrict it via system privacy settings).

Then validate the pass data. The pass must include locations, and the customer must be close enough to trigger them.

What is the delay between two geolocated notifications?

The OS typically surfaces the message when the customer enters the configured area. It can disappear when they leave. It can reappear the next time they enter.

Apple’s reference: Showing a pass on the lock screen.

How are the 10 locations selected for one customer?

Each customer has a home store. The Wallet Crew selects the 9 closest locations to that home store, for a total of 10.

Is this the same as beacon-based notifications?

No. Beacons use Bluetooth (iBeacon identifiers). Geolocated notifications use GPS coordinates.

Apple Wallet also supports beacon triggers. Before using them, confirm the target devices and store hardware constraints.