Why Conversion Tracking in GA4 Still Trips People Up

Google Analytics 4 has been the default analytics platform since mid-2023, yet a surprising number of SMBs in Australia, Canada, Singapore, and the US are still relying on pageview data alone — with zero visibility into which actions are actually driving revenue. Leads slip through. Ad spend goes unattributed. And the data that should inform decisions sits empty.

Most tutorials assume you have Google Tag Manager already set up. But if you run a lean operation — a small SaaS, a local services business, or a growing e-commerce brand that just wants things working — adding GTM can feel like more overhead than it's worth. The good news: you can configure robust GA4 conversion tracking directly through the gtag.js snippet, and it takes less than an hour.

This guide walks you through every step, from installing the base tag to verifying that conversions are firing correctly in your GA4 dashboard.

What You'll Need

  • A Google Analytics 4 property (not a Universal Analytics property)
  • Basic access to your website's HTML — either via your CMS (WordPress, Webflow, Shopify, Squarespace) or directly in code
  • The ability to add or edit JavaScript on your site
  • Google Chrome with the GA4 Debugger extension installed (free, highly recommended)
  • About 45–60 minutes

Note: This guide covers manual gtag.js implementation. If you're on Shopify, some steps differ slightly — those are called out inline.

Step 1: Locate Your GA4 Measurement ID

Your Measurement ID is the unique identifier for your GA4 property. It looks like G-XXXXXXXXXX.

To find it, log in to Google Analytics, navigate to Admin → Data Streams, then click your web data stream. Your Measurement ID appears at the top right of the panel. Copy it — you'll need it in the next step.

Common pitfall: Don't confuse the Measurement ID with the older UA tracking ID (which starts with UA-). If you see that, you're looking at a Universal Analytics property, not GA4.

Step 2: Install the Base gtag.js Snippet

If your site doesn't already have the GA4 base tag installed, add the following snippet to the <head> section of every page on your site. Replace G-XXXXXXXXXX with your actual Measurement ID.

<!-- Google Analytics 4 -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-XXXXXXXXXX');
</script>

Platform-specific notes

  • WordPress: Paste the snippet using a plugin like Insert Headers and Footers, or directly in your theme's header.php file inside the <head> tag.
  • Webflow: Go to Project Settings → Custom Code and paste into the Head Code section.
  • Shopify: Go to Online Store → Themes → Edit Code → theme.liquid and paste before the closing </head> tag.
  • Squarespace: Go to Settings → Advanced → Code Injection and paste into the Header section.

Pro tip: Once installed, open Chrome's GA4 Debugger extension and visit your site. If you see events firing in the debugger panel, your base tag is working.

Step 3: Identify the Conversions You Actually Want to Track

Before writing a single line of tracking code, decide what a conversion means for your business. Most SMBs should start with two or three high-value events — not everything at once.

Common conversion events worth tracking:

  • Lead form submissions — contact forms, quote request forms, demo requests
  • Button clicks — "Get a Quote", "Book a Call", "Start Free Trial"
  • Thank-you page views — the confirmation page after a purchase or form submission
  • Phone number clicks — especially important for local service businesses
  • File downloads — whitepapers, product spec sheets

Pick your top two to start. You can add more later once the foundation is solid.

Step 4: Set Up Event-Based Conversion Tracking

GA4 works on an event model. Every conversion is an event. There are two approaches: tracking a thank-you page view (simpler) or tracking a specific user action like a button click (more precise).

Option A: Thank-You Page Conversion (Easiest)

If your form redirects to a dedicated thank-you page (e.g., /thank-you or /order-confirmed), you can fire a conversion event by adding this snippet to that page only, after the base gtag config:

<script>
  gtag('event', 'generate_lead', {
    'event_category': 'form',
    'event_label': 'contact_form_submission'
  });
</script>

The event name generate_lead is one of GA4's recommended event names — using it means GA4 automatically understands the intent. You can also use purchase, sign_up, or a custom name like book_demo.

Option B: Button Click Conversion (More Precise)

If there's no redirect and your form submits inline (common with Ajax forms), attach the event to the button or form submit handler:

