Connecting HubSpot, Salesforce or Pipedrive to your website: common problems and how to fix them

By Ranjit Bhinge, founder of Blur Studio · Updated · 12 min read

Short answer: When a website form fills in but no record shows up in HubSpot (a customer relationship management tool, or CRM, that stores contacts and deals), Salesforce (a larger business CRM) or Pipedrive (a sales pipeline CRM), the cause is almost always one of eight things, and you can find it by checking in order. First confirm the form submission arrived at all, then the connection and its permissions, then required fields, duplicates, consent settings, daily limits and the connecting user's rights. Each tool has its own traps: HubSpot cannot see forms inside an iframe, Salesforce Web-to-Lead holds back leads past 500 per 24 hours, and a Pipedrive lead must be linked to a person or an organization.

Ranjit Bhinge

A form fill came in, the visitor got a thank-you page, and your CRM shows nothing. This page walks you through why, in the order that finds the cause fastest.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Start with the one question that splits the problem in half: did the form submission arrive anywhere at all? If your website keeps its own log of submissions, look there first. If the submission is in the log but not in the CRM, the problem is the connection. If it is not in the log either, the form itself is broken, and you should start with the forms not sending leads checklist and the spam checks before touching the CRM.

Limits and error names below are from each vendor's own documentation, as of November 2026. Vendors change them, so check the linked pages for your plan.

This page may contain affiliate links from which Blur Studio earns commissions.

The diagnosis order: eight checks, in this order

Work down the list and stop at the first check that fails.

  1. Did the submission arrive? Check your form's own log or the notification email. No record here means the form is the problem, not the CRM.
  2. Is the integration connected, and with write access? Open the connection screen and look for a connected status. Many connections can read data but cannot create records until write permission is on.
  3. Do the required fields match? Each CRM needs certain fields. A form that leaves one blank, or sends it under a different name, gets rejected.
  4. Is a duplicate rule or an existing record in the way? A rule can block the new record, or the tool can quietly add the submission to an older record that you did not look at.
  5. Do consent and lifecycle settings allow it? HubSpot in particular can refuse a submission that lacks processing consent when its legal basis settings are on.
  6. Did you hit a limit? Daily caps and per-second caps return error code 429 (too many requests) or, for Salesforce Web-to-Lead, send leads into a queue.
  7. Does the connecting user have the right to create records? The person who authorised the connection sets what the tool can do. A restricted user means silent failures.
  8. Test in a sandbox first, then live. A sandbox is a practice copy of the CRM. Check each vendor's own sandbox page and pricing page to see whether your plan includes one.

After each change, send one test submission with an email address you recognise. Change one thing at a time.

HubSpot: forms that never arrive, and the errors that explain why

HubSpot can capture forms that were not built in HubSpot. HubSpot's help page for non-HubSpot forms says this works when the HubSpot tracking code is installed on the page and the setting for non-HubSpot forms is switched on. It then creates a contact with the submitted fields and the visit history. A form only appears in the forms list after its first captured submission, which confuses people who look for it before testing.

HubSpot lists nine reasons a submission is not captured. Compare your form against each one.

Why HubSpot misses the formWhat to do
The form is not wrapped in standard form tagsAsk your developer or builder to output a real form element.
The form sits inside an iframe (a page embedded in a page)Use HubSpot's own embed code, or send the data with the forms API instead.
Code is attached to the submit event or button clickTest with the script disabled, or use the API route.
The form appears after the page finished loadingPop-ups and late-loading widgets are missed. Use a form that exists when the page loads, or use the API.
The site is a single-page appThese swap content without a page load. Use the forms API.
Sensitive fields such as card numbersHubSpot skips these on purpose. Never route payment data into a CRM form.
Hidden fieldsHidden fields are not captured, so a hidden source field you rely on will be empty.
The email field is not an email-type inputChange the field type so it is a true email input.
The button is not a standard submit buttonUse a standard submit input.

