> For the complete documentation index, see [llms.txt](https://docs.onefootballclub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onefootballclub.com/2-the-end-of-fragmented-fan-value/2.1-what-is-fandom.md).

# 2.1 What is fandom

Fandom is the most durable relationship in sport. A fan attaches to a club or a player, and that attachment holds across markets, platforms and decades, and through wins and losses. Fandom is a culmination of identity and activity over time: who a fan supports, how they show up, and how long they keep showing up.&#x20;

Billions of people carry it. They watch matches, follow transfers, argue tactics, debate team selections, and predict results. Fans experience their fandom as one continuous relationship, yet football’s commercial systems treat it as disconnected moments. The gap is the problem the fandom economy has yet to solve.


---

# 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.onefootballclub.com/2-the-end-of-fragmented-fan-value/2.1-what-is-fandom.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.
