THE AIRTOUCH DIGITAL FIELD GUIDE
How to Track Website Leads From the First Click to CRM Follow-Up
When someone contacts your business through your website, can you tell where the inquiry came from, who received it, and what happened next? This guide shows you how to check that entire process.
A practical guide for business owners responsible for incoming leads.
What does it mean to track a website lead?
Tracking a website lead means knowing five things. Where the inquiry came from, whether the form saved it, whether it reached your team, who is responsible for responding, and whether it became a real sales opportunity.
For example, a customer requests a quote and sees a thank-you message. The form entry exists, but its email notification goes to an old inbox. Nobody follows up. The website appears to be working, yet the business never gets a chance to win the job.
That’s why tracking website leads in a CRM is about more than counting submissions. It helps you find the point where inquiries stop moving toward a conversation or a sale.
Start with one test inquiry. Submit the form yourself, then follow it through the website, inbox, and CRM. The first missing or incorrect step tells you what needs attention.
01
Saved submission
The website records the submitted details. A thank-you message alone does not prove the request was delivered to your team.
02
Alert and delivery
The form notifies someone or sends the information to another system. Notifications and external integrations can fail independently.
03
Owned opportunity
The CRM holds a usable lead with an owner, status, and dated next action—not just a name waiting in an inbox.
How a website inquiry should move through your business
A simple process has six checkpoints. You don’t need the same software as another company, but you do need to know that the information reached the next step. Follow a sample request through each checkpoint and check the actual record.
01
Capture where the inquiry started
Keep the original page, form name, and relevant campaign source when available. A lead should be traceable to the marketing that brought the person in.
02
Save the actual entry
Confirm the form system stored the submission. Keep the entry ID and submission time so you can investigate errors and avoid duplicate imports.
03
Verify the handoff
Check that the notification goes to the correct person and the CRM integration actually succeeds. An email alert is not proof the CRM received it.
04
Match or create a sales opportunity
Match an existing contact when appropriate, but preserve a new request as a separate opportunity if it is for a different job or service.
05
Assign an owner and next action
Give the request to someone who can respond. A useful next step sounds like ‘Call about service request today,’ not simply ‘New lead.’
06
Record the real outcome
Track whether the prospect was contacted, qualified, quoted, won, or lost. Those results tell you more than a visitor count.
What should you record about each lead?
The person handling the inquiry needs to know who contacted you, what they need, where the work is located, and what to do next. Your reporting also needs to know which page or campaign brought the request in, when that information is available.
The table below is a starting point for mapping website form fields into a CRM. Some details can be added by your staff after the first conversation, rather than making customers fill out a long form.
| Field | Why it matters | Illustrative example |
|---|---|---|
| Submission ID and time | Trace the original inquiry and spot retries. | Entry 1042 / 10:21 a.m. |
| Name and contact | Give someone a way to respond. | Sample Contact / [email protected] |
| Service requested | Route to the right person. | Commercial HVAC maintenance |
| Service location | Confirm the correct territory. | Winter Park, Florida |
| Landing page / form | Identify what the visitor asked about. | /commercial-hvac / quote-request |
| Marketing source | Understand the visit when attribution data is available. | google / organic |
| Consent or permission | Respect relevant contact and privacy requirements. | Recorded where required |
| CRM owner and next action | Put someone in charge of the response. | Service manager / call today |
| Status and sales outcome | Separate new inquiries from real opportunities. | New → Contacted → Quoted |
Keep private information in the form and CRM. Don’t put a customer’s email address, phone number, name, or message into Google Analytics event parameters or tracked page URLs.
EXAMPLE WORKFLOW — ILLUSTRATIVE, NOT A CLIENT RESULT
What a trackable lead looks like
A facilities manager requests a maintenance quote at 10:21 a.m. The website saves the form entry. The configured CRM connection sends the request to the service team with the customer’s details, location, and requested service.
A manager is assigned the next action, Call about the maintenance quote today. After the call, the record changes from New to Contacted. When a quote is sent, the next action becomes Follow up on proposal.
Now the business can answer who received the request, whether anyone responded, and what stage the opportunity reached. If the form-to-CRM connection fails, the team knows where to investigate instead of assuming the lead was handled.
How do you know which leads are worth your marketing budget?
Look at three different results. Inquiries tell you who contacted the business. Qualified opportunities tell you which requests match the work you want. Won jobs tell you which opportunities actually became customers.
Google Analytics 4 can help measure successful website submissions. Your CRM or sales records are needed to verify qualification, follow-up, and outcomes. Compare the information only when the lead source is recorded reliably. Not every phone call or sale can be attributed to one website visit.
For technical tracking, Google recommends the generate_lead event for a new inquiry. More advanced setups may record later stages using events such as qualify_lead, but only when the business actually verifies those stages. Configure one reliable trigger after a successful submission and check that plugins or tags do not count it twice. Clicking Submit, clicking a phone number, and completing a sale are different actions.
See Google’s guidance on recommended lead events and measuring lead forms if you manage the tracking setup.
Form conversions
Validated form submissions or other specifically defined inbound inquiries.
Qualified opportunities
Requests that actually meet service, timing, budget, and customer-fit criteria.
Won business
Customers and revenue supported by real sales or billing records, with attribution limits acknowledged.
Where can the handoff fail in WordPress?
In Gravity Forms, a confirmation message, an email notification, and a CRM connection are separate steps. The visitor can see a successful confirmation while an email or outside integration still has a problem.
That’s why the test needs to cover more than the visible form. Check whether an entry was saved, whether the right person was notified, and whether the CRM received the information. The same principle applies to other form systems.
Open the form’s Entries list and confirm the request was saved. Check the form’s Notifications settings and delivery. Then inspect the add-on feed or webhook result and look for the matching CRM lead. For troubleshooting, see Gravity Forms’ official confirmations and notifications and add-on feeds guidance.
Four places the process commonly breaks
- The notification goes to an old inbox. Check configured recipients, delivery logs and spam filtering.
- The entry saved, but no CRM lead appears. Check credentials, field mapping, feed status and integration logs.
- A retry creates duplicate opportunities. Keep the original entry ID and decide how repeat requests should be handled.
- The lead exists but nobody calls. Confirm the record has a responsible person and a dated next action.
Run this test before you rely on your lead reports
Set aside a few minutes and submit a clearly labeled test inquiry. Follow it from the website to the person responsible for responding. Check each step rather than assuming an integration works because it’s installed.
- Submit one test request using realistic but fictional contact details.
- Verify that exactly one entry was saved with a submission ID and timestamp.
- Confirm the visitor sees the correct thank-you message or page.
- Check that the notification reaches the intended inbox.
- Find the matching CRM record and verify the service, location and source fields.
- Confirm an owner, status and next action were assigned.
- Inspect GA4 Realtime or DebugView, then reporting, for the intended successful-lead event without duplicates.
- Test one controlled failure or retry and verify that errors are visible and duplicates are handled.
A pass means you observed the result. If the CRM feed was not configured, or you can’t access the destination system, mark the step not verified. That distinction keeps reports honest.
Start by finding the first broken step.
You should be able to take one test inquiry and answer five questions. Where did it come from? Was it saved? Did your team receive it? Who owns the response? What happened next?
If you can’t answer one of those questions, that’s where to focus first. You may need a form notification repaired, a CRM field mapped correctly, or a clear follow-up task—not a new advertising campaign.
Airtouch Digital helps businesses connect lead capture, CRM workflows, and WordPress websites. If you want help reviewing your current lead process, we can start with the existing forms and follow-up steps before recommending changes.
Official setup guides
If you’re responsible for the website or CRM, these resources explain the technical steps behind the process.
Gravity Forms notifications and confirmations — Check where form emails go and what visitors see after they submit.
Gravity Forms add-on feeds — Learn how form entries move into connected services.
Google Analytics recommended events — Understand how successful inquiries can be measured.
Google Analytics key events — Choose which recorded actions matter to your business.
The example in this guide is illustrative. Keep names, email addresses, phone numbers, and private customer details in secure form and CRM systems—not analytics event data.