> 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/technical-guide/data-exports/data-structure-and-types/campaign-calculated-effect-results.md).

# Campaign Calculated Effect Results

The calculated result of each campaign effect, exported daily as a delta file.

The Campaign Calculated Effect Results file contains the outcome of each effect of a campaign execution, for example the number of units granted or the reward issued.

{% hint style="info" %}
**Delta export.** Each daily file contains effect results created or updated during that day. Upsert on `calculatedEffectResultId` and keep the row with the latest `updatedAt`.
{% endhint %}

**File:** `analytics/Campaigns/campaigns_calculated_effects_results_YYYY_MM_DD.csv`\
**Primary key:** `calculatedEffectResultId`

A sample file is provided below:

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

**Available Data** (in column order, see Column types for how each type is written):

<table><thead><tr><th width="244.328125">Column</th><th width="96.2421875">Type</th><th width="114.33984375">Can be empty</th><th>Description</th></tr></thead><tbody><tr><td><code>calculatedEffectResultId</code></td><td>uuid</td><td>No</td><td>Unique ID of the calculated effect result</td></tr><tr><td><code>tenantId</code></td><td>uuid</td><td>No</td><td>ID of the tenant where the campaign was created</td></tr><tr><td><code>campaignExecutionId</code></td><td>uuid</td><td>No</td><td>ID of the campaign execution the effect belongs to (links to the Campaign Execution file)</td></tr><tr><td><code>status</code></td><td>enum</td><td>No</td><td>Status of the effect result (<code>success</code>, <code>skipped</code>, or <code>failed</code>)</td></tr><tr><td><code>targetId</code></td><td>uuid</td><td>No</td><td>ID of the member who received the effect (same value as <code>memberId</code> in the Members file)</td></tr><tr><td><code>type</code></td><td>enum</td><td>No</td><td>Type of the effect: <code>give_points</code>, <code>deduct_unit</code>, <code>give_reward</code>, <code>grant_badge</code>, <code>assign_member_custom_attribute</code>, <code>remove_member_custom_attribute</code>, <code>cancel_transaction_effects</code>, <code>assign_member_to_tier</code></td></tr><tr><td><code>createdAt</code></td><td>datetime</td><td>No</td><td>Date when the entry was created</td></tr><tr><td><code>updatedAt</code></td><td>datetime</td><td>No</td><td>Date when the entry was last updated</td></tr><tr><td><code>points</code></td><td>decimal</td><td>Yes</td><td>Number of units calculated by the effect</td></tr><tr><td><code>couponValue</code></td><td>decimal</td><td>Yes</td><td>Value of the coupon granted (for dynamic coupons)</td></tr><tr><td><code>rewardId</code></td><td>uuid</td><td>Yes</td><td>ID of the reward granted (links to the Rewards file)</td></tr><tr><td><code>walletCode</code></td><td>string</td><td>Yes</td><td>Code of the wallet type the units were granted to (matches <code>walletTypeCode</code> in the Unit Transfers and Wallet Balance files)</td></tr><tr><td><code>error</code></td><td>string</td><td>Yes</td><td>Error message for failed effects</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/technical-guide/data-exports/data-structure-and-types/campaign-calculated-effect-results.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.