> For the complete documentation index, see [llms.txt](https://docs.enable3.io/enable3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enable3.io/enable3/info-tab.md).

# Info Tab

The **Info Tab** is an information panel displayed inside your loyalty and engagement widget. It tells users everything they need to know about an active campaign (e.g., how to participate, what the rules are, and what rewards they can earn).

<figure><img src="/files/DwOUrY2oJymtlTnqfB0i" alt=""><figcaption></figcaption></figure>

### Why Use Info Tab

#### Case #1: Your users don’t understand the rules of the Campaign

**Problem**: In an always-on loyalty program, users – especially returning or inactive ones – often need a knowledge refresher on how the program works or whether the rules have changed.

**Solution**: Keep the current rules and reward tiers in the Info Tab so users can reorient themselves at any point without contacting support.

**How to do it**: Populate the Info Tab with the main Campaign details, but don’t set the dates of the Campaign.

**Outcome**: Users can self-serve campaign information on demand, reducing drop-off caused by confusion and lowering the support load on your team.

#### 🎯 Info Tab benefits

* Users understand participation rules from the start → **higher activation rate**
* Returning users can re-orient without support → **reduced drop-off and churn**
* Campaign messaging stays consistent across all widget entry points → **more coherent user experience**

### How to Set Up Info Tab

{% hint style="success" %}
Info Tab is available for both No-code and API integrations.&#x20;
{% endhint %}

Go to the **Info Tab** section in your admin dashboard.

<figure><img src="/files/V8T0hf4wTLq9r6ZsHv6c" alt=""><figcaption></figcaption></figure>

In the Structure tab, you can configure everything about the Info Tab page in your widget.&#x20;

Fill in the essential information you want to provide about your Campaign in the **Head** section.

Put your Call to Action in the **Button name** field. Note that this button leads to the **All Missions** tab *in your Widget* by default.

Add details about your Campaign, like the rules, rewards, or anything else worth noting, in the **Body** section. It will appear below the Head section and the Campaign countdown in the Widget.

<figure><img src="/files/HwGE0fGOGy7LKPgLnLaU" alt=""><figcaption></figcaption></figure>

In the **Conditions** tab, set the Campaign deadline if you are running a Seasonal or time-limited Campaign.

<figure><img src="/files/5CaMPwvtwsROncs0zzgm" alt=""><figcaption></figcaption></figure>

Or, remove the Due Date in case of a long-term Campaign by clicking on the x.

<figure><img src="/files/g1d9aexQNbvo1aew8hNx" alt=""><figcaption></figcaption></figure>

This way, all the information in the Body section will appear **right after** the Head section in the Widget.

<figure><img src="/files/kkF75uPKRgXkvCEOyQeg" alt=""><figcaption></figcaption></figure>

Click **Save**. The Info Tab panel will update immediately and become visible to users inside the Widget.

Congratulations, you’re all set!

<br>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.enable3.io/enable3/info-tab.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
