> 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/implementation-guide/integrations-and-data-exchange/imports-exports/exports/ui-exports/campaigns.md).

# Campaigns

Campaigns support two distinct exports: a **dashboard** report (metrics) and a **configuration** export (the campaign setup itself, for backup or copying to another tenant).

### Campaign dashboard

Export the campaign overview in PNG, JPG, or CSV.

**File format:** PNG, JPG, or CSV

**Sample dashboard overview CSV file**

{% file src="/files/odxHOfRDCC19WzYHPkN9" %}

**Field reference**

<table><thead><tr><th width="220">Field</th><th>Description</th></tr></thead><tbody><tr><td>Total Engagement</td><td>Total number of times the campaign has awarded points or actions to members in the selected period</td></tr><tr><td>Engaged Members</td><td>Number of unique members who received a reward at least once in the selected period</td></tr><tr><td>Units issued by campaign</td><td>Number of points or coupons granted by the campaign</td></tr><tr><td>Remaining units</td><td>Budget left before hitting the campaign's unit limit</td></tr><tr><td>Per-member limitations</td><td>Units issued per individual member (total or per period)</td></tr><tr><td>Completion count per member</td><td>How many times each member has completed the campaign against the allowed total</td></tr></tbody></table>

### Campaign configuration

Export an individual campaign configuration as JSON — useful for backup or copying a campaign to another tenant.

**File format:** JSON


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/implementation-guide/integrations-and-data-exchange/imports-exports/exports/ui-exports/campaigns.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 `build a script that syncs our docs to a CMS` 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.