GA4 conversion tracking for marketers: a setup guide

GA4 conversion tracking works by flagging any event, button clicks, purchases, or form submissions your site already generates, as a “key event” that feeds reporting and Google Ads bidding. There’s no separate goal-building interface like Universal Analytics had. You work with the events already flowing through your property.

Getting it right comes down to three moves. First, identify which event actually represents a conversion for your business. Second, implement that event correctly through the Google tag (gtag.js) or Google Tag Manager, then confirm it fires using DebugView or Realtime. Third, mark it as a key event inside GA4 and share it with Google Ads so your campaigns can bid against it.

• Identify: Pick the event that matches a real business outcome, not just any click.
• Implement: Fire the event through gtag.js or GTM, then verify it in DebugView or Realtime before trusting the data.
• Mark and share: Flag it as a key event in GA4 Admin, then link your Google Ads account so the conversion can inform bidding.

Pro Tip: Don’t mark an event as a key event the same day you launch it. Watch it in DebugView and Realtime for 24 to 48 hours first. GA4 reports lag, and a rushed conversion flag can quietly skew your Ads bidding data before you’ve even confirmed the event fires correctly.

Key Takeaways

GA4 conversion tracking works when marketers pick a small set of high-value events, verify them in DebugView before trusting the data, and keep Google Ads conversion settings deliberately reconciled.

Point	Details
Limit your key events	Standard properties cap at 30 key events, so prioritize revenue and lead-driving actions over vanity metrics.
Verify before trusting	Always check DebugView and Realtime first, since standard reports can take 24 to 48 hours to populate.
Pass value parameters	Include value, currency, and transaction_id on purchase and lead events to strengthen Ads bidding signals.
Check primary vs secondary status	Google Ads often defaults imported GA4 conversions to secondary status, which excludes some from Smart Bidding unless adjusted.
Audit on a schedule	Run a conversion audit roughly every 90 days, or bring in Tech Business Development to handle setup and auditing directly.

Table of Contents

• What counts as a conversion in GA4 conversion tracking
• GA4 event types and when to use each one
• Setting up GA4 events with gtag.js and Google Tag Manager
• How to mark a GA4 event as a key event
• Connecting GA4 to Google Ads for conversion tracking
• Verifying GA4 conversion tracking and fixing discrepancies
• Best practices for maintaining accurate GA4 conversion data
• A conversion tracking audit checklist you can run this week
• Why fewer, sharper conversions beat a long list every time
• Get your GA4 and Google Ads setup done right the first time
• Where to go for deeper GA4 conversion reading
• Frequently asked questions about GA4 conversion tracking
• Sources

What counts as a conversion in GA4 conversion tracking

GA4 doesn’t have “goals.” It has events, and any event can become a conversion the moment you flag it as a key event in the Admin panel. That’s the entire model: no separate goal funnel builder, no distinction between destination, duration, or event-based goal types. Everything is an event first.

This is a real departure from how Universal Analytics worked, and it trips up a lot of people migrating over. UA required you to define goals inside a rigid framework, hit-based tracking, essentially, where a pageview or session event triggered a completion. GA4 flips that. Every user interaction is already an event by default, and you choose which ones matter enough to count as conversions.

Here’s a practical translation table for anyone still thinking in UA terms:

• A UA “destination goal” for a thank-you page becomes a page_view event filtered by URL, or better, a dedicated custom event fired only on that page.
• A UA “duration goal” for session length has no direct GA4 equivalent. You’d typically replace it with engagement metrics instead.
• A UA “event goal” (like a video play) maps almost one-to-one to a GA4 custom or recommended event, just flagged as a key event.

The property limits matter here too. Standard GA4 properties can mark up to 30 events as key events, while Analytics 360 properties get a higher ceiling. That cap is a feature, not a limitation. It forces discipline. Migrating every legacy UA goal one-for-one usually means dragging over years of accumulated clutter, half of which nobody has looked at since 2019.

