A button click tells you someone tried to contact you. It does not tell you whether the form was accepted. If your reporting treats both as a lead, your conversion numbers can look healthier than your inbox.
Start with a precise definition
Write down what counts as a lead before opening GTM. For a contact form, the lead event should follow a confirmed success response or confirmation page. Track a form attempt separately so you can see where people run into validation or delivery issues.
Trace one test submission
- Open GTM Preview and your website in a fresh session.
- Submit the form with a clearly labeled test message. Confirm that the page shows a real success state.
- Look for the form attempt and lead success events in the data layer. Success should occur once, after the form accepts the submission.
- Check whether the GA4 event tag fires when analytics consent is granted and stays blocked when it is denied.
- Verify the event in GA4 DebugView, then check that the form notification reaches its intended inbox.
Check the details you send
Useful event details can include a form identifier, page location, and a general lead source. Leave names, email addresses, and message text out of GA4 event parameters. Test the form on mobile and desktop, and make sure a reload cannot count the same lead twice.
Keep a short QA record
Record the test date, the consent choice, the page, the event sequence, and whether the notification arrived. If one step fails, you can tell whether the issue belongs to the form, email delivery, the data layer, GTM, or GA4.
If your team needs help defining and testing this journey, explore our digital analytics service or campaign measurement service.