> For the complete documentation index, see [llms.txt](https://docs.cros.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cros.world/advertising-ecosystem-today/advertising.md). # Advertising ## Advertiser Advertisers can be traditional businesses, influencers or any other party that would like to promote their brands and services to users through the digital real estate made available by publishers in the games. The advertisers themselves might have digital presence and can target to attract virtual attendees to their properties where they can either buy virtual goods or collect coupons/offers to buy goods from physical stores. While there are avenues available to advertise, but nothing comes close to the ubiquity, ease of use and capability of traditional product like an ad-manager or campaign management tool in the traditional web2 ecosystem. ### Consumer These are people like us looking for entertainment and other experiences in the games and virtual worlds. They have been "the product" in the traditional web2 advertisement economy. Again, a group which has been easy to exclude from the advertising value chain to say the least. ### --- # 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.cros.world/advertising-ecosystem-today/advertising.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.