Integrating a CRM with your website, reliably
How to connect your website to a CRM so enquiries never get lost: what data to send, queues and retries, linking without duplicates and syncing status back.
In short
Integrating a CRM with your website means every enquiry from the site becomes a CRM record by itself – no re-typing from an inbox. It works reliably when records are sent through a queue with retries, linked by ID rather than by email, a repeated send never creates a duplicate, and a CRM outage never stops the website's form from working.
Key takeaways
- In a 2011 HBR study, firms that tried to contact a lead within an hour were nearly 7 times as likely to have a meaningful conversation with a decision maker as those that tried later.
- Send only what sales needs: the GDPR's data minimisation principle requires data to be limited to what is necessary for the purpose.
- The website form must succeed even when the CRM is down: the enquiry is saved and passed on through a queue with retries.
- Don't match customers by email – addresses change and duplicates appear. Link records by ID.
- Decide which system owns each field, or the two systems will keep overwriting each other.
Why, and what travels
What integration means, why speed matters and which data to send.
What CRM–website integration is
- CRM–website integration
- An automatic link through which data from your website's forms, orders or sign-ups reaches your customer relationship management system (CRM) as contacts, leads or tasks – and sometimes comes back, for example as the status of an enquiry.
Without integration the path usually looks like this: an enquiry arrives by email, someone re-types it into the CRM when they have time, and the account manager hears about it later. Every step adds delay and a chance to lose something. It is a typical process worth automating first.
Why the time an enquiry spends in transit matters
~7×
How much more likely firms that tried to contact a lead within an hour were to have a meaningful conversation with a decision maker than firms that tried even an hour later, according to a 2011 HBR study of 1.25 million leads.
Source: Harvard Business Review, 20261
42 hours
The average response time among the 2,241 US companies HBR audited (of those that responded within 30 days); 23% of companies never responded to the test enquiry at all.
Source: Harvard Business Review, 20261
The study is old and US-based, but its point hasn't aged: leads go cold quickly, and the biggest delay is often not in the reply but in the path to the person who should reply. A CRM integration cuts that path to seconds.
What data to send
Start by asking what the account manager needs to reply well. Usually that is the contact details, what the person wants, how urgent it is and where they came from. Anything sales doesn't need stays out of the CRM.
| On the website | In the CRM | Note |
|---|---|---|
| Name, email, phone | Lead contact | Only what is needed to reply |
| Company | Company name | Optional if you also sell to individuals |
| Service or package | Enquiry type | Lets you assign an owner straight away |
| Description and budget | Enquiry note | The account manager doesn't ask the same thing twice |
| Source (page, campaign) | Source field | Shows which channels bring enquiries |
| Enquiry ID | External ID | Prevents duplicates when a send is retried |
This isn't only about convenience. Article 5(1)(c) of the GDPR sets out the data minimisation principle: personal data must be adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed.
In practice: don't send fields to the CRM “just in case”, and don't keep attachments longer than needed. The less personal data travels between systems, the fewer places you have to protect it.
How to do it reliably
Four principles that separate a working integration from one that quietly loses enquiries.
1. Send through a queue with retries
The simplest integration sends the enquiry to the CRM the moment the visitor clicks “Send”. If the CRM is slow or down at that moment, the visitor sees an error and the enquiry disappears. A more reliable approach is to save the enquiry on your side first, confirm it to the visitor straight away, and send it to the CRM through a queue.
- A failed send is retried with an increasing interval, not immediately over and over.
- Temporary errors (the CRM doesn't respond, it is overloaded) are retried; errors caused by invalid data are not – they are shown to a person.
- After several failures an alert is sent, and every attempt stays in the log.
2. Link records by ID, not by email
The most common mistake is looking up the customer in the CRM by email address. It works until someone changes the address in one of the systems. Then the next sync can't “find” the customer and quietly creates a second one. A few months later the CRM is full of duplicates and the history is split.
Matching by email
- The customer changes their address in their website account
- The sync can't find them in the CRM
- A second contact is created and the history is split
- A retried send creates yet another record
Linking by ID
- Every record has a CRM ID stored in a link table
- An address change updates the same contact
- The history stays in one place
- A retried send with the same enquiry ID duplicates nothing
The other half of this principle is idempotency: every enquiry has its own ID, and when the CRM side receives the same ID a second time, it doesn't create a new record. That makes retries after an error safe.
3. Decide which system owns each field
When data flows both ways, two systems can start overwriting each other. The answer isn't “which system matters more” but assigning an owner to each group of fields. For example, the website owns the enquiry content and source, while the CRM owns the sales stage, proposals and invoices.
Sending status back is useful when the customer has an account or a portal: they see that the enquiry is being reviewed or the proposal has been sent, and you see which enquiries turned into customers. This link usually works through notifications (webhooks) sent by the CRM, which must be signed and refused when no secret is configured.
4. Don't let the CRM become the critical path
Your website form, checkout or sign-in shouldn't depend on whether the CRM is working at that moment. If the CRM is being updated or has a problem, enquiries build up in the queue and go through once it is reachable again. The visitor never notices.
Check before launch
- Switch off the CRM connection and submit the form – does the visitor still get a confirmation?
- Switch it back on – does the enquiry appear in the CRM once, not twice?
- Change a contact's email – is the same record updated?
- Break the access token – does anyone get an alert?
The most common CRM integration mistakes
- The form sends data straight to the CRM, so on failure the visitor sees an error and the enquiry disappears.
- Customers are looked up by email, so duplicates appear after an address change.
- A retry after an error creates a second lead because there is no enquiry ID.
- Both systems can change the same fields, so a later sync overwrites the account manager's corrections.
- Everything the form collects goes into the CRM, including fields sales doesn't need.
- Nobody gets an alert when an access token expires – the integration “works” but passes nothing on.
All of these mistakes have one thing in common: while everything works, you can't see them. They surface only when a customer calls to ask why nobody replied, or when the same person appears three times in a CRM report.
How to monitor the integration after launch
An integration isn't a one-off job. The CRM gets updated, fields get renamed, access tokens expire. So after launch you need three things: an alert when sending fails several times in a row, a log showing every attempt, and a simple periodic check that the number of enquiries on the website and in the CRM match.
For our automations this is standard: 3 automatic retries, an alert on failure, an execution log and monitoring of critical processes. Incident response follows your maintenance plan; without a plan, incidents are handled as separate work.
Three ways to connect a website to a CRM
| Method | How it works | When it fits | What to watch |
|---|---|---|---|
| CRM form on the website | A form generated by the CRM is embedded | A simple enquiry, one CRM | Limited design; hard to add your own logic |
| Automation tool | n8n or Make passes data between the form and the CRM | Most websites and multiple systems | Error handling and monitoring must be set up |
| Coded integration | The website or system code talks to the CRM's API | Accounts, portals, two-way sync | Higher up-front cost, but full control |
Most CRMs have lead management: Perfex CRM, for example, shows leads on a stage board, lets you add notes and convert them into customers. The integration's job is to get the website enquiry onto that board by itself, with every field it needs.
What it costs and where to start
An integration through an automation tool is part of our process automation work and is priced on scope: it depends on the number of forms, systems and directions. If the integration is part of a larger system or client portal, it is a web platform project from €4,900. Either way, the price, scope and timeline are in writing before work starts.
What to prepare before the call
- Which CRM you use and whether it has an API
- Which website forms need to reach the CRM
- Which fields the account manager needs to see
- Whether status needs to come back to the website or portal
- Who should get an alert if the link breaks
If the CRM and website are only part of a bigger question – how to connect all your tools – read when a business needs a custom system. And if you want to start now, describe your forms and CRM in an enquiry. We reply within 1 business day.
Methodology
- Date
- Sample
- HBR: 2,241 US companies (response-time audit) and 1.25 million leads from 42 companies (effect of response speed)
- Criteria
- Response-speed data – from the HBR article (March 2011), accessed 2026-10-01
- The data minimisation principle – GDPR Article 5(1)(c)
- Integration principles – the architecture of our own website–CRM link, described in general terms
- Limitations
- The HBR study was carried out in the US more than a decade ago; it shows a direction, not the exact effect on your company. This is not legal advice on the GDPR.
Frequently asked questions
Will the CRM integration work if the CRM is temporarily down?
It should. A reliable integration saves the enquiry on the website side first and sends it to the CRM through a queue with retries, so the visitor gets a confirmation and the enquiry goes through once the CRM is reachable again.
Why shouldn't customers be matched by email?
Because addresses change. Once one is changed in one system, the next sync can't find the customer and creates a duplicate. Linking by CRM ID doesn't have this problem.
Which CRM should we choose?
Almost any CRM with an API can be integrated. What matters more is whether it fits your sales process and whether your team will use it. We use Perfex CRM ourselves.
How much does a CRM integration cost?
Through an automation tool it is priced on scope: it depends on the number of forms, systems and directions. If the integration is part of a larger system, it is a web platform project from €4,900.
What happens when the integration breaks?
The failed send is retried, an alert is sent and the execution log keeps a record. Incident response follows your maintenance plan; without a plan, incidents are handled as separate work.
Sources and methodology
- Harvard Business ReviewThe Short Life of Online Sales Leadsaccessed
- gdpr-info.eu (Regulation (EU) 2016/679)Art. 5 GDPR – Principles relating to processing of personal dataaccessed
- Perfex CRMPerfex CRM – featuresaccessed