Treat the UA to GA4 transition as a chance to reset your measurement strategy entirely, rather than recreating every legacy goal by rote. Focus on the actions tied directly to current revenue drivers, and let the rest go.

Auditing your conversion list before you migrate anything is worth the afternoon it takes. Most businesses find at least a third of their old UA goals no longer reflect how the site or funnel actually works.

GA4 event types and when to use each one

GA4 sorts events into four categories, and knowing which bucket an action falls into saves you from building something Google already tracks for you. The one-line rule: use automatically collected events for baseline behaviour, enhanced measurement for common on-page interactions, recommended events for standard business actions, and custom events only when nothing else fits.

Automatically collected events fire the moment you install the Google tag, no configuration needed. Things like session_start and first_visit fall here. You’ll rarely mark these as conversions on their own since they measure activity, not intent.

Enhanced measurement events are the toggleable extras: scroll, click (for outbound links), file_download, video_start, and similar. These live in a checkbox list under Admin → Data Streams and require zero code. If your conversion candidate is “visitor downloaded the PDF,” this is where it already lives.

Recommended events are Google’s naming templates for common actions like purchase, sign_up, generate_lead, or add_to_cart. You still implement these yourself through gtag.js or GTM, but using Google’s exact event and parameter names unlocks prebuilt reporting and ecommerce dashboards that a custom-named event won’t populate.

Custom events exist for everything else, actions unique to your business that don’t match a recommended template. Google’s own guidance is blunt about this: check whether the action is already captured automatically or through a recommended event before you build something new. Custom events don’t inherit prebuilt dimensions the way recommended events do, so you often end up building custom reports just to see the data cleanly.

Business goal	Best event type	Why
E-commerce purchase	Recommended (purchase)	Populates revenue reporting automatically
Newsletter signup	Custom or recommended (sign_up)	Depends on whether it fits the sign_up template
PDF or brochure download	Enhanced measurement	Already tracked via file_download toggle
Quote request form	Custom event	Rarely matches a standard template
Phone number click	Enhanced measurement (outbound click) or custom	Depends on how the link is coded

Naming discipline matters more than people expect. Stick to lowercase, underscore-separated names (request_quote, not “Request A Quote!!”), and pass consistent parameters like value and currency wherever money is involved. Google Ads bidding algorithms lean on that parameter data, and sloppy naming across events makes optimization noisier than it needs to be.

Setting up GA4 events with gtag.js and Google Tag Manager

Both the Google tag and Google Tag Manager get the job done, but they solve different problems. gtag.js is faster for simple, static implementations. GTM wins when you’re dealing with dynamic triggers, multiple stakeholders touching the container, or interactions that a developer would rather not hardcode.

Implementing with gtag.js:

1. Confirm your base Google tag is installed on every page, typically in the <head>, loading the gtag.js library and your GA4 measurement ID.
2. Add an event call at the point of interaction. For a form submission, that looks like: gtag('event', 'generate_lead', { 'value': 50, 'currency': 'USD' });
3. Trigger this snippet through a JavaScript event listener tied to your form’s submit action, or fire it directly in the code path that runs on successful submission.
4. Confirm the parameters you’re passing (value, currency, any custom ones) match what you’ll want to see later in reporting.

Implementing with Google Tag Manager:

1. Create a new tag inside GTM, type “Google Analytics: GA4 Event.”
2. Point it to your existing GA4 Configuration tag.
3. Name the event (following the naming conventions above) and add any parameters you want captured, like button_text or form_id.
4. Build a trigger, most commonly a “Click” or “Form Submission” trigger scoped to the specific element you care about.
5. Use GTM’s preview mode to test the trigger fires correctly before publishing anything live.

Comparing the two head-to-head: gtag.js gives developers direct control and skips an extra platform, but every change needs a code deployment. GTM removes that dependency, marketers or analysts can build and test triggers without touching the codebase, but it adds a layer of container management and a slightly steeper learning curve for anyone new to trigger logic.

