Website traffic tells you how many people visited your site. Conversion tracking tells you whether those visitors did anything valuable. For a service business, that may mean submitting an enquiry form. For an eCommerce store, it could be completing a purchase.
For a SaaS company, it might be starting a trial, creating an account or booking a demo. This is why GA4 conversion tracking is one of the most important parts of a useful analytics setup. However, Google Analytics terminology has changed.
In GA4, an important action inside Analytics is now called a key event. If that same action is used to measure or optimise advertising performance in Google Ads, Google Analytics conversion tracking, it can become a conversion. Google’s current measurement flow is:
Event → Key Event → Conversion.
Understanding that difference makes the rest of the setup much easier.
What Is GA4 Conversion Tracking?
GA4 tracks user interactions as events.
An event can represent actions such as:
- viewing a page
- clicking a link
- submitting a form
- creating an account
- adding a product to cart
- completing checkout
- making a purchase
When an event represents something particularly important to your business, you can mark it as a key event.
Google Analytics then gives that action additional prominence in reporting so you can understand which users and marketing channels are driving it.
If you also use Google Ads, selected Analytics events or key events can be turned into Google Ads conversions for campaign reporting and bidding.
Events vs Key Events vs Conversions
This is the most important concept to understand before setting anything up.
Event
An event records an interaction.
Examples:
page_view
scroll
click
form_submit
Key Event
A key event is an Analytics event that represents an important business action.
Examples:
generate_lead
sign_up
purchase
Conversion
A conversion is an important action used for advertising measurement and optimisation, particularly across Google Ads and Analytics.
Google now aligns conversion measurement more closely between Google Ads and Google Analytics.
You should therefore avoid marking every small interaction as a key event.
A visitor scrolling down a blog may be useful behavioural information.
A visitor submitting a genuine enquiry is usually much more important to the business.
What Should You Track as a Key Event?
Start with actions that GA4 Conversion Tracking directly represent progress toward a business goal.
For a lead-generation website, this may include:
- enquiry form submitted
- quote requested
- consultation booked
- demo requested
- account created
For eCommerce:
- purchase
- checkout completed
- possibly high-value funnel actions such as begin checkout
For SaaS:
- account signup
- trial started
- demo booked
- subscription purchased
Google recommends using predefined recommended event names where they fit your use case. Examples include generate_lead, sign_up, purchase, begin_checkout and refund.
Using Google’s recommended naming conventions can also unlock more useful predefined reports and integrations.
Before You Start
Before configuring conversions, make sure your GA4 Conversion Tracking foundation is working correctly.
You should already have:
- a Google Analytics account
- a GA4 property
- a web data stream
- the Google tag installed
- access to your website or Google Tag Manager
Google Analytics can be installed directly with the Google tag or managed through Google Tag Manager.
Do not begin by creating key events if the basic Analytics tag itself is not collecting data correctly.
Step 1: Confirm That GA4 Is Collecting Data
Open your GA4 property and visit the website yourself.
Then open the Realtime report.
GA4’s Realtime report shows events received from users during the previous 30 minutes.
You should be able to see activity such as:
page_view
and other automatically collected events.
If nothing appears, fix the base tracking installation first.
Step 2: Decide What Business Action You Want to Measure
This step is often skipped.
Do not start by asking:
“What can GA4 track?”
Ask:
“What action matters to our business?”
Suppose you operate a digital agency.
Your most important website action may be:
Contact form successfully submitted
Your measurement plan might therefore be:
User submits contact form → generate_lead event → mark as key event
This is much clearer than tracking every button click as a conversion.
Method 1: Track a Thank-You Page Without Code
A simple lead-generation website may redirect visitors to a dedicated confirmation page after submitting a form.
For example:
/thank-you/
In this situation, GA4 Conversion Tracking can create a new event based on a page-view condition.
Google’s current tutorial recommends using the generate_lead recommended event when someone reaches a confirmation page after submitting a lead form.
Setup
Open:
Admin → Data display → Events → Create event
Create an event such as:
generate_lead
Choose Create without code.
Use the existing event:
page_view
Then define the confirmation-page URL as the condition.
After creating it, mark the event as a key event.
This approach can work well when every successful form submission reaches a unique confirmation page.
Important
Do not fire a lead event simply because someone visits the contact page.
That measures interest, not a completed lead.
The event should fire only after the successful action.
Method 2: Use GA4 Enhanced Measurement
GA4 can automatically track several interactions through Enhanced Measurement.
Depending on your configuration, this can include activities such as:
- scrolls
- outbound clicks
- site search
- video engagement
- file downloads
- form interactions
GA4 Conversion Tracking currently provides form_start and form_submit enhanced-measurement events for form interactions.
This can make basic tracking easier.
However, test your forms carefully.
Different website builders, AJAX forms and custom JavaScript implementations may behave differently.
Do not assume that every form_submit event represents a successful lead without verifying it.
Method 3: Set Up Events With Google Tag Manager
Google Tag Manager gives you more control when you need to track actions such as:
- button clicks
- successful AJAX form submissions
- phone-number clicks
- WhatsApp clicks
- custom interactions
- specific downloads
Google’s current Tag Manager process uses a Google tag for the base Analytics configuration and GA4 Conversion Tracking Event tags for additional events.
Typical GTM Setup
You create:
1. A trigger
This defines when the action happens.
For example:
Contact form success.
2. A GA4 Event tag
This defines the event sent to Google Analytics.
For example:
generate_lead
3. Event parameters when useful
For example:
form_name
lead_type
page_location
Then test everything before publishing the Tag Manager container.
A Note About Google Tag Manager in 2026
Google updated the Google tag and Google Tag Manager interface in August 2026.
The newer experience centralises more tag settings and simplifies container management. Existing functionality remains available, but the interface may look different from older tutorials or screenshots you find online.
Google also notes that the old GA4 Conversion Tracking Configuration tag has effectively become the Google tag, while existing GA4 Event tags continue to work.
So if you follow an old tutorial that says:
“Create GA4 Configuration Tag”
your current interface may not look exactly the same.
Step 3: Mark the Event as a Key Event
Once the event exists, mark it as a key event.
Go to:
Admin → Data display → Events
Find the relevant event and select the star / key-event option.
For example:
generate_lead
After it has been marked, GA4 Conversion Tracking begins treating future occurrences as key events.
This does not retroactively convert old event data into key-event data.
Google also allows standard properties to mark up to 30 events as key events, while Analytics 360 properties allow more.
That is another reason not to mark every interaction as important.
Step 4: Test the Event in Realtime
Now perform the action yourself.
For example:
- Open your website.
- Fill in the contact form.
- Submit it.
- Open GA4 Realtime.
Check whether generate_lead appears.
Google says Realtime can be used to confirm recent event and key-event activity within minutes.
If the event does not appear, do not assume the configuration is complete.
Troubleshoot it before launching campaigns.
Step 5: Use DebugView for Detailed Testing
For deeper troubleshooting, use GA4 DebugView.
DebugView shows events generated by a specific debugging device in real time.
It is useful for checking:
- event name
- event sequence
- event parameters
- duplicate events
- missing events
Google recommends using DebugView when verifying new recommended events.
If you use Google Tag Manager, Preview / Tag Assistant can help enable debugging while you test your implementation.
Step 6: Check Standard Reports Later
Do not panic if the event appears in Realtime but not immediately in your standard reports.
Google notes that standard event reporting may take up to 24 hours to fully populate.
Realtime and DebugView are better tools for immediate setup verification.
Standard reports are better for ongoing performance analysis.
Setting Up Lead Tracking Properly
For lead-generation websites, one successful form submission should ideally produce one meaningful lead event.
Google currently recommends a fuller lead-funnel event structure for businesses that manage leads beyond the original submission.
This includes events such as:
generate_lead
qualify_lead
working_lead
close_convert_lead
These recommended events can populate GA4’s lead-generation reporting and help connect marketing acquisition with later lead quality.
This is particularly useful for:
B2B companies, agencies, real estate businesses and other businesses where the sale happens after the initial online enquiry.
Setting Up eCommerce Conversion Tracking
For an online store, the most important event is typically:
purchase
Google recommends using the predefined eCommerce event structure and associated parameters rather than creating random custom names.
A complete purchase implementation may include information such as:
- transaction ID
- value
- currency
- products purchased
A unique transaction ID is particularly important because it can help prevent duplicate purchase counting and reconcile analytics with backend order systems.
For eCommerce businesses, never rely only on a thank-you page view if a proper purchase event with transaction information can be implemented.
How to Connect GA4 Key Events With Google Ads
If you run Google Ads, you can use selected Analytics activity as Google Ads conversions.
First connect:
Google Analytics 4 → Google Ads
Google’s current setup requires the Analytics property and Ads account to be linked before Analytics-based conversions can be used properly across the two platforms.
Then you can create a Google Ads conversion using an Analytics event or key event.
The current Google Ads flow includes:
Goals → Create conversion action → Select Google Analytics property → Select event
Alternatively, conversions can be created from Analytics through the Advertising section.
Not Every Key Event Should Be a Google Ads Conversion
This distinction matters.
You may mark an action as important inside Analytics because it helps you understand customer behaviour.
But you may not want Google Ads bidding to optimise toward it.
For example:
Actual form submission: likely a strong Ads conversion.
User scrolls 90% of a page: useful engagement signal, but probably not something you want Smart Bidding treating like a lead.
Only use actions as advertising conversions when they represent real campaign value.
Primary vs Secondary Google Ads Conversions
When Analytics-based conversions are created in Google Ads, review their optimization settings.
Google notes that some conversion actions created through Analytics may initially be set as secondary, meaning they are available for reporting but do not automatically influence bidding.
If an action should guide Smart Bidding, check its Google Ads optimization settings carefully.
This can prevent a common problem where marketers think a conversion is being used for bidding when it is only being reported.
Track Values Where Possible
Not every conversion has equal value.
A purchase worth ₹25,000 is more valuable than one worth ₹500.
A qualified enterprise lead may be worth more than a general enquiry.
Where relevant, pass monetary or business value through your event parameters.
This allows better reporting and eventually supports stronger campaign optimization.
For purchases, use the actual transaction value.
For lead-generation businesses, consider developing realistic lead values based on historical sales data rather than inventing arbitrary numbers.
Use Recommended Events Instead of Random Names
GA4 allows custom events, but you should use Google’s recommended event names whenever they accurately describe the action.
For example:
Use:
generate_lead
rather than:
contact_form_success_2026_final
when the action genuinely represents a lead.
Google recommends standard event names because they support predefined metrics, reports, suggested audiences and future platform integrations.
Custom events remain useful when no recommended event fits the interaction.
Avoid Duplicate Tracking
Duplicate conversions are a common analytics problem.
Imagine one form submission triggers:
form_submit
and
generate_lead
and both are marked as key events.
If both represent the same business outcome, reporting can make it appear that two conversions happened when there was really only one lead.
Similarly, an eCommerce purchase should not fire twice because:
the thank-you page reloads, or the tag is installed both directly and through Tag Manager.
Always test for duplicates.
Do Not Mark Every Micro-Interaction as a Key Event
Clicks, scrolling and video views are useful engagement data.
But key events should be reserved for actions connected to real business goals.
Otherwise your reports become noisy.
A good measurement hierarchy is:
Engagement event: visitor interacts.
Key event: visitor performs an important business action.
Conversion: the important action is also used for advertising measurement or bidding.
This creates much cleaner reporting.

