Integrate HubSpot CRM with Your B2B Website Easily

When you integrate Salesforce with your B2B website correctly, every qualified submission creates a Lead or Contact in Salesforce, triggers the right assignment rule, and carries the source, campaign, and page data that allows the sales team to prioritize correctly. Before integration, leads arrive via email, get manually entered, and arrive without attribution data or lead score.

The gap between these two states is configuration, not development complexity, but the configuration decisions made at setup determine how useful the data is for months afterward.

Key Takeaways

• Web-to-Lead is the fastest integration path but has limits Salesforce's native Web-to-Lead creates Lead records directly without an API, but has a 500 leads-per-day limit and limited field customization.
• The Salesforce API route gives full control but requires a developer connecting custom forms via the REST API allows any object type and any automation trigger, but requires ongoing maintenance.
• Lead assignment rules must be configured before the first submission Salesforce does not route leads automatically; every lead lands in the default queue without assignment rules set in advance.
• Campaign tracking requires Campaign Member records, not just lead source accurate multi-touch attribution requires web submissions to create Campaign Member records in addition to Lead records.
• Duplicate management is a pre-launch requirement without a deduplication rule, every form submission from a returning visitor creates a new Lead record.
• Pardot changes the integration architecture entirely if Pardot is in the stack, forms should sync to Pardot, not directly to Salesforce; mixing the two without a deliberate decision creates attribution problems.

B2B Website Development

Websites That Win Enterprise Clients

We build high-converting B2B websites with modern no-code technology—designed to generate leads, build trust, and support your sales team.

Let's talk

How Does Salesforce Integration with a B2B Website Actually Work?