<script>
  document.getElementById('contact-form').addEventListener('submit', function() {
    gtag('event', 'generate_lead', {
      'event_category': 'form',
      'event_label': 'contact_page_form'
    });
  });
</script>

Replace 'contact-form' with the actual id attribute of your form element. Check your page source to confirm the ID.

Common pitfall: If your form has no id, use document.querySelector('.your-form-class') instead. And always test that the event fires before marking it as a conversion in GA4.

Step 5: Mark the Event as a Conversion in GA4

Sending an event is only half the job. You also need to tell GA4 that this event counts as a conversion.

  1. In GA4, go to Admin → Events (under your property column).
  2. Find your event in the list. If it doesn't appear yet, trigger it once on your live site using the debugger, then wait 24–48 hours — or use the Create event button to define it manually.
  3. Toggle the Mark as conversion switch next to the event name.

That's it. GA4 will now count every instance of that event as a conversion and include it in your Conversions reports.

Pro tip: If you're running Google Ads, link your GA4 property to Google Ads under Admin → Google Ads Links, then import your GA4 conversions into Ads. This gives your campaigns real conversion signals to optimise against — and it's far more accurate than Google Ads' auto-detected conversions.

Step 6: Verify Everything Is Firing Correctly

Never assume tracking is working — always verify before using the data to make decisions.

Using GA4 DebugView

In GA4, go to Admin → DebugView. With the GA4 Debugger Chrome extension enabled on your browser, visit your site and trigger the conversion (submit the form, click the button). You should see your event appear in real time in the DebugView panel within a few seconds.

Using the Realtime Report

Go to Reports → Realtime in GA4. Trigger your event and watch for it to appear under "Event count by event name." If it shows up, your tracking is live.

Common pitfall: Ad blockers and browser privacy extensions (like Brave's shields) can block GA4 events. Always test in a clean Chrome window with extensions disabled, or use an incognito tab with only the GA4 Debugger active.

Step 7: Add Conversion Value (Optional but Recommended)

If you know the average value of a conversion — say, your average lead is worth $200 to your business — pass that value with the event. This unlocks Revenue reporting in GA4 and makes ROAS calculations in Google Ads meaningful.

<script>
  gtag('event', 'generate_lead', {
    'value': 200,
    'currency': 'AUD'
  });
</script>

Use your local currency code: AUD for Australia, SGD for Singapore, CAD for Canada, USD for the US. Even a rough estimate is better than no value at all — you can refine it later as you gather more data.

Common Mistakes to Avoid

  • Double-counting: If you install GA4 through your CMS's built-in integration AND manually add the gtag snippet, you'll send every event twice. Pick one method.
  • Tracking too many events as conversions: If every scroll and hover is a conversion, your data becomes meaningless. Be selective.
  • Not testing after site updates: A theme update or CMS migration can wipe your custom snippets. Set a monthly reminder to verify your key conversions are still firing.
  • Ignoring consent requirements: If you operate in regions covered by GDPR, Australia's Privacy Act amendments, or Canada's PIPEDA, ensure your cookie consent solution blocks GA4 until consent is given. GA4's consent mode v2 handles this — but that's a separate configuration step.

Next Steps

With conversion tracking live, you now have the foundation for data-driven marketing decisions. The natural next move is connecting your GA4 data to your broader marketing workflow — understanding which channels are driving conversions, which campaigns are wasting budget, and where users are dropping off before they convert.

If you're also working on your content and social strategy alongside this, our free social media content calendar template is a practical tool for aligning your publishing cadence with the conversion goals you've just set up — so your organic efforts are pointing in the same direction as your tracking.

At Lenka Studio, we work with SMBs across Australia, Singapore, Canada, and the US to build analytics setups that actually inform decisions — not just dashboards that look busy. If you've followed this guide and want to go further — connecting GA4 to Looker Studio, setting up audience segments, or linking to Google Ads — we're happy to help you get there faster.

Get in touch with the Lenka Studio team to talk through your analytics setup and make sure your tracking is working as hard as your marketing.