# Campaign Execution

The Campaign Execution report indicates when and which transaction triggered the campaign.&#x20;

A sample file is provided below:

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

**Available Data:**

* **campaignExecutionId**: ID of the campaign execution
* **tenantId**: ID of the tenant where the campaign was created
* **campaignId**: Unique ID of the campaign
* **contextData**: Context data that triggered the campaign (e.g. member's data, transaction data)
* **createdAt**: Date when the entry was created
* **updatedAt**: Date when the entry was last updated
* **executedAt**: Date when the entry was executed
* **executionStatus**: Status of the execution (`success`, `skipped`, `failed`)
* **customerId**: Member's ID generated in Open Loyalty (`memberId`)
* **transactionId**: ID of the transaction that triggered the campaign (for the campaign's triggered by transactions)
* **message**: Message for failed executions
* **warningMessage**: Warning message for failed executions


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/campaign-execution.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