Pro Tip: Always test in DebugView before you publish a GTM container live. Turn on DebugView from the GA4 Admin panel or install the Google Analytics Debugger Chrome extension, fire the event manually, and watch it appear in real time with all its parameters listed. If a parameter is missing or a value looks off, you’ll catch it before it pollutes weeks of reporting.

After implementation, run through this quick checklist: open DebugView, trigger the event yourself, confirm it appears within seconds, check every parameter value looks correct, then repeat the test in Realtime to be sure it’s not a debug-only artifact.

How to mark a GA4 event as a key event

Once an event fires reliably in DebugView, marking it as a conversion takes about ten seconds. Go to Admin, then Events (or Configure → Key events, depending on your interface version), find the event in the list, and toggle “Mark as key event” next to it.

After you flip that switch, verify a few things:

• The event actually shows up in the Key events list you’ll later use for the Conversions report.
• Data starts populating within 24 to 48 hours in standard reports, even though DebugView and Realtime show it immediately.
• You haven’t accidentally marked a high-volume, low-intent event (like a generic click) that will flood your conversion count with noise.

Standard GA4 properties cap out at 30 key events per property, and that number matters more than it sounds like it should. If you’re already near the limit, prioritize events tied directly to revenue or lead generation over vanity actions like scroll depth or video starts. Analytics 360 customers work with a substantially higher ceiling, which is one of the more overlooked reasons larger organizations upgrade.

GA4’s Admin panel also keeps a change history log, showing who marked or unmarked which events and when. Check this log whenever your conversion numbers shift unexpectedly. It’s often the fastest way to spot that someone toggled a key event off during a container cleanup and nobody noticed until the report looked wrong.

Connecting GA4 to Google Ads for conversion tracking

Link your Google Ads account to GA4 first, then create or import the specific conversions you want Ads to bid against. The connection itself lives under GA4 Admin → Product Links → Google Ads Links, and it requires administrative access on both the Analytics property and the Ads account.

Steps to link and import:

1. In GA4 Admin, navigate to Google Ads Links and choose “Link,” then select the Ads account you want connected.
2. Confirm the linking permissions; you’ll need edit access on Analytics and admin access on the Ads account (or have someone with that access approve it).
3. Once linked, go to GA4’s Admin → Conversions (or Key events) and choose which key events to expose to Google Ads.
4. In Google Ads, navigate to Goals → Conversions, and you’ll see the imported GA4 conversions available to add to your conversion actions.
5. Review each imported conversion’s settings, counting method (one per click vs. every) and conversion window, since these are often managed from the Analytics side and locked from editing directly in Ads.

Deciding between native Google Ads tags and GA4-sourced conversions comes down to what you’re optimizing for. Native Ads conversion tags give you granular click-level attribution windows tailored specifically to ad interactions. GA4-sourced conversions give you a single source of truth across your entire marketing mix, useful when you want Ads bidding informed by the same data your organic and email channels are measured against. Many teams run both for a period, then consolidate once they trust the GA4 numbers.

Pro Tip: Check the “Include in Conversions” toggle for every GA4-imported conversion inside Google Ads. Google often sets these to secondary status by default as a safeguard against double-counting when a similar Ads-native conversion already exists. If you expected an imported conversion to influence Smart Bidding and it isn’t showing up in optimization, this toggle is usually why.

That default secondary status catches a lot of marketers off guard mid-campaign. Conversions imported from Analytics key events don’t automatically feed bidding algorithms unless someone deliberately promotes them to primary, precisely because Google assumes you might already be tracking that same action natively.

Verifying GA4 conversion tracking and fixing discrepancies

Check events in this order: DebugView first for immediate parameter-level confirmation, Realtime second for a broader live view across your whole property, and the standard Conversions report last, once you’ve given data 24 to 48 hours to settle.

Debug checklist before you trust any conversion number:

