> 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-visibility.md).

# Campaign Visibility

The file displays the list of visible campaigns per member.

This file can be used e.g. for the marketing tools to send out emails on available campaigns.

**File:** `analytics/CampaignsVisibility/campaigns_visibility_YYYY_MM_DD_N.csv`\
**Primary key:** `memberId`

The file is split into parts of up to 222,500 rows each. The parts are numbered from `0` (`_0`, `_1`, …), and the suffix is present even when there is only one part. Load all parts for a given date.

A sample file is provided below:

{% file src="/files/8n7RwlWrw1wmXYhBYJwo" %}

{% hint style="warning" %}
This report is **not** available by default. If you want to have it enabled for your environment, please contact Open Loyalty support team.
{% endhint %}

{% hint style="danger" %}
This report is **not** a delta file. This is a daily list of available campaigns for all the members on a given day.
{% endhint %}

**Available Data:**

<table><thead><tr><th width="187.43359375">Column</th><th width="114.80859375">Type</th><th width="128.73046875">Can be empty</th><th>Description</th></tr></thead><tbody><tr><td><code>tenantId</code></td><td>uuid</td><td>No</td><td>Tenant ID</td></tr><tr><td><code>memberId</code></td><td>uuid</td><td>No</td><td>Member ID</td></tr><tr><td><code>email</code></td><td>string</td><td>Yes</td><td>Member email address</td></tr><tr><td><code>phone</code></td><td>string</td><td>Yes</td><td>Member phone number</td></tr><tr><td><code>loyaltyCardNumber</code></td><td>string</td><td>Yes</td><td>Member loyalty card number</td></tr><tr><td><code>visibleCampaigns</code></td><td>json array</td><td>No</td><td>Serialized array of campaign UUID's</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-visibility.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.