> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/campaigns/campaigns/campaigns-and-referral-campaigns/creating-campaigns/trigger-types.md).

# Trigger Types

Learn more about campaign trigger types and which one to choose for your campaigns.

## Trigger Events

When a relevant event occurs, the system evaluates **all active campaigns with the same trigger** to determine if conditions are met.

<table><thead><tr><th width="255">Trigger Type</th><th>Description</th></tr></thead><tbody><tr><td><strong>Purchase Transaction</strong></td><td>Fires on a successful, member-associated purchase transaction.</td></tr><tr><td><strong>Return Transaction</strong></td><td>Fires on a successful, member-associated return linked to a prior purchase.</td></tr><tr><td><strong>Internal Event</strong></td><td>System-internal actions (e.g., tier change, member activation, profile update, achievement progress).</td></tr><tr><td><strong>Custom Event</strong></td><td>Externally pushed events via API, based on a pre-defined custom event schema.</td></tr><tr><td><strong>Achievement</strong></td><td>Fires when a member completes an achievement (e.g., "First Purchase" milestone).</td></tr><tr><td><strong>Redemption Code</strong></td><td>Fires when a generated code (coupon, QR, etc.) is redeemed by a member.</td></tr></tbody></table>

***

## Learn more about triggers

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Purchase Transactions</strong></td><td><a href="/campaigns/campaigns/campaigns-and-referral-campaigns/creating-campaigns/trigger-types/purchase-transaction.md">Purchase Transaction</a></td></tr><tr><td><strong>Return Transactions</strong></td><td><a href="/campaigns/campaigns/campaigns-and-referral-campaigns/creating-campaigns/trigger-types/return-transaction.md">Return Transaction</a></td></tr><tr><td><strong>Internal Event</strong></td><td><a href="/campaigns/campaigns/campaigns-and-referral-campaigns/creating-campaigns/trigger-types/internal-event.md">Internal Event</a></td></tr><tr><td><strong>Custom Event</strong></td><td><a href="/members-and-activity/custom-events.md">Custom Events</a></td></tr><tr><td><strong>Achievement</strong></td><td><a href="/campaigns/campaigns/campaigns-and-referral-campaigns/creating-campaigns/trigger-types/achievement.md">Achievement</a></td></tr><tr><td><strong>Redemption Code</strong></td><td><a href="/campaigns/campaigns/campaigns-and-referral-campaigns/creating-campaigns/trigger-types/redemption-code-campaign.md">Redemption Code</a></td></tr></tbody></table>


---

# 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://help.openloyalty.io/campaigns/campaigns/campaigns-and-referral-campaigns/creating-campaigns/trigger-types.md?ask=<question>&goal=<user_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.