> 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/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences/view-your-microsite-registration-form-submissions.md).
# 查看你的微站注册表单提交
查看表单时，您可以看到微站注册所有尝试提交的表单详情。如果您需要排查提交失败的原因，我们建议您查看表单提交记录。
1. 从左侧导航菜单中，选择  **\[Engage] → 数据源** → **表单**.
2. 将鼠标悬停在 *微站注册* 表单上，然后选择 **查看提交**.
* 使用筛选器细化搜索。请参阅 *筛选器说明参考* 以获取更多信息。
筛选器说明参考
| 筛选器 | 说明 |
| --- | ----------------------------- |
| 表单 | 保持此筛选器开启 **微站注册** 以避免看到无关的表单。 |
| 状态 | 选择要查看的表单提交状态。此筛选器默认为 *任何状态*. |
| 时间段 | 选择表单提交的时间段。此筛选器默认显示30天。 |
3. 将鼠标悬停在注册表单上，然后选择 **查看详情**.
4. 查看表单的提交详情。
提交摘要
* **状态：** 查看表单提交是否成功。
* **提交于：** 表单提交的日期。
* **提交者：** 提交表单的参与者。
* **提交 ID：** 参与者的唯一标识符。
表单响应
* **电子邮件：** 参与者的电子邮件地址。
* **重定向路径：** 用户在提交注册表单后将被重定向到的微站页面。通常是 /verifyEmail 页面，它是微站用户验证流程的一部分。
* **名字：** 参与者的名字。
* **姓氏：** 参与者的姓氏。
行动
在提交注册表单时，Advocate 系统中发生的任何事情都属于一个操作。例如，用户被添加到某个分群、某人在表单成功或失败时收到电子邮件、表单提交成功或失败，以及失败的原因。
{% hint style="info" %}
**注意：** 如果您已设置一个提交操作，将注册信息发送到 Salesforce，那么操作历史会显示 Salesforce 如何处理这些数据的详细信息。
{% 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.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences/view-your-microsite-registration-form-submissions.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.
