> For the complete documentation index, see [llms.txt](https://faq.rollercoin.com/rollercoin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.rollercoin.com/rollercoin/f.a.q./task-wall/7.-why-dont-i-get-any-surveys.md). # 7. Why don't I get any surveys? We would like to bring to your attention that the availability of tasks on our platform is entirely dependent on the discretion and specific requirements of each individual advertiser, which also applies to surveys. This allows advertisers to tailor their tasks to their specific needs and goals, helping ensure that the tasks are relevant and effective for the target audience. Consequently, it is important to note that the rewards, types, and number of tasks offered may vary significantly depending on the region and location from which you are accessing our platform. That being said, we strongly recommend that you regularly check for available tasks from all advertisers in your region to ensure that you can take full advantage of the diverse opportunities available to you. --- # 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://faq.rollercoin.com/rollercoin/f.a.q./task-wall/7.-why-dont-i-get-any-surveys.md?ask=&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.