> For the complete documentation index, see [llms.txt](https://docs.clearout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearout.io/integrations/forms/leadpages.md).
# Leadpages
Integrate Clearout with Leadpages for real-time email validation
The Clearout Form Guard supports the **simple integration of real-time email validation on Leadpages**. It helps to stop bad leads from getting into your Email list or CRM via Leadpages. \
\
A **form or landing page** created on Leadpages generally **doesn’t detect invalid email addresses** like disposable, spam-trap, gibberish, or role/group addresses or mis-typos, resulting in poor lead quality.
**Embedding Clearout’s Form Guard in Leadpages** can detect such bad email addresses in real-time, **upgrading the quality of leads** and **increasing the deliverability rate** with better engagement.
## How It Works:
{% stepper %}
{% step %}
Go to the **Clearout account**, click on **Form Guard**. "**Create Guard**" and customise the validation checks. **Save** the Guard to generate the **JavaScript code snippet**.
{% endstep %}
{% step %}
**Add** the Clearout Form Guard snippet as part of the Leadpages script using **Settings** **→ Analytics →** Header tag
Once the complete script is embedded, the real-time verification will be active.
> **Powered by Clearout** is visible in the trial version, which can be removed upon upgrading your account. The same process can be followed for pop-up forms as well.
> {% endstep %}
> {% endstepper %}
Integrating the Leadpages forms/landing pages with the Clearout email verifier will add caliber to the lead capture flow/process.
---
# 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.clearout.io/integrations/forms/leadpages.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.