1. Turn on DebugView from GA4 Admin or via a debug browser extension.
2. Trigger the event manually and confirm it appears with the correct name and parameters.
3. If using GTM, run the same test inside preview mode before publishing.
4. Check the event fires consistently across at least three test scenarios (different browsers, devices, or user paths).
5. Compare a conversion triggered from an ad click against one triggered organically to catch any attribution-specific bugs.

When Google Ads and GA4 show different numbers for what should be the same conversion, the mismatch almost always traces back to one of these:

• Time zone settings differ between your Ads account and GA4 property, shifting which day a conversion gets attributed to.
• Attribution model differences mean Ads and GA4 might be crediting different touchpoints for the same conversion path.
• Counting method is set to “every” in one platform and “one per session” in the other, doubling or halving apparent volume.
• Duplicate tags are firing the same event twice, often left over from a migration where both an old and new tag are live simultaneously.
• Cross-domain tracking isn’t configured correctly, splitting a single user journey into two disconnected sessions.
• Conversion windows differ, so a 30 day Ads window captures conversions that a 7 day GA4 window would exclude.

Run through this list top to bottom whenever the numbers don’t match. Nine times out of ten, it’s a settings mismatch rather than a broken tag.

Best practices for maintaining accurate GA4 conversion data

Keep your key event list short, name events consistently, pass value parameters wherever money changes hands, and document every change you make. That’s the whole discipline in one sentence, but each piece deserves a closer look.

Naming conventions should be decided once and enforced everywhere, lowercase_with_underscores, consistent whether it’s implemented in gtag.js or GTM. A mixed naming scheme (Purchase in one place, purchase_complete in another) fragments your reporting and confuses anyone auditing the account later.

Parameter usage deserves more attention than most teams give it. Passing value, currency, and transaction_id on ecommerce and lead events means Google Ads can optimize toward actual dollar figures rather than raw conversion counts, which meaningfully improves bidding quality once you have enough volume.

Deduplication matters most for purchase events, where a page refresh on a confirmation screen can double-fire a conversion. Using a unique transaction_id parameter lets GA4 recognize and discard the duplicate automatically.

Cross-domain setup needs explicit configuration if your checkout or booking flow lives on a different domain than your main site. Without it, GA4 sees two separate users instead of one continuous journey, which quietly inflates session counts and breaks attribution.

Pro Tip: Use dynamic event parameters, like value pulled from an actual cart total rather than a hardcoded number, so Google Ads bidding reflects real transaction sizes instead of a flat estimate that under or overvalues every conversion equally.

Pro Tip: Put a recurring 90 day conversion audit on the calendar. Revisit which key events are still active, whether any have gone quiet due to a site redesign, and whether new business priorities warrant retiring an old conversion or adding a new one.

A conversion tracking audit checklist you can run this week

A proper audit validates that your conversions reflect real business events, fire reliably, and sync correctly with Google Ads. Expect to come out the other side with a clean key event list, confirmed Ads linkage, and consistent naming across your whole setup.

Step-by-step audit tasks:

1. Inventory every event currently firing in your GA4 property, cross-referencing DebugView against your GTM container or gtag.js implementation.
2. Map each event candidate to an actual business KPI, revenue, lead volume, engagement that matters to leadership.
3. Validate implementation for each candidate in DebugView, confirming parameters and firing conditions are correct.
4. Mark the validated, KPI-aligned events as key events inside GA4 Admin.
5. Confirm your Google Ads account is linked, then import the relevant key events as Ads conversions.
6. Check counting methods, conversion windows, and primary/secondary status on each imported conversion.
7. Wait 48 hours, then compare GA4’s Conversions report against Google Ads’ conversion numbers for consistency.

Assign this across roles rather than dumping it on one person. A marketing owner should handle the KPI mapping and prioritization (roughly one to two days). A developer or analytics admin handles implementation and DebugView validation (one to three days depending on how many events need building). The marketing owner or an analytics admin then handles the Ads linking and final verification (about one day).

