> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences/track-microsite-registrations-with-a-segment.md).
# Track Microsite Registrations With a Segment
To see who has registered for your microsite, create a segment that automatically captures all registrants. You can then use this segment to filter the Participants tab or when exporting participant reports.
### Create a segment for microsite registrations
You’ll first need to create a segment to add registered participants to if one is not yet set up. To do so:
1. From the left navigation bar, select  **\[Engage] → Data Sources → Segments**.
2. In the top-right corner select **Add Segment**.
3. Give your segment a name and then select **Add**.
### Assign a segment to your registration form
Once your segment is added, you can assign it to the registration form so that any new users who register through your microsite will automatically be assigned to the segment:
1. From the left navigation bar, select  **\[Engage] → Data Sources → Forms**.
2. Hover your cursor over the *Microsite Registration* form and select **Edit**.
3. In the *When the form succeeds* section, select the **Update user segments** drop box and select the segment you created that you want the users added to.
4. Select **Update Registration** to save your changes.
Moving forward, any new users who register via your microsite form will be automatically added to the segment.
### Assign already registered users to your segment
For users who have already registered, you can add them manually by following the instructions below:
1. From the left navigation bar, select  **\[Engage] → Participants**.
2. Select the participant you’d like to add to your segment.
3. Scroll down to the *Segments* section and select **Add segment**.
4. From the drop list select the segment you’d like to add the user to.
For more information on user segments, see [Manage Advocate User Segments](/brand/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/manage-advocate-user-segments.md).
### View which participants registered via your microsite
Once you have your segment in place and users have been added to it, you can view the participants of this segment by using the filtering option on the *Participants* screen or exporting a report.
{% tabs %}
{% tab title="Filter participants" %}
1. From the left navigation bar, select  **\[Engage] → Participants**.
2. Select **Advanced filter**.
3. Select **Add filter** and proceed to fill out the drop boxes to filter to what you’re looking for.
{% endtab %}
{% tab title="Export a report" %}
1. From the left navigation bar, select  **\[Engage] → Reporting → Imports & Exports**.
2. In the top-right corner, select **Create Report**.
3. Give the report a name.
4. Select **User details** as the report type (this is the participants export).
5. Ensure  **\[Checked box]** **User Fields** is selected and feel free to add any other fields you want.
6. Select the *Report format*, either **CSV** or **Excel**.
7. Select **Create Report**.
{% endtab %}
{% endtabs %}
---
# 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.impact.com/brand/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences/track-microsite-registrations-with-a-segment.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.
