> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/private-panels/panel-management/track-panelist-signup-source.md). # Track panelist signup source By default, where panelists signed up from, or by what means where they added as a panelist, is associated with the **Source** panel property. To see how, or where from, the panelist was added to your company's pool of panelists, go to **Panel Panelists**. Then, look under the **Source** column.
If you aim to track the signups on a more targeted level, e.g., know the social media platform where the signup originated, etc., you can add a **Hidden Value** element on your screener or signup form. Then, make the needed configurations on its **Default Value** and the screener's link. More information can be found in the [Merge Codes section of our Hidden Values](/private-panels/screeners/hidden-values.md#merge-codes) guide. {% hint style="info" %} **Note:** Private Panels was previously managed outside of Dscout, so you may see a different logo and URL in some places. If you have any questions, contact . {% endhint %} --- # 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://help.dscout.com/private-panels/panel-management/track-panelist-signup-source.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.