> For the complete documentation index, see [llms.txt](https://developer.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.mediarithmics.io/advanced-usages/contextual-targeting.md).

# Contextual targeting

## Context

Check [User guides documentation](https://userguides.mediarithmics.io/contextual/introduction-to-contextual-targeting) to learn more about this feature.

## Prerequisites&#x20;

URLs & hits must be captured into mediarithmics in order to perform the contextual extraction and semantic analysis. This can be done either through:

* [User event tag](/data-ingestion/real-time-user-tracking/web-events.md) (user tracking)
* [Contextual targeting tag](/advanced-usages/contextual-targeting/general-setup.md#event-rule-configuration) (no user tracking)
* [User activities import](/data-ingestion/bulk-processing/imports/offline-activities.md) (for mobile app only. `url` field needs to be populated in that case)

## Setup

To configure the Contextual targeting feature, follow the setup steps below depending on your needs:

1. [General setup](/advanced-usages/contextual-targeting/general-setup.md) - **MANDATORY**. This initial configuration is required for all customers using the Contextual targeting feature
2. [Activation setup](/advanced-usages/contextual-targeting/activation-setup.md) - OPTIONAL. Complete this step only if you plan to activate your contextual targeting lists. You do not need this step if your goal is solely to use contextual extraction for audience building within the platform


---

# 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://developer.mediarithmics.io/advanced-usages/contextual-targeting.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.
