> For the complete documentation index, see [llms.txt](https://docs.pulselabs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulselabs.ai/participants/participant-funnel.md). # Participant Funnel ## Participant funnel Every participant in Pulse Labs moves through a structured funnel before they can participate in your study. The funnel ensures participants meet your criteria and have completed any required verification steps before they access your capture methods. ### How the funnel works Every participant in Pulse Labs moves through a structured funnel before they can participate in your study. The funnel ensures participants meet your criteria and have completed any required verification steps before they access your studies. The stages are: **Recruited → Verified → Enrolled** #### Stage 1: Recruited Participants that have been introduced to your study — either through a direct email invitation, a CSV upload, a Pulse Voices panel listing, or an external recruitment link — but have not completed any verification steps yet. Think of these participants as your pool of participants listed on the Recruitment tab. #### Stage 2: Verified (optional) The participants have passed all verification steps you've configured. They've met your screening criteria, passed other applicable verification steps, and are confirmed eligible. Note: Verifications are selected at the project level and are optional. Participants remain on the Recruitment tab until they pass your verification steps and until they are enrolled. #### Stage 3: Enrolled When you have decided which participants you want, select them individually on the Recruitment tab (or Select all for bulk enrollments) and then select Enroll. These enrolled participants can be actively assigned to capture methods within your project. You can see how many participants are at each stage from the project dashboard's Recruitment and Enrollment tabs. ### Verifications You configure which verification steps are required for your study. Participants must complete every enabled step before they move from Invited to Verified. All steps are optional — enable only the ones relevant to your research. #### Location verification Confirms the participant’s current location or permanent address matches your study’s target region. Two location modes: * **Current location** — Uses real-time location data to verify where the participant is right now. Useful for studies that require participants to be in a specific location during the research. * **Permanent address** — Verifies the participant's home address. Useful for studies targeting specific regional markets or demographics. #### Identity verification Confirms the participant is who they say they are using third-party identity verification through **Persona**. Identity verification requires the participant to take a picture of their government-issued ID and take a selfie from a few view angles. **How it works** 1. The participant takes a photo of their government-issued ID. 2. They take a selfie from multiple angles. 3. **Persona** matches the ID photo to the selfie and verifies the ID information. 4. Results are returned automatically. **Good to know** Many participants on the Pulse Voices panel are already ID-verified. Newly invited participants will complete this step if required by your study. **When to use it** * As an escalation when participants fail passive device and network checks * High-stakes research requiring verified identities * Regulated industries that require participant authentication #### Face Verification Requires participants to complete a biometric check to confirm a real, unique person is operating their device and they are not associated with another participant account. **How it works** 1. The participant explicitly agrees to the face verification consent. 2. They allow camera access when prompted on their device or browser. 3. They follow the on-screen guidance to complete the face verification. 4. Results are returned automatically. **Good to know** Face verification keeps your participants trustworthy for your research team and protects your study from duplicates. This is separate from the **government-ID verification**. **When to use it** * As an escalation when duplicate accounts are suspected * High-stakes research requiring verified identities * Regulated industries that require participant authentication #### Document signature Requires participants to review and digitally sign documents through the integrated e-signature system before proceeding. These are typically consent forms, NDAs, or participation agreements. **How it works** 1. Documents must be shared to the Pulse Labs team to review and port into the e-signature platform. 2. Participants review and sign them digitally via the integrated e-signature system. 3. Signed documents are reported as completed tasks on the participant dashboard. **When to use it** * Your IRB or legal team requires signed consent * Participants will be exposed to confidential information * Regulatory requirements mandate documented consent ### Managing the funnel #### Approving and rejecting participants For verification steps that require manual review, you'll see pending participants in the Recruitment tab. For each participant you can: * **Approve** — Move them to the next verification step (or to Enrolled if this was the last step) * **Reject** — Remove them entirely from the project #### Monitoring progress The Recruitment tab shows each participant's current position in the funnel and which verification steps they've completed or are pending. Use the Enrolled tab to see your fully qualified, active participant pool. --- # 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://docs.pulselabs.ai/participants/participant-funnel.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.