Consent and Privacy Matter in 2026
Conversion tracking should also respect user consent and applicable privacy requirements.
Google Consent Mode allows Google tags to adjust their behaviour based on the consent choices communicated by your consent banner or consent-management platform.
Google currently supports both basic and advanced Consent Mode implementations.
In basic mode, Google tags can be blocked until consent is granted.
In advanced mode, tags can load with denied consent states and send limited cookieless signals, which can support more detailed conversion modeling where eligible.
Consent Mode itself is not a cookie banner.
You still need an appropriate consent mechanism when required.
Common GA4 Conversion Tracking Mistakes
Several mistakes can make your reports misleading.
Tracking Page Visits as Leads
Visiting /contact/ does not mean someone submitted an enquiry.
Tracking Button Clicks Instead of Successful Actions
Clicking “Submit” does not always mean the form was successfully processed.
Duplicate Tags
Installing GA4 directly and through GTM without understanding the setup can create duplicate data.
Wrong Event Names
Using inconsistent custom names makes reporting harder.
No Testing
Publishing a tag without using Realtime, Tag Assistant or DebugView is risky.
Marking Too Many Key Events
Your key-event list should represent genuine business importance.
Ignoring Google Ads Settings
An Analytics event existing in GA4 does not automatically mean Google Ads is optimising toward it.
A Practical GA4 Measurement Plan
Before configuring anything, create a simple table like this:
| Business Action | GA4 Event | Key Event? | Ads Conversion? |
| Contact form submitted | generate_lead | Yes | Yes |
| Account created | sign_up | Yes | Maybe |
| Purchase completed | purchase | Yes | Yes |
| File downloaded | file_download | No | No |
| Outbound link clicked | click | No | No |
| Blog scrolled | scroll | No | No |
This prevents analytics from becoming a collection of random events.
Every tracked action should have a reason.
How Businesses Can Use Conversion Data
Once tracking is accurate, GA4 becomes much more useful.
You can compare:
- organic search conversions
- paid search conversions
- social media leads
- landing-page conversion rates
- device performance
- campaign performance
- high-converting traffic sources
This helps answer questions such as:
Which channel generates actual leads?
Which landing page converts better?
Are mobile users converting?
Which marketing campaigns deserve more budget?
Businesses that need help connecting analytics, campaign performance and website conversions can explore Analytics growth tracking.
For broader campaign planning and measurement, Strategic digital marketing can also support digital marketing requirements.
GA4 Conversion Tracking Checklist
Before considering your setup complete, check:
- GA4 property is receiving data
- correct business actions are defined
- recommended event names are used where possible
- important events are marked as key events
- events fire only after successful actions
- duplicate events are removed
- values and transaction IDs are passed where needed
- Realtime testing is complete
- DebugView testing is complete
- GA4 and Google Ads are linked where required
- only appropriate actions are used for Ads optimization
- consent implementation is reviewed
A clean setup is more valuable than tracking everything.
Conclusion
A proper GA4 conversion tracking setup begins with the business goal, not the Analytics interface.
First decide which customer actions actually matter.
Then create or identify the correct GA4 events, mark important ones as key events and test them carefully.
If the action is also important for Google Ads measurement or bidding, create a Google Ads conversion from the relevant Analytics event or key event.
The current GA4 structure is simple once the terminology is clear:
Event → Key Event → Conversion
Use recommended event names where possible, test with Realtime and DebugView, avoid duplicate tracking and keep the number of key events focused on genuine business outcomes.
When conversion tracking is configured correctly, Analytics stops being just a traffic report.
It becomes a system for understanding which marketing activity actually contributes to leads, sales and business growth.
Frequently Asked Questions
1. What is a conversion in GA4 in 2026?
Inside GA4, important business actions are primarily called key events. A conversion is created when an Analytics event is used for advertising measurement and optimization, such as in Google Ads.
2. How do I mark an event as a key event in GA4?
Go to Admin → Data display → Events, find the event and mark it as a key event.
3. What event should I use for a contact form submission?
Google recommends generate_lead when a user submits a form or request for information.
4. Can GA4 track forms automatically?
Enhanced Measurement can collect form_start and form_submit events, but you should test whether these accurately represent successful submissions on your particular website.
5. Can I set up GA4 conversion tracking with Google Tag Manager?
Yes. Tag Manager can send GA4 events based on triggers such as clicks, forms and custom website interactions.
6. How do I test GA4 conversions?
Use GA4 Realtime for recent activity and DebugView for detailed event-level troubleshooting.
7. Why is my GA4 event not appearing in reports immediately?
Standard event reports can take up to 24 hours to populate, while Realtime is designed for quicker verification.
8. Can I import GA4 conversions into Google Ads?
Yes. Link the GA4 property with Google Ads, then create a Google Ads conversion from the relevant Analytics event or key event.
9. Should every GA4 event be marked as a key event?
No. Key events should represent actions that are particularly important to the business, such as leads, signups or purchases.
10. What are the main GA4 conversion tracking mistakes?
Common problems include duplicate events, tracking button clicks instead of successful actions, using poor event names, marking too many key events and failing to test the implementation.