How to collect leads from an external website form

A landing page can keep working on its current host while your team manages enquiries in one place. Start with a single quote or demo form and test the entire journey from submission to follow-up.

Decide what a useful lead looks like

Ask for the information your team needs to reply. A web agency might need a name, email address, type of project and a short description. Pick field names you will recognize in the submission view and give the form a distinct name so it is easy to identify later.

Connect the external form to PraismaHub

In Lead Center, open the form and enable Accept submissions from other websites. Add the website that hosts the form to the allowed list. The form drawer provides HTML and JavaScript examples for sending submissions to its public endpoint. Use the example that suits the page and map the field names to your form.

Test from the page a customer will use

1. Submit a realistic enquiry from the external website.

2. Check the success message or redirect and verify the entry appears in Lead Center.

3. Try an invalid email to see whether the visitor gets a clear error.

4. Give one person ownership of new enquiries and confirm that they can see the submission.

For a second landing page, decide whether leads should share the same form or have their own source. Separate forms help when different teams own the follow-up. A shared form works when the owner and response process are the same.

Example: connect a quote form on an agency website

Suppose an agency already has a landing page for website redesign enquiries. It wants the enquiry to land in the same Lead Center as submissions from other campaigns. Keep the existing page and choose one form for the pilot. Name it so a teammate can identify the source later, such as Website Redesign Quote, and agree who will check the queue after launch.

Make a small field map before editing the page. The name shown beside an input can be friendly, such as “What would you like to build?” The field identifier sent by the form should remain stable. Document the expected identifier for email, project type and message so the developer and lead owner can compare what the website sends with what Lead Center receives.

Choose how the form should submit

The HTML example is a starting point for a traditional form. The JavaScript example is useful when the page needs to update in place or already handles submissions through its own frontend code. Follow the example from the form drawer for the exact endpoint and expected data. Keep private credentials out of browser code. This external submission route uses a public endpoint rather than an API token.

Run this checklist on the live hostname

1. Test the public hostname that visitors use. If staging uses a separate hostname, decide whether to allow it for testing.

2. Send a test with a unique reference in the message so you can find the exact entry in Lead Center.

3. Compare the received fields with the field map, including any optional values.

4. Check the confirmation on mobile and make sure a failure offers a clear way to try again.

5. Ask the lead owner to open the entry and confirm they can see what they need to reply.

Troubleshoot with the failed step in mind

If the form appears to submit but no entry arrives, confirm that the page is posting to the endpoint for the intended form and that the submitting website is on its allowed list. If the entry arrives with a missing value, compare the submitted field name with the expected field identifier. If the lead is visible but nobody responds, confirm the owner and the routine for checking the queue.

Test one incorrect input and one normal input after changing the form. Record whether the error came from the browser, the request or the receiving form. That small distinction saves time when someone has to investigate the same issue later.

Measure the handoff as well as the form

In the first week, count valid submissions and how many received a reply. If visitors regularly leave a field blank, check whether the question is easy to understand and necessary for the first contact. Keep the handoff short: the owner should know where to look, what a new enquiry needs and when to pass it to someone else.

See the PraismaHub forms and submissions guide for the product setup.