> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paylead.fr/llms.txt
> Use this file to discover all available pages before exploring further.

# Drive engagement

> Program × Product Manager: the engagement levers that drive program success: triggered notifications and activations across Perks and Loyalty.

<Warning>
  **Work in progress, under review.** This page is not validated yet and may contain inaccuracies. Track and record its status in the [documentation review tracker](https://www.notion.so/22a535a8f8794ec8aa19f56cbb5f749a). This banner is removed once the page is validated.
</Warning>

Launching a [Program](/glossary#program) is not enough. Its success depends on **animation**: the timely messages and activations that bring [Consumers](/glossary#consumer) back, prompt them to act, and reinforce the habit. This page catalogs the animation levers across both domains, [Perks](/glossary#perks) and [Loyalty](/glossary#loyalty).

<Info>
  This page is a Product Manager view of *what* to animate and *when*. The technical mechanisms it builds on are documented in [Webhooks](/program/user-journey/concepts/webhooks) (triggers) and [Manage consumers](/program/user-journey/guides/manage-consumers) (consent).
</Info>

## The anatomy of an animation

Every animation combines three things:

| Part        | What it is                                 | Where it comes from                                                                                                                               |
| ----------- | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Trigger** | The event that fires the message           | A [Webhook](/program/user-journey/concepts/webhooks) event (e.g. `reward_created`, `consumer_reward_paid`) or a transaction detected at ingestion |
| **Consent** | The permission that authorizes the message | A consent level on the Consumer, notably [`transaction_triggers`](/program/user-journey/guides/manage-consumers) for transaction-based messages   |
| **Message** | What the Consumer receives                 | The bank's own notification / CRM channel                                                                                                         |

The bank owns the message and the channel; Paylead provides the trigger and enforces the consent. Design each animation as one row of *trigger × consent × message*.

<Warning>
  Transaction-triggered messages require the Consumer's [`transaction_triggers`](/program/user-journey/guides/manage-consumers) consent. Respect frequency and GDPR obligations: animation must stay an opt-in service, never spam.
</Warning>

## What's next

<CardGroup cols={2}>
  <Card title="Webhooks" icon="zap" href="/program/user-journey/concepts/webhooks">
    The events that trigger animations in real time.
  </Card>

  <Card title="Manage consumers" icon="user-cog" href="/program/user-journey/guides/manage-consumers">
    The consent levels that authorize each kind of message.
  </Card>
</CardGroup>