> 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/monitoring-and-analytics.md).
# Monitoring & Analytics
Once a campaign is active, it’s essential to track its performance. The **Campaign Overview** (Single Campaign View) provides clear, actionable insights into how well your campaign is engaging members.
***
### 📊 Dashboard Metrics
At the top of the overview page, two key metrics are displayed:
* **Total Engagement** – total number of times the campaign has awarded points or actions to members during the selected period
* **Engaged Members** – number of unique members who received rewards at least once in that timeframe
Beneath the summary, a line chart illustrates these metrics over time, helping you identify peaks and trends.
***
### ⏱️ Timeframe Selection & Comparison
* You can adjust the period (e.g., last 7, 30, or 90 days)
* A dashed line indicates metrics for a previous comparison period, enabling performance benchmarking (e.g., month-over-month)
Use this to assess whether engagement is increasing, plateauing, or declining.
***
### 💰 Limits & Budget Section
A lower panel tracks campaign usage and network capacity:
* **Units issued by campaign**: number of points or coupons granted
* **Remaining units**: budget left before hitting limits
* **Per-member limitations**: counts issued per individual (e.g., total or per period)
* **Completion count per member**: how many times each member can engage
This section helps you monitor whether your limit/budget settings are being reached.
***
### 🔍 Interpreting Data
* 📈 **Engagement Spikes**:\
Peaks suggest objectives are resonating—check if they align with trigger events (e.g., start of the campaign, birthday, achievement completion).
* ⚠️ **Zero Engagement**:\
Indicates possible misconfiguration - check trigger schedule, type, active status, and rule conditions.
* 🔄 **Budget Alerts**:\
If “Remaining units” nears zero, consider increasing budget or pausing the campaign to adjust.
***
### ✅ Best Monitoring Practices
1. **Set Alerts**: Monitor daily and weekly engagement trends to spot anomalies.
2. **Compare Periods**: Use the comparison feature to evaluate campaign tweaks.
3. **Watch Budgets**: Prevent early exhaustion or over-delivery of rewards.
4. **Use for Informed Iteration**: Adjust rules, visibility, or timing based on analytics.
---
# 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/monitoring-and-analytics.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.
