Salesforce on your landing pages
In most companies on Salesforce, marketing has to prove itself in Salesforce. That's hard when paid leads arrive by CSV a day late with the campaign stripped off, or through a Web-to-Lead form someone pasted into the page a year ago. Sending your LanderLab leads to Salesforce makes every submit a Lead in real time, with the page, the variant and the campaign in fields your admin can report on.
It's for teams where Salesforce is the system of record: B2B demand gen on LinkedIn and Google, insurance and lending teams with reps on the phones, agencies running ads into a client's org. There's no Salesforce connector to install: the page's webhook posts each lead to Salesforce's Web-to-Lead endpoint with your org ID, server to server, and the Leads go to the queues and list views your reps already work.
Form submits as Salesforce Leads
Each form submit is created as a Lead in Salesforce the moment the form is sent, with the answers in the Lead fields the webhook maps them to.
Salesforce asks for a last name and a company on every Lead by default. For B2B pages that's natural. For consumer offers, a static value in the webhook can fill Company, so the Lead saves without asking a homeowner for an employer.
Leads in the views your reps already use
A lead from your page is an ordinary Salesforce Lead. It shows up in the list views, queues and reports your team already works from, and a rep qualifies it and converts it into an account, contact and opportunity the usual way. Nobody has to check a second inbox or a shared sheet to find the leads your ads paid for.
Your Salesforce flows run on every page lead
Whatever your admin has built to run on new Leads runs on these too. A record-triggered flow can assign an owner, create a call task or send the first email as soon as the Lead exists, while the visitor is still close to the ad they clicked.
The same goes for your guardrails. Validation rules and required fields apply to page leads as they do to any other, so the data that reaches Salesforce meets the standard your team already set.
Web-to-Lead or the REST API: what's practical
Salesforce offers two ways in. Its REST API wants an OAuth access token, and those tokens expire, which a fixed header on a page webhook can't renew. Web-to-Lead takes a plain form post with your org ID and no token, so it's the route that keeps working without anyone babysitting it. Its limits are Salesforce's, including a daily cap on Web-to-Lead submissions, so check yours against the volume you plan to buy.
If you need the full API, a middle step that manages tokens is the practical answer: LanderLab's New Lead trigger in Zapier, or a Make scenario fed by the page's webhook, can be that step.
Campaign and variant from Lead to closed-won
The campaign, the click ID, the landing page and the page variant can all travel on the Lead, filled from hidden fields and LanderLab's own fields, and carry on to the Contact and the Opportunity when a rep converts it.
Then a report on closed-won opportunities grouped by campaign answers the question that sets next month's budget: which ad spend became revenue, and which page version sold it.
