To connect a website form to your CRM, let the CRM host the form and let the website embed it. The page stores only the form’s link and a title, so adding a question is a CRM change, not a website release. Then set the form to update an existing record when the email matches, and to create a new record only when it does not. On one live form in Coevera (formerly Pipeliner CRM), 49 submissions came from 41 people, and the 8 repeat submissions updated existing contacts instead of creating duplicates. Every website has this form: Contact us, Apply now, Request a call. The goal is always the same. A stranger types their details, and the submission becomes a real CRM record at once, with an owner, a type and a source.
Why do website forms create so much CRM work?
A common first approach is to build the form inside the website and send the data to the CRM’s API. It works on day one. After that, the list of fields lives in two places. Every new question needs a code change and a release, so the questions stop changing. The website also has to handle spam, validation and a stored key that can write to the CRM. The second problem is duplicates. People submit public forms more than once. They lose the confirmation, they are not sure it worked, or they change an answer. If every submission creates a new record, one person becomes several contacts, and each one gets its own follow-up emails.
What setup connects a website form to your CRM cleanly?
In Coevera, an online form lives in the CRM. The website embeds it with a link. Three settings turn each submission into an “upsert”, which means update if the person exists, create if they do not:
- create a record when there is no match
- update the record when there is a match
- autolink, which matches the submitted email against the contact’s email field
A record template on the form sets what a visitor cannot give: a fixed owner, a sales unit, a contact type, and a source field. That source field is what later makes “everyone who applied on the website” a list you can filter.
What it looked like on a live form
The blueprint reads a partner-program application form that has been live since April 2026:
- 49 submissions came from 41 people. With creation only, that would have been eight duplicate contacts. With the upsert, the eight repeat submissions updated an existing contact instead, and every submission was matched to a contact.
- The follow-up process ran soon after. The small process behind the form, one filter and one email, last ran about eight seconds after the form’s last recorded response. That is one observation, not a benchmark.
- The next step was measurable. An embedded form has no recipients, so it shows no response rate. The agreement form that followed was sent to the same 41 people instead of embedded. It went out 144 times in total, and 35 of the 41 people signed. The platform reported a response rate of 85.4%.
The lesson: put the step you need to measure where the decision happens, and send that form instead of embedding it.
When does this approach fall short?
- No response rate and no list of people who did not respond on the embedded form. You rebuild both as reports and a scheduled reminder over the records the form created.
- A required field can go nowhere. On the live form, the privacy checkbox is required, but it is not mapped to the contact. Consent stays on the response record and its PDF, not on the contact. Map it to its own field if you need to report on it.
- Anyone who knows an email address can update that record. For a first contact form this is usually acceptable. For anything commercial, match on a value only the right person has.
- Inside an embedded frame (an iframe), search engines do not see the questions, the form does not work without JavaScript, and the page around the form cannot see what happens inside it.
- The owner is a placeholder. Someone still has to route the new records to a real person.
- Spam protection is set per form. reCAPTCHA is a setting on each form. Turn it on for a public form, because junk submissions become junk records.
For a form behind a button, this is a good trade. For a form that is the landing page itself, a form built into the page may be the better choice, even with the extra maintenance.
Key takeaways
- Host the form in the CRM so questions change without a website release.
- Turn on create, update and email matching together.
- Set owner, type and source in the record template.
- Map consent to its own field.
- Measure at the step where the decision happens.
Frequently asked questions

Comments