What does a Salesforce integration do on a marketing site?
On a marketing site, a Salesforce integration turns form submissions into leads in your Salesforce org, so sales can follow up without copying anything by hand. Done well, each lead arrives with its source, the page it came from and the campaign that brought it, and lands with the right owner.
- Lead capture: demo requests, contact forms and gated content create Lead records with mapped fields.
- Attribution: UTM parameters, landing page and referrer saved to custom fields on the lead.
- Campaign membership: leads added to the right Salesforce campaign for reporting.
- Routing: assignment rules send each lead to the right rep or queue.
- Follow-up: auto-response rules or a booking step so the buyer knows what happens next.
The website's job is to collect clean data. Lead scoring, routing logic and nurture usually belong in Salesforce or your marketing automation tool. Our guide to connecting website analytics to HubSpot or Salesforce pipeline covers how the pieces fit.
Salesforce Web-to-Lead or the API: which should you use?
Web-to-Lead is Salesforce's built-in way to turn a website form into leads: you generate an HTML form in Setup and it posts to Salesforce with your org ID. It's quick and needs no server. The API route sends submissions from your own server code, which gives you validation, error handling and more control.
Web-to-Lead | API from your server | |
|---|---|---|
Setup effort | Low, generated in Salesforce Setup | Higher, needs an integration user and code |
Objects | Leads only | Leads, contacts, campaigns, custom objects |
Error handling | Little visibility when a submission fails | Errors logged and retried |
Volume | Subject to a daily cap set by Salesforce | Subject to your org's API limits |
Duplicate checks | Limited | Look up existing records before creating |
Best for | Simple contact and demo forms | High-volume or multi-step forms |
Salesforce documents a daily limit on Web-to-Lead submissions, and spam counts against it, so check the current limit for your edition in Salesforce's help before launch. If you use Account Engagement (formerly Pardot) or HubSpot synced to Salesforce, the form often goes to that tool first. Our explainer on what Web-to-Lead is goes into the details.
How does Salesforce work with Framer, Webflow and Next.js?
Each platform reaches Salesforce differently. Webflow and Framer forms are built into the visual editor, so getting data out usually means a custom form action, a webhook or an automation tool in between. Next.js lets us post to Salesforce from a server route we control.
Framer | Webflow | Next.js | |
|---|---|---|---|
Common method | Webhook to a small server function, or an embedded form | Custom form action to Web-to-Lead, or a webhook | Server route posting to Web-to-Lead or the API |
Hidden UTM fields | Custom code or a code component | Custom code fills hidden inputs | Read in the app and sent with the form |
Spam protection | Checks in the server function before Salesforce | Webflow's options or reCAPTCHA | Honeypot, rate limits and server validation |
Keeps a copy of submissions | Depends on the method | Not when the action posts to Salesforce | Yes, if we log it |
Our view | Works, with a webhook in between | Works for simple forms | Most control |
Platform form features change, so we confirm the current options in Framer's and Webflow's docs at build time. Our walkthrough of Webflow and Framer forms to Salesforce shows each setup, and Zapier vs Make for website forms covers the no-code middle layer.
How do we set up Salesforce on your site?
We start with your sales process, not the form, and end with a test lead your team has seen arrive.
Map the fields
We agree which website fields map to which Salesforce fields with your Salesforce admin, including picklist values and required fields.
Design the form
Only the fields sales actually uses, clear labels and errors, and a confirmation that says what happens next.
Capture attribution
Hidden fields store UTM parameters, landing page and referrer, carried across pages until the visitor submits.
Connect and protect
Web-to-Lead or the API depending on platform and volume, with spam checks that run before anything reaches Salesforce.
Test end to end
Test leads from each form and campaign link, checked in Salesforce for field values, owner and campaign.
Track the conversion
A named conversion event in your analytics, so marketing reports match the leads in Salesforce.
Our guides to capturing UTM parameters in forms and demo request form fields explain the two steps that most affect lead quality.
What are the common Salesforce form mistakes?
- Picklist mismatches: a website value that doesn't match the Salesforce picklist exactly gets dropped or rejected.
- No attribution: leads arrive with no source, so marketing can't show which campaigns work.
- Spam filling the cap: bot submissions use up Web-to-Lead capacity and bury real leads.
- Silent failures: a changed field or expired credential stops leads arriving, and nobody notices for weeks.
- Too many fields: asking for everything sales might want, when enrichment or the first call can fill gaps.
- Testing in production only: test leads mixed into real pipeline reports.
What does a Salesforce integration cost with us?
Salesforce form setup is part of our website package: $8,000 fixed for up to six pages, then $500 per extra page, including copy, custom design, the build, animation and tested lead capture. Your Salesforce licenses and any automation tools are billed by those vendors.
Moving forms from an old site is scoped on the intro call, and our guide to migrating forms without losing leads covers what to check. If your team uses HubSpot alongside Salesforce, see our HubSpot integration. For demo routing after the form, see Chili Piper. The next step is a free 30-minute call.
