Paste this into a project tracker as five rows: Inventory, KPI Mapping, Implementation, Ads Linking, Verification, each with an owner and a target date. It’s a small enough project to finish inside a single sprint, and it’s the kind of housekeeping that pays for itself the first time a bidding campaign starts making better decisions because the conversion signal feeding it is finally clean.

Why fewer, sharper conversions beat a long list every time

The instinct when migrating to GA4 is to recreate every UA goal you ever built, and it’s the wrong instinct. A property with 30 available key event slots and eight goals worth tracking doesn’t need to fill all 30 slots just because it can. What actually moves the needle is picking the handful of events that map directly to revenue or qualified leads, implementing them cleanly, and letting Google Ads bid against a strong signal instead of a diluted one. Teams that treat this transition as a strategic reset, rather than a lift-and-shift exercise, consistently end up with better bidding performance simply because the data feeding their campaigns isn’t cluttered with noise from events nobody’s looked at in years.

Get your GA4 and Google Ads setup done right the first time

If everything above feels like a lot to manage on top of running a business, that’s because it is. Tech Business Development handles GA4, GTM, and Google Ads setup as one of its core services, at a fraction of what a traditional agency retainer costs, and without the months-long onboarding that usually comes with it.

The deliverables are concrete: a full conversion audit against your current setup, a properly built GTM container with tested triggers, key events mapped to your actual revenue drivers, Google Ads conversion import handled correctly (including checking that secondary/primary status you now know to look for), and automated reporting dashboards so you’re not logging into three platforms to check whether campaigns are working. Tech Business Development builds this for small and local businesses specifically, where an in-house analytics hire isn’t realistic but sloppy tracking is quietly costing ad budget every month.

Book a discovery call through the services page and get a straight answer on what your current setup is missing before you spend another dollar on Google Ads.

Where to go for deeper GA4 conversion reading

Google’s own documentation remains the most reliable reference for anything that changes with GA4, and a few practitioner guides fill in the practical gaps official docs tend to skip.

• UA to GA4: Conversions and key events for the full breakdown of property limits and legacy goal migration.
• GA4 events documentation from Google Developers, covering gtag.js syntax and event structure in technical detail.
• Set up recommended and custom events for the GTM-specific configuration steps and trigger setup.
• Creating and managing conversions for the Google Ads linking and import workflow.
• Track Key Events with GA4 from Analytics Mania, a practitioner walkthrough with screenshots that pairs well with the official steps.

Frequently asked questions about GA4 conversion tracking

Is GA4 conversion tracking the same as setting up goals in Universal Analytics? No. UA used a dedicated goals interface with hit-based logic. GA4 flags any existing event as a key event instead, which changes how you plan, name, and prioritize what counts as a conversion.

How long does it take for a new GA4 conversion to show up in reports? DebugView and Realtime show event data within seconds. Standard GA4 reports, including the Conversions report, typically take 24 to 48 hours to fully populate.

Can I have unlimited key events in GA4? No. Standard properties are capped at 30 key events, while Analytics 360 properties get a considerably higher limit. That constraint is worth embracing rather than fighting.

Why does my Google Ads conversion show as “secondary” after importing it from GA4? Google sets many imported conversions to secondary status by default to prevent double-counting against existing Ads-native tags. You need to manually check and adjust this if you want the conversion to influence Smart Bidding.

Should I use gtag.js or Google Tag Manager for GA4 event tracking? GTM offers more flexibility for teams without constant developer access and makes testing triggers easier through preview mode. gtag.js suits simpler, code-controlled implementations where a developer is already making the change directly.

Sources

• UA→GA4 Conversions and key events in Google Analytics 4 Legacy - Analytics Help
• GA4 events - Google Developers
• Set up recommended and custom events - Analytics Help
• Creating and managing conversions - Analytics Help

Recommended

• Tech Business Development
• Tech Business Development
• Tech Business Development
• Tech Business Development