> 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.

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:**

* **tenantId**: ID of the tenant where the campaign was created
* **memberId**: Unique ID of the member
* **email**: Member's email address
* **phone**: Member's phone number
* **loyaltyCardNumber**: Member's loyalty card number
* **visibleCampaigns:** Serialized array of campaign UUID's


---

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

```
GET https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/campaign-visibility.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.