> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/integrations/integration-reference/trustedform.md).
# TrustedForm
[TrustedForm](https://activeprospect.com/trustedform/) is a tool that, when loaded in Formsort, will produce a certificate proving that a responder actually filled out your form. It is helpful if you are redirecting your responders to affiliate sites and need to provide proof that a real person actually filled out the form flow.
### Enabling TrustedForm
To enable TrustedForm, access **TrustedForm** from the **Integrations** section of a flow.
Make sure that **enabled** is checked.
To actually have the TrustedForm load, you must:
1. Re-deploy the flow from Formsort
2. Within TrustedForm, add the domain that your Formsort flow is hosted on
1. If you are using [Custom domains](/workspace-management/custom-domains.md), you can add those domains
2. If you are not using custom domains, you can add your `.formsort.app` domain - it will look something like `abc123.formsort.app`
### Accessing the TrustedForm certificate URL
It is helpful to be able to associate a particular responder's answers with a TrustedForm certificate URL.
To add the TrustedForm certificate URL to a variant's variables, go to **Variables > System library > Trusted Form certificate URL**.
Once the variable is added and the flow is re-deployed, the certificate that is generated for a responder will be found at the URL that is stored in that variable.
Learn more about [library variables](/response-data-collection-and-management/variable-schema/system-library-answers.md).
### TrustedForm settings
* **Sandbox**: if enabled, the TrustedForm snippet will always be loaded, and will always produce certificates. This is useful for staging environments or for testing.
---
# 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.formsort.com/integrations/integration-reference/trustedform.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.
