How to Track Quote Requests on Your Website
Learn how to track quote requests on your website: form events, WhatsApp and phone clicks, and how to see which source actually brings in real buyers.
By Downway Team 3 min read
To track quote requests on your website, turn three actions into measured events: form submissions, WhatsApp clicks and phone clicks. Once these are set up in Google Tag Manager and Google Analytics 4, you can see which channel each request came from. The setup takes a few hours and changes how you decide where to spend.
Before you start: what you need in place
- A Google Analytics 4 property connected to the site.
- A Google Tag Manager account with the container installed on every page.
- Access to edit the site, or to ask whoever maintains it for a small change.
- A thank-you page shown after the form is submitted, if possible.
If any of these is missing, fix it first. A thank-you page, for instance, is the most reliable way to count submitted forms and avoids false counts.
Step-by-step tracking setup
- Define what counts as a quote request: a submitted form, a WhatsApp click and a phone click. Give each event a consistent name, such as quote_form, click_whatsapp and click_phone.
- In Tag Manager, create one trigger per action: a view of the thank-you page, clicks on links containing wa.me or api.whatsapp.com, and clicks on links starting with tel:.
- Create a GA4 event tag for each trigger using your chosen names. Add a parameter recording the page where the click happened.
- Use Tag Manager's preview mode to test: submit the form, click each button and confirm every event fires exactly once.
- In Analytics, mark these events as key events so they show up in conversion reports.
- Publish the container and check real-time reports to confirm events arrive.
Finding out where each request came from
With events marked, the acquisition report shows the source of each conversion: organic search, ads, social, email or direct. For ads, add UTM parameters to your links, such as utm_source and utm_campaign, so Analytics can separate each campaign.
One refinement: forms keep the origin better if you add hidden fields that store source and campaign at the moment of submission. The email your sales team receives then already says where the lead came from.
Phone calls without tracking numbers
A tap on a number from a mobile phone is recorded, but a call made by typing the number from a desktop is not. If you get many requests by phone, a practical fix is to ask How did you find us? on every call and note the answer. Dynamic call-tracking numbers exist, but they only pay off at high volume.
For paid campaigns, a clean conversion setup matters even more. See how it connects to our paid ads work.
What to measure once it is running
- Number of requests per channel each month.
- Conversion rate: requests divided by visits from each source.
- Pages that generate the most requests, to know what to reinforce.
- Requests that became proposals and sales, logged by your sales team.
The last item closes the loop. A channel that brings many requests but few customers is worth less than one that brings a few qualified ones. Ask sales to note, in a spreadsheet or CRM, the source of every closed deal.
Next step: review the tracking every three months, because site changes such as a new form can silently break an event.
Frequently asked questions
Do I need a developer to track the form?
Often not. If the form leads to a thank-you page, Tag Manager can count visits to that page as a conversion.
How do I know if the WhatsApp event fires twice?
Use Tag Manager's preview mode and Analytics real-time view. Each click should produce a single event.
Does tracking work with ad blockers?
Partly. Some browsers and extensions block analytics scripts, so your numbers will usually sit slightly below reality.