GA4 Conversion Events in 2026: Setup, Google Ads Import, GTM Custom Events & Verification

14 min read · CRO · Last updated July 2026

Quick answer: In GA4, any event can become a conversion with a single toggle. The critical steps most teams miss: (1) creating meaningful custom events first before marking them as conversions, (2) importing GA4 conversions into Google Ads after linking, and (3) verifying each conversion fires in DebugView before launching campaigns that depend on it.

Introduction

Conversion tracking is the backbone of performance marketing. Without accurate conversion data flowing from your website to GA4 and into Google Ads, you are running Smart Bidding strategies (Target CPA, Target ROAS, Maximize Conversions) on guesswork. Google’s own data shows that campaigns using Smart Bidding with accurate conversion data outperform campaigns without it by an average of 20–30% on ROAS.

This guide covers the complete conversion event workflow: from marking existing events in GA4, to creating custom events via GTM, to importing into Google Ads, to verification that every conversion fires correctly.

What you’ll learn:
– How GA4 conversion events work and how to mark them
– Creating custom events in GTM and via GA4’s event modification interface
– Importing GA4 conversions into Google Ads (and why this beats Google Ads tag)
– Verifying conversions with DebugView, Tag Assistant, and Realtime Reports

Table of Contents

1. How GA4 Conversion Events Work
2. Marking Existing Events as Conversions
3. Creating Custom Events via GA4 Interface
4. Creating Custom Events via GTM
5. Which Events to Track as Conversions
6. Importing GA4 Conversions into Google Ads
7. Conversion Attribution: GA4 vs Google Ads
8. Smart Bidding and Conversion Data Quality
9. Conversion Window Settings
10. Verifying Conversion Events
11. Conversion Event Planning Worksheet
12. GTM GA4 Event Tag Builder Guide
13. FAQ
14. Conclusion

1. How GA4 Conversion Events Work

In Universal Analytics, you configured Goals with specific trigger conditions (destination URL, event category/action/label, duration, pages per session). Each goal was a separate configuration object.

GA4 takes a different approach: every conversion is just an event with the “conversion” toggle enabled. There are no separate goal configurations. Any event that fires in GA4 can be marked as a conversion, and GA4 will start counting instances of that event as conversions from that point forward.

Key implications:
– GA4 conversions are not retroactive. Marking an event as a conversion today does not count past instances. Historical data shows zero conversions for that event before the toggle date.
– Each event instance counts as one conversion. If a user submits 3 forms in one session, GA4 records 3 conversions (unless you configure “once per session” counting).
– Multiple conversions can be active simultaneously. Unlike UA which showed one goal as the primary conversion, GA4 lets you analyze all conversions in parallel.
– GA4 has a 30-conversion event limit per property. This is rarely a practical constraint, but means you should not mark every incidental interaction as a conversion — be selective.

2. Marking Existing Events as Conversions

The simplest conversion setup: toggle an existing event as a conversion directly in GA4 Admin.

Steps:
1. Admin → Events (under the Property column)
2. The events table shows all events GA4 has received in the last 28 days
3. Find the event you want to mark (e.g., form_submit, purchase, sign_up)
4. Toggle the “Mark as conversion” switch to ON
5. GA4 immediately begins counting future instances as conversions

Automatic events that are pre-marked as conversions:
GA4 automatically marks purchase and first_open (app) as conversions when they are detected. You do not need to manually toggle these.

Events that require manual conversion marking (common examples):
– form_submit — available if your form fires this event
– generate_lead — fires via Google Ads auto-tagging in some setups
– Custom events you’ve created via GTM

Important: Events only appear in the Admin → Events table after they have fired at least once. If you haven’t yet had a form submission on your site, form_submit won’t be in the list and you cannot mark it as a conversion until it fires. Solution: fire a test event using GTM Preview mode or DebugView first.

3. Creating Custom Events via GA4 Interface

GA4’s built-in event modification tool lets you create new events based on existing ones — without writing code. This is useful for segmenting broad events into specific conversions.

Use case: GA4 fires form_submit for every form on your site. You want to track only the “contact_form” submission as a conversion, not newsletter signups.

Steps:
1. Admin → Events → Create event
2. Name your new event: contact_form_submit
3. Define conditions:
– Parameter: event_name → equals → form_submit
– AND Parameter: form_id → equals → contact-form (or whatever your form’s ID is)
4. Copy parameters from source event: Yes
5. Create
6. Mark the new contact_form_submit event as a conversion

Limitations of the interface method:
– You can only create events from existing events (not from scratch)
– You can only filter on parameters that are already being sent
– You cannot create triggers based on arbitrary DOM interactions (for that, use GTM)

4. Creating Custom Events via GTM

GTM gives you full control over when and what events fire. For any interaction that GA4’s enhanced measurement or automatic events don’t capture, GTM is the solution.

Example: Track phone number clicks as a conversion

