How to send only qualified leads as conversions with Google Tag Manager
A step-by-step setup: one custom event, one trigger swap, and what to check in Preview before you publish.
Updated November 11, 2026. 7 minute read.
Most lead generation containers fire the conversion tag on a form submission or a thank-you page view. That counts every submission, real or not. This guide shows how to fire it only for qualified leads, using one custom event and one trigger change. Your tags and conversion actions stay as they are.
The idea in one picture
| Before | After | |
|---|---|---|
| Trigger on your conversion tag | Form submission, or thank-you page view | Custom event qualified_lead |
| What fires it | Anyone who submits | Only leads that passed a quality check |
| Conversion action in Google Ads | Unchanged | Unchanged |
What you need
- Publish access to your Google Tag Manager container.
- Something that decides whether a lead is qualified and pushes an event to the data layer. This guide uses LeadJudge, which pushes
qualified_leadfor real leads andjunk_leadfor the rest. The trigger steps are the same for any tool or script that pushes such an event.
Step 1: add the tag that judges leads
In your LeadJudge dashboard, open Install and download the Tag Manager file for your website. In Tag Manager go to Admin, then Import Container, choose the file, pick your existing workspace, and select Merge with Rename conflicting tags, triggers and variables.
Merge only adds items. You get one tag (the LeadJudge snippet, firing on All Pages), two triggers and five variables. Nothing already in the container is touched. Never choose Overwrite.
Prefer to do it by hand? Create a Custom HTML tag with the snippet from your dashboard, firing on All Pages, and a Custom Event trigger with the event name qualified_lead.
Step 2: switch your conversion tags
Open each tag that reports a lead: the Google Ads conversion tag, the GA4 event, the Meta Lead event, and any others. Remove the current trigger and add LeadJudge - Qualified lead.
That is the whole change. The tags still send the conversion themselves, with the same IDs and the same settings.
Optional: a safety net
If you want tracking to carry on even if the snippet ever fails to load, keep a copy of your old trigger on each tag and add one condition to it: the variable LeadJudge - Snippet version equals undefined. The old trigger then fires only when the snippet is missing.
Step 3: enhanced conversions and advanced matching
If you use enhanced conversions for leads or Meta advanced matching, the qualified event carries the submitted email and phone for exactly this purpose. The import file includes a LeadJudge - User data variable holding those details, which you can use as the source in a User-Provided Data variable.
Step 4: test in Preview before publishing
- Click Preview and open your site.
- Submit your form with a real email address and phone number and a normal message.
- In the event list you should see
qualified_lead, with your conversion tags under "Tags Fired" on that event. - Submit again with obviously fake details. You should see
junk_lead, and no conversion tag fired.
If the second submission uses the same email or phone as the first, it is treated as a duplicate and no event is pushed. Use different details for each test.
Step 5: publish and watch the first week
Submit and publish the container. Then expect two things:
- Reported conversions fall. That is the junk leaving your numbers. Your real leads have not changed.
- Bidding re-learns. Any change to what a conversion means starts a learning period. Avoid other large changes to the campaign for a week or two.
Troubleshooting
| What you see | Likely cause |
|---|---|
No qualified_lead or junk_lead event at all | The snippet tag is not firing on the form page, or the site's domain is not listed in your LeadJudge settings. |
| The event appears but the conversion tag does not fire | The tag still has its old trigger, or the trigger's event name has a typo. |
| Only your first test produced an event | Duplicate detection. Use a different email and phone. |
| A real test was judged as junk | Test words such as "test" in the name or message are treated as tests. Write a realistic message. |
Common questions
Do I need to create a new conversion action in Google Ads?
No. Keep the conversion action you have. Only the trigger on the tag that reports it changes, so your history stays in one place.
Will this work for Meta, Microsoft Ads and GA4 too?
Yes. Any tag in your container can use the same custom event trigger. Switch each tag that reports a lead.
What about forms that redirect to a thank-you page?
The verdict is remembered across the page change. The event fires on the thank-you page once the submission is confirmed and the lead is judged qualified.