> For the complete documentation index, see [llms.txt](https://emailpref.gitbook.io/emailpref-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emailpref.gitbook.io/emailpref-documentation/use-cases/dynamic-list-visibility.md).

# Dynamic List Visibility

> Segmentation is key to effective communication. However, managing user preferences can be tricky, especially when catering to diverse user groups. Take, for example, Flourish Institute, faced a common dilemma: How to distinguish between email preferences for paid users and free users without compromising user experience? Additionally, how to prevent free users from subscribing to email lists intended for paid users?

### ❌ Problem

Flourish Institute faced a challenge: managing email preferences for both paid and free users effectively. Their goal was: to grant paid users access to all available email lists while limiting free users' access to only a select few on the preference page. Their existing system did not offer a seamless solution for such differentiated management.

### ✅ Solution

Leveraging [ActiveCampaign](https://www.activecampaign.com/)'s tag functionality, our team devised a solution: Dynamic Show/Hide Lists. This innovative feature allows users to control list visibility based on predefined tags. Here's how it works:

1. **Tag-Based Segmentation:** By tagging users as "paid" or "free" in ActiveCampaign, Flourish Institute gained granular control over list access.\
   ‍
2. **Dynamic Preference Pages:** Our team implemented logic to customize the preference page based on user tags. Paid users are presented with all available lists, empowering them to tailor their email subscriptions to their preferences. Meanwhile, free users are shown a curated selection of lists, maintaining a seamless user experience.\
   ‍
3. **Enhanced User Experience:** With Dynamic Show/Hide Lists, Flourish Institute can provide a personalized experience for each user segment, ensuring relevant content delivery without overwhelming users with unnecessary options

<figure><img src="/files/XxevT8IlkXvMGJvAPVqR" alt=""><figcaption><p>Dynamic show/ hide lists</p></figcaption></figure>

### 🛫 Outcome

By implementing Dynamic Show/Hide Lists, Flourish Institute successfully streamlined their email preference management process. Paid users enjoy greater flexibility in selecting their preferred email lists, while free users receive targeted content tailored to their interests. This solution not only enhances user experience but also maximizes engagement and retention.

Dynamic Show/Hide Lists offer a powerful solution for managing list visibility based on user tags, empowering businesses to deliver personalised content and optimize user engagement. As email marketing continues to evolve, innovative features like Dynamic Show/Hide Lists enable businesses to stay ahead of the curve and deliver exceptional customer experiences.


---

# 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://emailpref.gitbook.io/emailpref-documentation/use-cases/dynamic-list-visibility.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.
