---
title: Combine both recipient management approaches
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

## Combine both approaches for targeted campaigns

You don't need to choose just one approach. A hybrid strategy uses multiple recipient lists for clearly distinct email streams while applying contact group filtering within a given list for more granular targeting.

**When to choose this approach**:

- You have one main subscriber base, but need to send differentiated content to sub-segments.
- Some content should go to everyone, while other content targets specific groups – and you want to avoid sending both versions to the same person.

### Example: Tiered sports club subscribers

A sports club has one main recipient list for all email subscribers. Everyone on the list receives general updates like match schedules and club news.

However, the club also has a "Fans" tier – dedicated supporters who get exclusive content such as behind-the-scenes access and early ticket sales.

Here's how they set it up:

1. Developers add a [custom contact field](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/contact-configuration.md) called _FanClubMember_ (a boolean field). See the [Add a custom field to the Contact profile](https://docs.kentico.com/guides/development/customizations-and-integrations/add-custom-contact-field.md) guide for details.
2. A contact group called _Fans_ is created with the condition: "Contact field _FanClubMember_ is equal to **1**"
3. **For general club emails** (match schedules, news): send to the recipient list with the _Fans_ group set under **Exclude recipients from contact groups**. This way, fans don't receive the general version – they receive the targeted version instead.
4. **For fans-only emails** (exclusive content, early ticket access): send to the same recipient list with **Send only to recipients from contact groups** set to _Fans_.

> **Tip:** **Schedule both email variants at the same time**
>
> Use the **Schedule for later** option and set the same delivery time for both the general and fans-only emails. This prevents a timing gap where fans might receive the general email before the targeted version is ready, or vice versa.
>
> Remember, Xperience does not have frequency capping, so in more complex scenarios with multiple recipient tiers and possible overlaps between contacts groups, some contacts could receive multiple versions of the same email if you don't coordinate.