Salesforce Web-to-Lead lets you put lead capture forms on your website. This guide turns visits back to your website after a form submission 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 Salesforce Web-to-Lead form on your HTTPS website and install Converly across the website, including the form and return pages. Follow Install Converly if you have not done that yet.

Set the form's return address (retURL) to a different page on the same website, such as https://www.yoursite.com/thanks. Use the full HTTPS address with the same domain, including www if the form page uses it. Keep the submission and return in the same browser tab.

Converly counts the visitor returning, not a confirmed Salesforce lead. The return must happen within 60 seconds of submitting. Salesforce can refuse a lead and still return the visitor, so refused submissions can count. This includes leads rejected by duplicate rules. A manual return after a failed submission can also count.

Use the standard Web-to-Lead form that submits to webto.salesforce.com. The older www.salesforce.com form address is recognised, but its return journey has not been verified. Web-to-Case, Pardot, custom Salesforce domains, forms inside an embedded frame and forms that submit without leaving your page are not covered.

Forms that require reCAPTCHA have not been tested. The live checks used a Salesforce organisation with Require reCAPTCHA Verification switched off.

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.

The empty flow builder showing the Add A Trigger panel and an Add Trigger button
A new flow, before a trigger is added.

Step 2: Choose Salesforce

A panel slides in from the right listing every lead capture tool Converly supports, grouped by type.

Simply click Salesforce. If you do not see it straight away, scroll the panel or use the search box at the top.

The trigger panel listing supported tools, with Salesforce visible
Pick Salesforce from the list of trigger sources.

Step 3: Choose where it fires

Converly counts when a visitor returns within 60 seconds of submitting a supported Salesforce Web-to-Lead form. Use the page setting to choose which website pages count.

Read this before you choose

Without a specific page, every supported Salesforce 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 a visitor returns within 60 seconds of submitting a supported Salesforce Web-to-Lead form. This includes supported forms across your site. Choose this if all those submissions should count together.

The page selection screen with All Pages selected
All Pages includes supported forms or widgets across your site.

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 original page containing the form, not the return page. Converly uses the original form page for this setting, even though the conversion is counted after the visitor returns. Keep Converly installed across your website so it can recognise that return.

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.

The Specific Pages option selected with example page paths entered
Specific Pages uses the website page containing the form or widget.

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.

The first eligible visit to a different page on the same website counts once. Opening the return page without a previous submission does not count. Refreshing it does not repeat the conversion. Check Salesforce separately to confirm that the lead was saved.

Converly captures email, first name, last name and phone from the standard Web-to-Lead fields when the visitor submits. It includes those details for matching when the return counts. Custom contact fields and a single combined name field are not mapped. Hidden contact fields and other answers are not included.

That's it! The final step is to test your setup in a new incognito window. Submit the Web-to-Lead form with a real email address and let it return within 60 seconds. Check Salesforce separately for the saved lead, including whether a duplicate rule rejected it. 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 the return address, same-tab journey and 60-second limit. Converly must load on the form and return pages, and browser storage must be available. Check the original form page in your page settings and that the flow is Active rather than Draft. Blocked scripts or withdrawn advertising consent can also prevent tracking.