> 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/engage-and-animate/privilege-and-activation/activation.md).

# Activation

An activation applies a privilege (and optionally a notification) to many passes. Use activations for campaigns and scheduled rollouts.

### What an activation contains

1. **Segmentation**: which passes are targeted.
2. **Trigger**: when the activation runs.
3. **Configuration**: what is applied (privilege + optional notification).

### How it differs from a Privilege

A [Privilege](/guides-animation/engage-and-animate/privilege-and-activation/privilege.md) is the object stored on a pass. An activation is the “batch mechanism” that creates or updates privileges at scale.

### Execution model (high level)

* When the trigger fires, the platform resolves the segment into pass ids.
* The platform applies the configured privilege to each pass.
* Each updated pass is pushed to Apple/Google via the usual update pipeline.

{% hint style="info" %}
Use an activation when you need repeatable logic. Use the privilege API when you target a single pass.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thewalletcrew.io/guides-animation/engage-and-animate/privilege-and-activation/activation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.