> For the complete documentation index, see [llms.txt](https://docs.xoob.link/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xoob.link/introduction/why-xoob.md). # Why XOOB Most marketing activity in Web3 happens on social platforms. Projects collaborate with creators to generate visibility through posts, discussions, and community engagement. Campaign performance is typically measured using metrics such as: * impressions * likes and reposts * follower growth * engagement rates These indicators reflect attention, but they rarely reveal the most important outcome: product adoption. For protocols and on-chain applications, the key questions remain difficult to answer: * Does social attention translate into real product usage? * Which creators actually drive on-chain activity? * How can campaigns distinguish between genuine influence and superficial engagement? Today, attention and product impact exist in separate measurement systems. Social platforms capture visibility, while blockchain networks record user activity. However, there is no unified infrastructure that connects these layers in a transparent and verifiable way. XOOB addresses this gap by connecting creator influence with measurable on-chain outcomes. --- # 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.xoob.link/introduction/why-xoob.md?ask=&goal= ``` `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.