> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-animation/guides-animation.md).
# Engage and Animation Guides
Turn every pass into an active touchpoint: reward loyalty, surface timely offers, and reach customers exactly when it matters.
## Animation & engagement: step by step
Cover image
:location-crosshairs:
Geolocated notifications
Show a contextual message near a location when a customer is nearby for reminders, on-site information, or store/venue alerts.
**Privileges and activations turn a static pass into a living engagement tool.** A privilege is a benefit attached to an individual pass — a discount, a free item, an unlockable reward, a stamp counter — that can be added, updated, or removed at any time without reissuing the pass. Four behavior types cover virtually every loyalty or campaign scenario: OneTime (redeem once), Unlimited (always available while valid), MultiUse (a limited number of uses), and Unlockable (revealed once a condition or progress threshold is met). Each pass can carry up to five privileges at once, with priority rules resolving any conflicts automatically.
**Privileges can come from anywhere in the stack.** They're generated internally by activations, pushed externally through marketing connectors like Salesforce Marketing Cloud or Bloomreach, or created and updated directly via the API. Every privilege carries its own appearance (image, colors), content (title, description), call-to-action links, and a movement-based value history — making it easy to track balances, progress, or redemption codes over time. From event tickets with unlockable afterparty access, to loyalty cards with tiered discounts, gift cards with redeemable balances, and membership passes with monthly quotas, privileges adapt to any real-world use case while keeping the core pass untouched.
**Push notifications complete the engagement loop**, with native, real-time delivery on both Apple Wallet and Google Wallet. Apple notifications are tied to pass updates and appear directly on the lock screen with full message content; Google Wallet offers more flexible, on-demand messaging — including clickable links and rich "Value-Added" content blocks — within a 3-per-day limit. Notifications can be triggered by geolocation, scheduled dates, or events from connected systems (CRM, POS, ticketing), giving brands a single, unified way to keep customers informed and engaged directly from their wallet.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.thewalletcrew.io/guides-animation/guides-animation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
