> For the complete documentation index, see [llms.txt](https://nfts-101.kyzzen.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nfts-101.kyzzen.io/evaluating-nft-projects/key-factors/marketing.md). # Marketing The marketing strategy of a collection is important in establishing its brand in the space and attracting newcomers to the community. Some questions to ask here are whether there are specific team members fully dedicated to marketing the project, what their overall strategy is, and if they have allocated a sufficient budget for this. Typical marketing strategies include: * An aggressive Twitter presence with regular giveaways/events * Influencers (crypto twitter and/or celebrity) * Partnerships/collaborations with other projects Another thing to consider is also how well-built the website is. The website is typically the face of a project, and often the first place that newcomers look at when they come across a project. It goes without saying that a higher quality website should provid --- # 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://nfts-101.kyzzen.io/evaluating-nft-projects/key-factors/marketing.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.