> 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/internal-event/internal-event-achievement-progressed.md).

# Achievement Progressed

Learn more about the campaign based on the achievement progression.

{% hint style="danger" %}
Please note this is an advanced use case. Contact Open Loyalty Support team if in doubt.

**Make sure to test any configuration thoroughly.**
{% endhint %}

The **Achievement Progressed** internal event allows you to trigger a campaign **each time a member makes progress** within a defined achievement—before they even complete it. This enables more granular reward logic such as **progress-based cashback** or **tiered rewards**.

Use this trigger when you want to **reward members incrementally**, rather than only after an achievement has been fully completed.

***

### 📌 When It’s Useful

This trigger is ideal when you want to:

* Incentivize **ongoing activity** (e.g., monthly spend, visits, transactions).
* Implement **advanced reward distribution** based on how much a member contributes during a given period.
* Combine achievements with campaigns to **distribute units based on thresholds**.

***

### 📥 Available Attributes

When using the `Achievement Progressed` event, you can access both achievement configuration values and the member’s real-time progress.

#### 🔧 Achievement Configuration Attributes

* `periodGoal` – Goal for the current period.
* `consecutivePeriods` – Remaining periods (for achievements based on consecutive goals).

#### 📊 Progress Attributes

* `currentPeriodValue` – Current progress in this period (e.g. amount spent).
* `completedConsecutivePeriods` – Number of completed periods so far.
* `progressChanges` – Change in value since the last progress (i.e. what triggered the event).

{% hint style="info" %}
The complete list of available attributes can be found in the article below:

[Attributes List](/integrations-and-data-exchange/expressions/attributes-list.md#achievement-progress)
{% 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 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/internal-event/internal-event-achievement-progressed.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.