Salesforce integration operates on two mechanisms: record creation (a web form submission creates a Lead, Contact, or custom object record) and activity tracking (a visitor's page behavior is logged against their Salesforce record via a tracking tool). The automation that follows both mechanisms depends entirely on the record type and field values at the moment of creation.

The object model matters: most B2B websites create Lead records on first form submission. Some organizations create Contacts directly if they use Person Accounts or do not use the Lead object. Know which model your Salesforce instance uses before configuring the form.

Automation in Salesforce is triggered by record creation or update, which means the integration must create the right record type with the right field values for any subsequent workflow or assignment rule to fire correctly.

For a development-side view of how CRM integration fits into a B2B website build, CRM integration in B2B website builds covers the architecture decisions that affect everything downstream.

Which Integration Method Is Right for Your Setup?

The right integration method depends on your lead volume, technical resource, and the object types you need to create. Web-to-Lead suits simple setups with Lead-only requirements. The REST API suits enterprise-grade integrations. Middleware suits interim or low-volume setups. Pardot suits organizations where marketing automation is already in the stack.

Method 1, Web-to-Lead (native Salesforce): go to Salesforce Setup → Web-to-Lead → Create Web-to-Lead Form. Salesforce generates an HTML form with a hidden Organization ID. Paste it into your CMS. All submissions create Lead records automatically. Limit: 500 leads per day; no support for Contacts, Opportunities, or custom objects; limited styling control.

Method 2, Salesforce REST API (custom integration): your form POSTs to the Salesforce REST API using a connected app with OAuth 2.0. Full control over object type, field values, and related record creation. Requires a developer and a connected app setup. This is the correct method for enterprise-grade integrations.

Method 3, Middleware (Zapier, Make, Workato): connect form submissions to Salesforce via automation middleware. Fastest to set up for non-developers; adds dependency on middleware uptime and latency. Suitable for lower-volume or interim setups, not production enterprise deployments.

Method 4, Marketing automation integration (Pardot / Marketing Cloud Account Engagement): if Pardot is in the stack, forms should connect to Pardot, which syncs to Salesforce, not the other way around. Mixing direct Salesforce form submissions with Pardot tracking creates duplicate and attribution problems.

If the decision between Salesforce and HubSpot as the primary CRM is still open, the HubSpot vs Salesforce integration decision covers the criteria that determine which fits the website and sales workflow better.

How Do You Set Up Web-to-Lead Correctly?

Web-to-Lead is a five-step configuration process. The most common failure points are missing hidden fields for attribution, no assignment rule configured before go-live, and the return URL left as Salesforce's default success message rather than your site's thank-you page.

Step 1, Enable Web-to-Lead: Salesforce Setup → Feature Settings → Marketing → Web-to-Lead → Enable.

Step 2, Create the form: Setup → Web-to-Lead → Create Web-to-Lead Form. Select fields to include. Map every visible field to the correct Salesforce Lead field name. Add hidden fields for lead_source, Campaign_ID, and any UTM parameters you want captured as custom fields.

Step 3, Set the return URL: define where the visitor is redirected after submission. This should be your thank-you or confirmation page, not Salesforce's generic success message.

Step 4, Paste the generated code into your CMS: replace the default Salesforce styling with your site's CSS. The HTML structure must remain intact, particularly the hidden oid field that contains your Salesforce Organization ID.

Step 5, Configure the default assignment rule: every Lead created via Web-to-Lead must have an assignment rule in place. Without one, the lead goes to the default owner, typically the system administrator. Set up Lead Assignment Rules in Salesforce Setup before going live.

Testing: submit a test lead with a non-company email address. Verify it appears in Salesforce with the correct field values, owner assignment, and any triggered workflows before activating the form for real traffic.

How Should Enterprise-Specific Salesforce Configurations Be Handled?

Enterprise Salesforce integrations require the REST API, Web-to-Lead cannot create non-Lead objects, match submissions to existing Account records, or handle multi-step form flows. These requirements make Web-to-Lead insufficient for most enterprise B2B websites.

Custom object creation: enterprise B2B websites often need to create Opportunities or custom objects directly from the website form, not just Lead records. This requires the REST API.

Account matching on submission: enterprise integrations typically match a submitted email domain to an existing Account record and link the new Lead or Contact to it automatically. This requires SOQL queries via the REST API and cannot be done with Web-to-Lead.

Multi-step form flows: complex enterprise qualification forms (collecting company size, use case, tech stack) should pass data progressively, not in a single long form. This requires a multi-step form builder connected to the API, with partial submission handling.

Sandbox testing requirement: any API-based integration must be built and tested against a Salesforce Sandbox before touching the production instance. Skip this and the first real submission may corrupt live data.

For how the website should function alongside enterprise deal cycles more broadly, B2B website for enterprise sales covers the requirements specific to that context.

How Do You Set Up Lead Attribution After Integration?

Accurate lead attribution in Salesforce requires three things: a consistently populated Lead Source field, Campaign Member records for multi-touch attribution, and custom UTM fields on the Lead object. None of these happen automatically, each requires deliberate configuration before the first submission goes live.

Lead Source field: the Salesforce Lead Source picklist should be populated on every Web-to-Lead submission, pass it as a hidden field value (e.g. "Organic Search", "Paid Search", "Webinar"). Agree on a canonical list of values with the sales team before launch. Inconsistent values make reporting unreliable.

Campaign Member records for multi-touch attribution: creating a Campaign Member record that links the Lead to a Salesforce Campaign is the correct way to track campaign influence. A Lead Source field only captures first-touch, Campaign Member records allow multi-touch analyzis.

UTM parameters as custom Lead fields: create custom text fields on the Lead object for utm_source, utm_medium, utm_campaign, utm_content, and utm_term. Pass these as hidden form fields on every web submission. This enables attribution by campaign, channel, and ad creative inside Salesforce.

Salesforce and GA4 do not share attribution natively, each maintains its own session and conversion model. For a guide to configuring GA4 alongside Salesforce for coordinated lead attribution, GA4 lead attribution setup covers the configuration that makes both systems useful simultaneously.

How Do You Secure the Salesforce Integration?

A Salesforce website integration requires OAuth 2.0 for API connections, minimum-scope Connected App permissions, CAPTCHA on Web-to-Lead forms, and credential storage in environment variables, not in the site's source code or CMS settings.

OAuth 2.0 for API integrations: never use username/password authentication for a web-to-Salesforce API connection. Use a Connected App with OAuth 2.0 (JWT Bearer Flow for server-to-server). This limits access scope and allows token revocation without changing credentials.

Connected App permission scoping: grant the minimum required API access. A web-to-CRM integration typically needs access only to the Lead and Campaign Member objects, not to the full Salesforce instance.

Web-to-Lead token protection: the Organization ID embedded in Web-to-Lead HTML is publicly visible, Salesforce accepts this by design, but it means spam submissions are possible. Implement CAPTCHA (Google reCAPTCHA v3) on Web-to-Lead forms to reduce spam lead volume.

API key and credential management: API credentials for Salesforce integrations should be stored in environment variables or a secrets manager such as AWS Secrets Manager or Vault. Never hardcode them in the site's source code or store them in a CMS settings page that multiple users can access.

For the broader security standards that apply to B2B websites handling CRM data, B2B website security covers what is expected at enterprise and growth-stage companies.

Conclusion

Integrating Salesforce with a B2B website is primarily a configuration and data architecture project. The method you choose, the object type you create, the assignment rules you set, and the attribution fields you map all compound over time, get them right at setup and the integration serves the sales team for years.

Identify your Salesforce object model first: do you use Leads, or do you convert to Contacts and Accounts immediately? Then choose the integration method based on volume and technical resource. Configure assignment rules before the first submission goes live, not after.

B2B Website Development

Websites That Win Enterprise Clients

We build high-converting B2B websites with modern no-code technology—designed to generate leads, build trust, and support your sales team.

Let's talk

Need the Salesforce Integration Built Right from Day One?

Salesforce integration mistakes are not obvious at launch, they surface weeks later when leads are landing in the wrong queue, attribution fields are empty, or duplicate records are accumulating faster than the sales team can clean them up.

At LowCode Agency, we build Salesforce CRM integrations as part of the B2B website development engagement, handling object mapping, assignment rules, attribution tracking, and API security correctly before launch. See what that produces in practice in our client work.

• Object model assessment we identify whether your Salesforce instance uses Leads, Person Accounts, or a custom object model before any form configuration begins.
• Integration method selection Web-to-Lead, REST API, or middleware recommended based on your lead volume, technical resource, and object requirements.
• Web-to-Lead setup and testing correct hidden fields for attribution, return URL configuration, and verified submission testing before go-live.
• Enterprise API integration REST API connections with OAuth 2.0, connected app setup, and Sandbox testing before touching the production instance.
• Lead assignment rule configuration assignment rules configured before the first submission, with routing logic agreed with the sales team in advance.
• UTM and attribution field setup custom Lead object fields for all UTM parameters, Campaign Member record creation, and canonical Lead Source value list agreed before launch.
• Security configuration OAuth 2.0 for API connections, minimum-scope permissions, reCAPTCHA on Web-to-Lead forms, and credential storage in environment variables.

We have built 350+ products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku.

Get in touch to discuss your Salesforce integration requirements.