GA4 Conversion Tracking Setup: A Step-by-Step Guide
Setting up conversion tracking in GA4 properly means understanding the Google tag, event structure, and key event configuration, not just clicking a toggle. This guide walks through the technical setup end to end.
Priya Nair
Senior Marketing Analyst
Attribution & Analytics Blueprint Guide
Start with the Google tag, not the conversion toggle
Before any conversion can be tracked, GA4 needs a properly installed Google tag on every page of your site that you want measured. This is the base script, either installed directly or through Google Tag Manager, that sends events to your GA4 property. If the tag is missing on even one key page, such as an order confirmation page, no amount of downstream configuration will produce accurate conversion data.
It is worth checking tag installation with GA4's own DebugView or the Tag Assistant browser extension before building anything on top of it, since a broken or duplicated tag is the root cause of a large share of conversion tracking problems that get misdiagnosed as configuration issues further downstream.
Understand GA4's event-based model
Unlike older analytics models built around sessions and pageviews as the primary unit, GA4 treats everything as an event, including pageviews themselves. A conversion in GA4 is simply an event that has been marked as a key event, meaning GA4 will surface it in conversion-specific reports and can factor it into certain models, but the underlying event still needs to be captured correctly first.
This means the real work of conversion tracking setup happens at the event level: making sure the events representing meaningful actions, such as a purchase, a form submission, or a signup, are firing with the right name and the right parameters at the right moment. Marking something as a key event afterward is a comparatively small step.
Automatically collected events versus events you configure
GA4 automatically collects a set of events without any extra configuration, including page_view, first_visit, and session_start, along with enhanced measurement events like scroll depth and outbound clicks if enabled. These give you baseline engagement data but rarely represent the specific conversions a business actually cares about.
For anything more specific, such as a completed purchase or a lead form submission, you need either GA4's recommended events, which follow a predefined naming and parameter structure Google documents, or fully custom events you define yourself. Using a recommended event name where one exists, such as generate_lead or purchase, is worth the extra setup time because it unlocks reporting features and integrations tied to those specific names.
Configuring events through Google Tag Manager
Most teams implement custom event tracking through Google Tag Manager rather than editing site code directly, since it lets marketers adjust event triggers without redeploying the website. A typical setup involves creating a trigger, such as a click on a specific button or a page load on a specific URL, and pairing it with a Google Analytics: GA4 Event tag that fires with the event name and parameters you want.
Parameters matter more than they might seem. A purchase event without a value parameter tells you a purchase happened but not what it was worth, which strips out most of the reporting value GA4 can otherwise provide, including revenue-based reporting in the same interface where you already review campaign performance.
Marking events as key events
Once an event is firing correctly and you can see it in GA4's Realtime or standard reports, the next step is marking it as a key event in the Admin section, under Events. This tells GA4 to treat this event as a conversion for reporting purposes, but it does not retroactively apply to data collected before the toggle was flipped, so this step should happen as early as possible once you trust the event data is accurate.
It is worth resisting the temptation to mark every event as a key event. Overloading key events with low-value actions, like scroll depth or generic clicks, dilutes the conversion reports and makes it harder to see the metrics that actually matter to the business at a glance.
Connecting conversions back to campaign data
Conversion tracking only becomes useful for marketing decisions once it connects back to the UTM parameters that identify where traffic came from. GA4 does this automatically for sessions that arrived with UTM tagging intact, attributing the eventual key event back to the session's source and medium, provided the tagging was applied consistently at the link level in the first place.
This is the point where conversion tracking and UTM tracking work together rather than as separate systems, a relationship covered in more depth in conversion tracking vs UTM tracking. Getting the UTM side right, using a consistent builder rather than ad hoc tagging, is just as important as the GA4-side event configuration described above.
Testing before trusting the data
Before relying on any new key event for decision-making, test it end to end using DebugView, which shows events in near real time as they are received by GA4, including their parameters. Walk through the actual conversion flow yourself, checking that the event fires exactly once per real conversion, not multiple times from a misconfigured trigger, and that parameter values look correct.
A common and costly bug is a purchase event firing on every visit to a confirmation page, including page refreshes or back-button navigation, which silently inflates conversion counts well beyond actual purchases. Catching this in DebugView before it accumulates weeks of bad data is far easier than trying to clean up the reporting afterward.
Handling ecommerce-specific conversion setup
Ecommerce sites have a more demanding version of this setup because a single purchase event needs to carry not just a value and currency, but an items array describing each product, quantity, and price in the cart. GA4's recommended purchase event schema expects this structure, and getting it wrong, such as sending only a total value without itemized data, still produces a working conversion count but breaks GA4's ecommerce-specific reports like product performance and purchase-to-view ratios.
Most ecommerce platforms, including Shopify and WooCommerce, offer a native GA4 integration or a well-documented Google Tag Manager recipe that populates this data automatically from the checkout process, which is generally more reliable than building the purchase event by hand. Testing a real, low-value order through the full checkout flow while watching DebugView is the fastest way to confirm the itemized data is arriving correctly before trusting the ecommerce reports for decisions about which products or campaigns drive revenue.
Where a no-developer approach differs from this setup
This guide covers the full technical path through Google Tag Manager and custom event configuration, which gives the most control but requires some comfort with tag management concepts. For teams without that capacity, a lighter no-developer approach using GA4's built-in enhanced measurement and simple trigger rules can cover a meaningful share of basic conversion needs, which is the territory covered in setting up conversions in GA4 without a developer.
Either path benefits from clean UTM tagging on the acquisition side, which UTMLoop's utm-builder and free tier are built to support regardless of how sophisticated your GA4 event setup ends up being.
Frequently Asked Questions
Do I need Google Tag Manager to set up GA4 conversion tracking?
Not strictly, but it is the most common and flexible way to implement custom events without editing site code directly. Simpler conversions can sometimes be handled through GA4's enhanced measurement settings alone.
What is the difference between an event and a key event in GA4?
Every conversion in GA4 starts as a regular event. A key event is simply an event that has been marked in GA4's settings to be treated as a conversion for reporting purposes; the underlying event data is identical either way.
Does marking an event as a key event apply retroactively?
No. Only data collected after you mark an event as a key event will appear in conversion-specific reports. Historical data for that event before the toggle was flipped is not reclassified.
Why does my purchase event show the wrong revenue?
This is usually a parameter configuration issue, most often a missing or incorrectly mapped value parameter on the purchase event tag. Check the event in DebugView to confirm the value and currency parameters are populated correctly.
Join 14,000+ marketing growth leaders
Receive our bi-weekly breakdown of campaign analytics setups, attribution rules, naming tactics, and link-stitching blueprints. Direct to your inbox.
Continue reading blueprints
All ArticlesWhat Is Attribution in Marketing? A Plain-English Guide
Attribution simply means deciding which marketing effort deserves credit for a conversion. Here's a plain-English breakdown of the models, and why the choice changes your budget decisions.
Why "Direct Traffic" in Analytics Is Often Mislabeled, and How to Fix It
"Direct" traffic is supposed to mean someone typed your URL from memory. In practice, it's often a dumping ground for broken tracking. Here's how to diagnose and fix it.