Step 1: Create a trigger in GTM
– Trigger Type: Click → All Elements
– Trigger fires on: Some Clicks
– Condition: Click URL → contains → tel:
– Name: “Click – Phone Number”

Step 2: Create a GA4 Event tag in GTM
– Tag Type: Google Analytics → Google Analytics: GA4 Event
– Configuration Tag: [Select your GA4 Configuration tag]
– Event Name: phone_call_click
– Event Parameters: Add parameter phone_number → Value: {{Click URL}}
– Trigger: “Click – Phone Number”
– Name: “GA4 Event – Phone Call Click”

Step 3: Test in GTM Preview
Preview your container → click a phone number link → verify the tag fires → verify the event appears in GA4 DebugView.

Step 4: Mark as conversion in GA4
After the event fires at least once (via your GTM Preview test), go to Admin → Events → mark phone_call_click as a conversion.

Common custom events to build in GTM:

5. Which Events to Track as Conversions

Not every event should be a conversion. Conversions should represent actions that have a clear business value and that you want to optimize toward. Over-marking conversions dilutes Google Ads Smart Bidding signals and makes reports harder to interpret.

Primary conversions (highest value, always track):

Secondary conversions (micro-conversions, useful for analysis but not bidding):

• add_to_cart — signals purchase intent
• newsletter_signup — engagement metric
• pdf_download — content engagement
• video_25_percent — early engagement with video content

Configure secondary conversions as “Non-primary” in Google Ads (once imported) to exclude them from Smart Bidding optimization while retaining them for reporting analysis. Smart Bidding should only optimize toward primary conversions that represent clear business value.

6. Importing GA4 Conversions into Google Ads

Importing GA4 conversions into Google Ads is the recommended approach for Google Ads conversion tracking in 2024 and beyond. It eliminates the need for a separate Google Ads conversion tag and ensures both platforms share the same conversion definition.

Prerequisites:
– GA4 property and Google Ads account linked (Admin → Google Ads Links in GA4)
– Conversions configured and verified in GA4 first

Steps to import:
1. In Google Ads: Tools & Settings → Measurement → Conversions
2. Click the “+” button → Import → Google Analytics 4 properties
3. Select your linked GA4 property
4. Select the conversion events you want to import
5. Review attribution model and conversion window settings
6. Click Import and Continue

After import, in Google Ads each GA4 conversion appears as:
– Source: Analytics
– Category: the event type (Purchase, Lead, etc.)
– Attribution: inherits from GA4’s property setting (usually Data-Driven)

Linked vs native Google Ads conversion tag:
When using linked GA4 conversions, you do NOT need a separate Google Ads conversion tracking tag on your site. The GA4 tag handles the measurement, and Google Ads reads the data via the account link. Running both creates duplicate conversion counting — audit your account for this issue if you’ve recently switched to GA4 imports.

7. Conversion Attribution: GA4 vs Google Ads

This is a source of confusion for every analytics team: GA4 and Google Ads report different conversion numbers even for the same conversion event. This is expected and has specific causes.

Reasons for discrepancy:

1. Attribution model: GA4 uses Data-Driven Attribution by default. Google Ads may use a different model depending on your campaign settings.

2. Conversion window: GA4’s default conversion window is 30 days for non-purchase events. Google Ads defaults to 30 days for clicks, 1 day for view-through. Different windows count different conversions.

3. Scope: GA4 shows conversions across all channels. Google Ads shows only conversions it can claim credit for (those where the user interacted with a Google ad in the attribution window).

4. Time of attribution: GA4 reports conversions at the time the conversion happens. Google Ads reports conversions at the time of the ad click (attribution date), which can appear in different reporting periods.

5. Cross-device: GA4 with Google Signals can track cross-device conversions from logged-in Google users. Google Ads also does this, but the two systems use slightly different identity graphs.

Rule of thumb: Expect a 10–20% discrepancy between GA4 and Google Ads conversion counts. If the discrepancy is larger than 30%, investigate for duplicate tags, tracking gaps, or attribution window mismatches.

8. Smart Bidding and Conversion Data Quality

Google’s Smart Bidding (Target CPA, Target ROAS, Maximize Conversions, Maximize Conversion Value) uses your conversion data to train its ML model. The quality of this data directly determines campaign performance.

Minimum conversion volume for Smart Bidding:
– Target CPA: 50+ conversions in the past 30 days (50 at the campaign level)
– Target ROAS: 50+ conversions (with revenue data) in the past 30 days
– Maximize Conversions: No minimum, but performance degrades significantly below 20/month
– Maximize Conversion Value: Same as Target ROAS minimums

Why accuracy matters more than volume:
If 30% of your tracked conversions are false positives (duplicate events, bot form fills, internal traffic), Smart Bidding learns to target users who fire false conversions — not real customers. Garbage in, garbage out.