If you send forms to HubSpot through the forms API (a way for your site's code to hand data straight to HubSpot), the response tells you what went wrong. HubSpot's documentation lists a 400 response with an error type and message. Names you may meet include REQUIRED_FIELD, INVALID_EMAIL, BLOCKED_EMAIL, FIELD_NOT_IN_FORM_DEFINITION, INVALID_HUTK, MISSING_PROCESSING_CONSENT and FORM_HAS_RECAPTCHA_ENABLED. The plain reading of each: a needed field was blank, the email was malformed or on a blocked list, you sent a field the form does not have, the tracking token was invalid, consent was missing, or the form requires a CAPTCHA (a "prove you are human" check) that an API call cannot pass.

Two more details. The tracking cookie token, called hutk in HubSpot's docs, is optional, but without it HubSpot loses the page-view and source history for that contact. And a 429 response means you sent too many requests too fast. HubSpot's usage guidelines give limits per 10 seconds (per app) and per day (per account) for privately distributed apps. Free and Starter allow 100 and 250,000, Professional 190 and 625,000, and Enterprise 190 and 1,000,000.

These apply to apps calling HubSpot's API, and HubSpot's page does not give a separate figure for form submissions, so treat them as a guide. A normal small-business site never gets near them. If you do, a bot is probably hitting your form.

Form builders add their own rules: check yours for whether every mapped field must already exist as a property (a column) in HubSpot.

Salesforce: the 500 per day limit and the quiet queue

Salesforce offers Web-to-Lead, a feature that turns a form on your site into lead records in Salesforce. Salesforce's own FAQ says Professional, Enterprise, Unlimited, Performance and Developer Edition orgs can capture up to 500 leads in a 24-hour period. Extra requests go into a holding queue shared with Web-to-Case (the same idea for support cases), up to 50,000 combined requests, and they are submitted when the limit refreshes. Once that queue is full, new requests are rejected, and your admin is emailed about the first five rejections.

A bot attack, a big ad day or a launch spike can push you over, and queued leads appear later, not now, so a lead can look missing for a day. Keep your own log of every submission as protection.

Other Salesforce causes worth checking, in order of how often they bite:

  • Required fields. A Lead record needs certain standard fields. Open your Lead field settings in Setup and compare them to what the form sends.
  • Restricted picklists. If a field only accepts set values, such as a lead source list, a form that sends a value not on the list is rejected. Salesforce community threads show this as a "bad value for restricted picklist field" message.
  • Duplicate rules set to block. A rule that blocks duplicates also blocks Web-to-Lead records unless you exclude the web lead user. Salesforce community write-ups describe fixing this with a rule condition that skips that user. Confirm in your org before changing a rule.
  • Field access and ownership. The web lead user needs access to every mapped field, and each lead needs an owner.
  • CAPTCHA. If you require reCAPTCHA (Google's human check) and the check fails, no lead is created.

Pipedrive: leads need a person or organization, and a token budget

Pipedrive is a CRM built around a visual sales pipeline. Its Leads API (the way outside tools create leads) requires a title, and its documentation states that a lead always has to be linked to a person, an organization or both. If your connection creates a lead from a form but never creates the person first, the call fails.

Pipedrive's documentation gives no guidance on duplicates for this endpoint. So do not assume it merges repeat submitters. Search for an existing person by email in your connection, or test it with the same address twice.

Pipedrive limits are worth reading because they surprise people. The daily budget is 30,000 base tokens multiplied by a plan factor and by the number of seats. The factor is 1 for Lite, 2 for Growth, 5 for Premium and 7 for Ultimate. Calls cost tokens: fetching one record costs 2, a list costs 20, an update 10, a delete 6 and a search 40. Pipedrive's page does not list the cost of adding a lead, so check its API reference for that endpoint. When the budget is used up, calls return 429 until midnight server time. There is also a burst limit per rolling 2 seconds that differs by plan. Admins get emails at 75 and 100 percent usage. Pipedrive warns that clients that keep sending heavy volume after 429 errors may be shown a block page, so stop and wait.

Made-up sum to show the method: a Lite plan with two seats has a daily budget of 60,000 tokens (30,000 x 1 x 2). If a duplicate search costs 40 and we assume the lead add costs 10 (a made-up figure), one clean submission costs about 50 tokens, so 60,000 tokens would cover about 1,200 submissions a day, before any other tool uses the same budget. Run the same sum for your plan.

Duplicates and fields: the quiet half of the problem

Many "missing lead" reports are not missing at all: the submission landed on an older record.

  • HubSpot matches contacts by email. A form submission is added to the existing contact instead of creating a second one, and companies are matched by primary domain. Companies created through the API are not matched by domain. Imports without a unique identifier can create new contacts. So search by email before you decide a lead is missing.
  • Salesforce behaviour depends on your duplicate and matching rules, which are admin settings. Ask your admin which rules touch Leads.
  • Pipedrive behaviour on this path is undocumented, so treat duplicates as likely until you test.

Fields cause the other half. Make a one-page mapping sheet with three columns: the field name on your form, the field name in the CRM, and the type (text, email, list, date). Fix three things before launch: lists on the form must match CRM list values exactly, including capital letters; phone and email formats must pass the CRM's checks; and anything required in the CRM must be required on the form. If you collect marketing consent, send it in the field your CRM expects and never pre-tick the box. Privacy rules differ by place, so check local law. See data security questions to ask any website or marketing platform.

If your site is built on Ploy

Ploy is an AI website platform that builds and hosts marketing sites and connects them to other tools. Its integrations documentation (updated 30 October 2026) describes the connect steps: choose Connect where it is available, authorise the account you intend, return to the Integrations screen and check for connected status. Authorisation methods and permissions differ by service. Write access lets Ploy's agent create, update and delete data in the service, and it is off by default. Workspace owners and admins can turn it on, and for a connection a member owns, only that member can. So the first thing to check on a quiet connection is that write access was switched on.

For the three CRMs in this page, Ploy's own pages say:

  • HubSpot: a two-way sync of contacts, companies and deals. Ploy's HubSpot page says you pick which workspaces, folders or properties it can read and write, and that you can narrow or revoke access in settings.
  • Salesforce: the docs say it is available on Enterprise and that you should contact your account manager to turn it on. Ploy's Salesforce page describes turning form submissions into leads.
  • Pipedrive: Ploy's Pipedrive page says form submissions can become people and organizations. The docs plan table does not list Pipedrive and tell you to email support@ploy.ai to ask about availability.

Ploy's pricing page sets the plan: HubSpot and Attio from Pro ($300 a month as of November 2026), Salesforce on Enterprise only. The integrations docs list the same tiers and do not list Pipedrive. Some Ploy marketing pages describe integrations without plan limits, so rely on the pricing page, and look at the Connect, Upgrade or Request label on your own account (Upgrade means your plan does not include it). The docs do not describe duplicate handling, field mapping screens, consent flags, sync frequency or sandbox support, so run the test plan below before you trust a connection with live leads. Ploy's forms keep every submission inside Ploy, which gives you the log that step one of the diagnosis needs. See Ploy's integrations and forms, booking and payments for more.

Test plan: six tests with pass and fail rules

Run these in a sandbox if you have one, and otherwise with clearly marked test data you will delete. Use a made-up person such as "Test Lead 1" at an address you control.

TestPassFail
1. Submit a complete formOne new record appears within a few minutes with every field filledNo record, or a field is empty or in the wrong place
2. Submit again with the same emailNo second record, or a second record you expected by designAn unexpected duplicate, or a blocked submission
3. Submit with one optional field blankRecord still createdRejected for a field you thought was optional
4. Submit with a list value that is not in the CRM listHandled as you decided (error to you, or a default)The lead disappears with no alert
5. Submit without ticking consent (if you collect it)Your rule is followed (for example, no marketing flag)The record is marked as consented
6. Submit 10 in a rowAll 10 arrive, or you see queue or limit messagesFewer arrive and nothing tells you why

Also set up one alert that does not depend on the CRM: an email to a shared inbox for every form submission, or a daily count from your form log compared with the CRM count. A mismatch of even one a day is a fail.

When to call for help

  • You pass tests 1 to 3 in a sandbox but live leads still vanish. Suspect a live-only setting such as a duplicate rule or user permission, and ask your CRM admin.
  • You see repeated too-many-requests errors. Stop the retries first. Then ask the vendor to look at your request pattern.
  • You collect data from people in privacy-regulated places such as the EU or UK. Get advice on consent and notices. This page is information, not legal advice.
  • Your site is a single-page app or heavily scripted. A developer should send forms to the CRM through its API, with a log and a retry plan.

How I'd approach this

I would treat the CRM connection as something I own and monitor, not something that works once and stays working. In your first week, do this. Day one: write the field mapping sheet. Day two: run the six tests and fix every fail. Day three: set the shared inbox alert and a weekly count check. Day four: agree what should happen to a repeat submitter. Day five: write a one-page runbook from the diagnosis order above.

Decision rule: pick the CRM your sales team will actually open every day, and let it decide the connection, not the other way round. If you are small, a lighter CRM with fewer required fields causes fewer silent failures. If you are not sure, read CRM for small business first, and Ploy compared with HubSpot if you wonder whether a website platform can stand in for a CRM. If you build on Ploy, check Ploy's plans to see which tier your CRM needs, and note that as of November 2026 both its pricing page and its integrations docs table put HubSpot and Attio on Pro and above and Salesforce on Enterprise. Whatever platform you pick, the leak between tools is a process problem as much as a technical one.

If your setup is more custom than a form-to-CRM link, Blur Studio builds the custom version: AI agents that use your business knowledge, CRM and calendar connections, finishing a half-built flow, and ongoing care. You can see what that includes, with no pressure to buy.

Questions people ask

Why does my website form not create a contact in HubSpot?

The most common reasons are a form inside an iframe, a form that loads after the page finishes, a script attached to the submit button, a single-page app, hidden fields, an email field that is not an email-type input, or the tracking code not being installed. HubSpot lists nine reasons on its non-HubSpot forms help page. Check those first, then check that your API call does not return a 400 error.

How many Web-to-Lead leads can Salesforce take per day?

Salesforce's own FAQ says you can capture up to 500 leads in a 24-hour period. Extra requests wait in a holding queue shared with Web-to-Case, up to 50,000 combined, and are submitted when the limit refreshes. Once the queue is full, new requests are rejected. Keep your own log of submissions so you can reconcile a busy day.

Why does Pipedrive reject a lead I send from my form?

Pipedrive's Leads API requires a title, and a lead has to be linked to a person, an organization or both. If your connection sends only a title, the call fails. Create or find the person first, then add the lead linked to them.

Does the HubSpot form sync create duplicates?

HubSpot matches contacts by email, so a repeat submission is normally added to the existing contact. Companies are matched by primary domain, but companies created through the API are not matched that way, and imports without a unique identifier can create new contacts. Search by email before you decide a lead is missing.

Does Ploy connect to HubSpot, Salesforce and Pipedrive?

Ploy has pages for all three. Its docs say HubSpot is a two-way sync of contacts, companies and deals, and Salesforce is available on Enterprise through your account manager. The docs table does not list Pipedrive. The pricing page puts HubSpot and Attio on Pro and above ($300 a month as of November 2026) and Salesforce on Enterprise, and the docs agree. Check the label on your own account, and see Ploy's integrations.

What does error 429 mean when sending leads to a CRM?

It means too many requests. HubSpot limits requests per 10 seconds and per day by plan, and Pipedrive uses a daily token budget based on plan and seats, with a short burst limit as well. Stop retrying, wait for the window to reset, and check whether a bot is filling your form.

Should I test the CRM connection in a sandbox?

Yes, where one exists. A sandbox is a practice copy of the CRM. Check each vendor's sandbox and pricing pages to see whether your plan includes one. If you have no sandbox, test with clearly marked fake contacts and delete them after.

How do I know a lead was lost between the form and the CRM?

Keep a second record that does not depend on the CRM, such as a notification email to a shared inbox or a count from your form log. Compare that count with the CRM each week. Any mismatch is a signal to run the diagnosis order, and the guide to connecting a website to a CRM covers the setup side.

More in this topic: Websites: fixing migration, DNS, forms, speed and CRM problems (6 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…