> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/audience-and-activation/target-contextually/contextual-reference/targeting-lists.md).

# Targeting lists

The set of URLs both contextual solutions produce, the criteria a semantic list accepts, and the blacklisting patterns.

## What a targeting list is

A **targeting list** is a set of URLs to be targeted. Both contextual solutions produce one: [semantic](/audience-and-activation/target-contextually/contextual-reference/semantic-targeting.md) from criteria you name, [panel-based](/audience-and-activation/target-contextually/contextual-reference/panel-based-targeting.md) from the content a seed audience consumes. It is the object you activate on an ad platform, and - for semantic lists only - the object you can use as an audience segment criterion.

## The Targeting lists menu

The **Targeting lists** menu holds every list previously created by either solution. Among the information displayed:

<table data-search="false"><thead><tr><th width="230">Column</th><th>What it tells you</th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Panel-based or Semantic.</td></tr><tr><td><strong># URLs</strong></td><td>The number of targeted URLs.</td></tr><tr><td><strong>30-days page views</strong></td><td>Page views over the last 30 days.</td></tr><tr><td><strong>Activated on</strong></td><td>The platforms where the list has been activated.</td></tr><tr><td><strong>Use for Audience segments</strong></td><td>Whether the list can be used as an audience segment criterion. <strong>Only applicable to Semantic lists.</strong></td></tr></tbody></table>

## Criteria a semantic list accepts

Inclusion and exclusion are not symmetric across criteria types, and that asymmetry drives how blacklists have to be built.

| Criterion            | Inclusion | Exclusion |
| -------------------- | --------- | --------- |
| Entities             | Yes       | Yes       |
| IAB categories       | Yes       | Yes       |
| Raw keywords         | Yes       | **No**    |
| URL or group of URLs | Yes       | Yes       |
| Channels             | **No**    | Yes       |

## Blacklist management

For brand safety and brand suitability, you will want to keep certain content out of your targeting. Two patterns, depending on how often you need the exclusion.

<table data-search="false"><thead><tr><th width="200">Need</th><th>Pattern</th></tr></thead><tbody><tr><td><strong>One-time exclusion</strong></td><td>Add the entity or category directly to your targeting list as an exclusion criterion. Remember that raw keywords cannot be used as exclusion criteria.</td></tr><tr><td><strong>General exclusion</strong>, across many campaigns</td><td>Create dedicated targeting lists that act as blacklists in your ad servers: the list <em>targets</em> everything to be excluded, and you then apply it as an exclusion criterion at campaign or line-item level in the ad server.</td></tr></tbody></table>

{% hint style="info" %}
The second pattern inverts the usual reading of a list: the URLs in it are the ones you do **not** want. The exclusion happens in the ad server, not in mediarithmics - which is what makes one list reusable across every campaign.
{% endhint %}

## Making a list usable in audience segments

A semantic list carries a **Use for Audience segments** option, set when the list is saved. Without it, the list will not appear in the targeting list search when you build a segment.

{% hint style="warning" %}
Two delays to expect:

* After enabling the option, wait around **15 minutes** for the targeting lists to be refreshed before the list appears in the search input.
* The option is **not retroactive**. Events ingested before the list was configured with it are not tagged with the list's ID, and are therefore not targetable through that criterion. Updating a list's definition likewise has no effect on events ingested earlier.
  {% endhint %}

See [Use contextual targeting in segments](/audience-and-activation/target-contextually/use-contextual-targeting-in-segments.md).

## When the list changes

The **contextual targeting JavaScript tag** is regularly updated to take into account new targeting lists, configuration changes on existing lists, and new URLs.

{% hint style="info" %}
Only URLs with a minimum number of page views are targetable. Consult your Account manager to check or update the minimum for your organisation.
{% endhint %}

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Contextual activation</strong></td><td>Sending a list to an ad platform.</td><td><a href="/audience-and-activation/target-contextually/contextual-reference/contextual-activation.md">Contextual activation</a></td></tr><tr><td><strong>Semantic targeting</strong></td><td>The criteria that fill a semantic list.</td><td><a href="/audience-and-activation/target-contextually/contextual-reference/semantic-targeting.md">Semantic targeting</a></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://docs.mediarithmics.io/audience-and-activation/target-contextually/contextual-reference/targeting-lists.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.