Accuracy checklist:
– Internal traffic filtered out via GA4 data filter
– Bot traffic excluded
– Test conversions excluded
– No duplicate conversion tags (GA4 import + native tag simultaneously)
– Conversion event fires only on genuine completion (not on form page load)

9. Conversion Window Settings

The conversion window determines how long after an ad click or impression a conversion is attributed to that ad interaction.

GA4 conversion window settings:
Admin → Attribution Settings

• Acquisition conversion window: How long after first acquiring a user do you attribute conversions? Default is 30 days.
• Other conversion events window: Default is 90 days.
• Engaged-view conversion window: For video ads, how long after a view counts. Default is 3 days.

Google Ads conversion window settings:
Tools → Conversions → select conversion action → Settings → Conversion window

• Click-through conversion window: 1, 7, 14, 30, 60, or 90 days
• View-through conversion window: 1–30 days

Which window to choose:

Set your window based on your actual sales cycle length, not the default. If your average customer researches for 45 days before converting, a 30-day window is undercounting conversions by design.

10. Verifying Conversion Events

Verification before launch is non-negotiable. An unverified conversion event in a live campaign is a liability.

Step 1: GA4 DebugView
Enable debug mode (GTM Preview or Chrome extension) → complete the action (form submit, purchase, phone click) → in GA4, go to Admin → DebugView → verify:
– Event appears with correct name
– All expected parameters are present with correct values
– Event is marked with a conversion icon (blue lightning bolt) if it’s a conversion

Step 2: GA4 Realtime Reports
Reports → Realtime → Event count by event name. Complete a conversion action and watch for the event to appear within 30 seconds. Check that it appears in the Conversions widget at the top of the Realtime report.

Step 3: Google Ads Tag Assistant
Install Tag Assistant companion Chrome extension → enable recording → complete a conversion → view the recording → verify the GA4 event fired with the correct Measurement ID and event name.

Step 4: Google Ads Conversion Status
In Google Ads → Tools → Conversions → check the Status column for imported GA4 conversions:
– “Recording conversions” with a recent date = working correctly
– “No recent conversions” = verify the event is firing and imported correctly
– “Tag inactive” = the linked GA4 property is not sending data

11. Conversion Event Planning Worksheet

12. GTM GA4 Event Tag Builder Guide

FAQ

Q1: Can I mark the same event as a conversion in both GA4 and have a separate Google Ads conversion tag?
Technically yes, but you should not. Running both creates duplicate conversion counting in Google Ads — the same action gets counted twice, inflating conversion data and corrupting Smart Bidding signals. Choose one approach: either GA4 import (recommended) or native Google Ads tags, not both.

Q2: How do I exclude internal traffic from conversion data?
In GA4: Admin → Data Filters → Create Filter → Internal Traffic → define your office IP addresses → set the filter to Active. This applies to all data, including conversions. In Google Ads, exclude internal IP addresses in the Campaign → Settings → IP Exclusions section.

Q3: What happens to conversion data if I unmark an event as a conversion?
GA4 stops counting future instances of that event as conversions. Historical conversion data (before the toggle-off date) remains in reports. This is useful if you’ve accidentally marked a high-volume non-meaningful event as a conversion and want to clean up your data going forward.

Q4: My form submit event is not appearing in the GA4 Events list. Why?
The Events list only shows events that have fired in the last 28 days. If your contact form hasn’t been submitted in that period, the event won’t appear. Solution: submit a test form (use DebugView to verify it fires), then the event will appear in the list within 24–48 hours.

Q5: How many conversion events is too many?
GA4 allows up to 30 conversion events per property. For most businesses, 3–8 conversion events is optimal. Too few (1–2) misses important micro-conversion signals. Too many (15+) makes reports difficult to interpret and can dilute Smart Bidding training data if all are sent to Google Ads.

Q6: Should I use GA4 conversions or Google Ads conversion tracking?
For new implementations: use GA4 conversions imported into Google Ads. For existing setups already running Google Ads tags with years of historical data: keep the Google Ads tag for campaigns where Smart Bidding is trained on it, and run GA4 in parallel. Switching abruptly can reset Smart Bidding learning periods.

Conclusion

Conversion event configuration is where analytics theory becomes business practice. The setup chain — custom event via GTM, marked as conversion in GA4, imported into Google Ads, verified in DebugView — is the infrastructure that makes every bidding decision, every budget allocation, and every funnel optimization evidence-based rather than assumption-based.

The most common mistake is rushing this setup: marking page_view as a conversion, sending string values to numeric parameters, or running duplicate tags simultaneously. Each takes 10 minutes to cause and hours to diagnose.

Do it once, do it correctly, verify everything in DebugView, then build campaigns on a foundation that will not shift under you.

Need conversion tracking implemented and verified? Ignited Nepal sets up GA4 conversion events, GTM configuration, and Google Ads import as part of our analytics foundation service. Book a free consultation at ignitednepal.com/cro/

Written by the Ignited Nepal team. ignitednepal.com