Close Forms lets you embed lead capture forms on your website. This guide turns supported form completions into conversions you can send to your ad platforms.
There is no account to connect. To set it up, follow the instructions below:
Before you start: Publish a standard single-step Close form directly on a live HTTPS page and install Converly on that page. Follow Install Converly if you have not done that yet.
Use Close's inline embed with its normal completion message. Hosted Close pages, forms inside another embedded frame, multi-step forms and redirects are not covered. Custom embeds that prevent access to the form fields are not supported.
Close can report completion for spam submissions too. Submissions caught by its hidden spam-trap field (sometimes called a honeypot) still count. A conversion does not prove that Close saved a lead.
CAPTCHA, file uploads, other serving domains, real iPhones and in-app browsers have not been verified.
Step 1: Create a flow
A flow is the rule that turns a form submission into a conversion. Click Flows in the left sidebar, then Create New Flow, and give it a name like "Contact form leads".
You land in the flow builder. It is empty for now. Click Add Trigger to choose what starts this flow.

Step 2: Choose Close Forms
A panel slides in from the right listing every lead capture tool Converly supports, grouped by type.
Simply click Close Forms. If you do not see it straight away, scroll the panel or use the search box at the top.

Step 3: Choose where it fires
Converly counts when Close returns its completion answer for a supported single-step form. Use the page setting to choose which website pages count.
Read this before you choose
Without a specific page, every supported Close form on your site can contribute to the same conversion. To count only the ones on a particular page, choose that page.
Option 1: Trigger on all pages
A conversion fires when Close returns its completion answer for a supported single-step form. This includes supported forms across your site. Choose this if all those submissions should count together.

Option 2: Trigger on specific pages
To count a form on https://www.yoursite.com/contact-us, select Specific Pages and enter /contact-us. The path is just the part after your domain. Start it with a slash, and do not include the domain.
Use the website page containing the form or widget, including for pop-ups. Do not enter a hosted form address or a separate thank-you page.
Click Add another page if you want to include more than 1 page, or the x to remove a page.
If 2 forms or widgets share 1 page
Page filtering includes both, so both can count as this conversion. To count only 1, put it on its own page, or contact support before publishing.

When you have picked an option, click Set trigger.
What happens next
A trigger on its own does not send anything yet. Next you add 1 or more destinations (Google Ads, Meta, and so on) and publish the flow. See Building a flow for that part.
Clicking Send or showing thank-you text alone does not count. Converly waits for Close's completion answer. Missing required fields and failed requests do not count, but spam and honeypot submissions can count because Close gives them the same completion answer.
Converly captures the visible name and email fields for matching. A full name is split into first and last name. Phone numbers, hidden fields, the spam-trap field and other answers are not included.
That's it! The final step is to test your setup in a new incognito window. Submit the inline form on your live website with a real email address and check that it completes. Check Close separately to confirm that it saved the lead. Then click Logs in Converly's left sidebar and check the destination results for your test. You can read more about how to properly test your setup here.
If submissions are not showing up later, check that you use a standard single-step inline embed with no redirect. Then check your Converly installation, page paths and that the flow is Active rather than Draft. Submitting immediately as a form appears or sending overlapping requests can cause a submission to be missed. Blocked scripts or withdrawn advertising consent can also prevent tracking.
