how-to
How to Track PPC Conversions in Google Analytics
Table of Contents
- What You Need Before You Start Tracking PPC Conversions
- Step 1: Define Your PPC Conversion Goals and Key Events
- Step 2: Configure the Google Tag and Conversion Tracking Tag
- Step 3: Importing GA4 Conversions to Google Ads
- Using Google Tag Manager for PPC Tracking
- Step 4: Verify Your Conversion Status and Test Tracking
- Troubleshooting Google Ads Conversion Tracking Issues
- Conclusion
- Frequently Asked Questions
Last Updated: September 27, 2026
What You Need Before You Start Tracking PPC Conversions
According to Google Analytics Help, GA4 now supports custom integer lookback windows for click-through conversions, with windows of 1, 7, 14, 30, 60, or 90 days. That flexibility matters when you're trying to track PPC conversions in Google Analytics, because your sales cycle decides which window actually tells the truth.
- A linked Google Ads account with admin access
- A GA4 property with the Google tag installed on every page
- A clear list of the actions that count as a conversion
- Tag Manager access if you want cleaner event tracking
Step 1: Define Your PPC Conversion Goals and Key Events
A key event is any user action you've marked as important in GA4, such as a form submission, phone call, or purchase. Google now uses key events as the main way to measure conversions. Most accounts get this wrong by marking everything, treating every page view as a conversion floods your reports with noise.
Pick the actions that map to real business value:
- Contact form submissions
- Phone calls from your site
- Quote requests
- Demo bookings
- Purchases or signed contracts
Marking Key Events in GA4
In GA4, go to Admin, then Events. Find the event, toggle "Mark as key event," and assign a value if you track revenue. That value feeds your conversion value reporting later.
Step 2: Configure the Google Tag and Conversion Tracking Tag
The Google tag is the base code connecting your site to GA4 and Google Ads. Every page needs it, and it must fire before any event trigger runs. Two paths:
| Method | Best For | Setup Time | Flexibility |
|---|---|---|---|
| Direct gtag.js | Simple sites, one or two events | 15-30 minutes | Low |
| Google Tag Manager | Multiple events, custom triggers | 1-2 hours | High |
Setting Up Event Triggers and Data Layer Variables
Event triggers tell Tag Manager when to fire a conversion tag. A data layer is the JavaScript object that passes values from your site to Tag Manager, like order totals or lead types. Build your data layer first, then triggers off it, to keep event parameters clean and reporting accurate.
Step 3: Importing GA4 Conversions to Google Ads
Importing GA4 conversions to Google Ads starts with linking the accounts. In GA4, go to Admin, then Product Links, and connect Google Ads. Then in Google Ads, go to Tools, then Conversions, and import your key events. Here's what most guides miss: not every imported event should be a primary action.
- Primary action: the conversions Google Ads bids toward
- Secondary action: useful data, but not used for bidding
Using Google Tag Manager for PPC Tracking
Google Tag Manager for PPC tracking gives you one place to manage every tag, trigger, and variable tied to your campaigns. Instead of editing site code for each new conversion, you publish a container update.
Step 4: Verify Your Conversion Status and Test Tracking
Verification is where most accounts quietly break. You think tracking works until you compare Google Ads to your CRM and find a 40% gap. The fix is a layered verification pass that catches different failure modes at different funnel stages.

Layer 1: Confirm the tag actually fires
Open Google Tag Manager, click Preview, and load your landing page. You should see, in order:
- The Google tag (GA4 configuration) firing on page load
- Your conversion event firing on the trigger you built (form submit, thank-you page view, click)
- The event parameters,
value,currency,transaction_id,lead_type, populated with real values, notundefined
Layer 2: Confirm the event reaches GA4
Go to Reports → Realtime in GA4 and submit a test conversion. Your event should appear within 30 seconds under the configured name. Then go to Admin → Events and confirm it's marked as a key event, an event that fires but isn't marked as a key event will never appear as a conversion in Google Ads, no matter how clean your tag is.
Layer 3: Confirm the conversion reaches Google Ads
In Google Ads, go to Goals → Conversions → Summary. Newly imported GA4 conversions show "No recent conversions" until the first is recorded, then move to "Recording conversions", expect a 24-48 hour delay. If it still reads "Inactive" after 72 hours, the import link is broken; re-check Admin → Product Links in GA4.
Schedule a Free Consultation →
Layer 4: Reconcile against a source of truth
This step is where trust is won or lost. Pick one conversion type, usually your highest-volume lead, and reconcile it three ways over a 7-day window:
| Source | What it counts | Typical variance vs. CRM |
|---|---|---|
| Google Ads | Clicks attributed to ads, per Google's model | Highest |
| GA4 | Sessions attributed per GA4's model and lookback | Middle |
| Your CRM or backend | Actual form submissions and orders | Lowest (ground truth) |
Troubleshooting Google Ads Conversion Tracking Issues
Most troubleshooting guides stop at "check your tag", useless once your tag is confirmed firing and the numbers still don't match. The four issues below account for the vast majority of real-world PPC tracking problems, each with a specific mechanism you can inspect.
Data discrepancies: why Google Ads and GA4 never match
Google Ads and GA4 will not match, and they aren't supposed to. Three mechanisms drive the gap:
- Different attribution models. Google Ads defaults to data-driven attribution across its own click and view data. GA4 defaults to data-driven as well but only sees sessions it can observe. A conversion that Google Ads credits to a click may be credited by GA4 to a different channel entirely.
- Different lookback windows. GA4 supports custom integer lookback windows for click-through conversions, 1, 7, 14, 30, 60, or 90 days, per Google Analytics Help. Google Ads uses its own windows per conversion action. If the two are set differently, the same conversion can be counted by one system and dropped by the other.
- Modeled conversions. When consent signals are absent, Google fills gaps with modeled conversions. Those appear in Google Ads but have no GA4 counterpart.
Conversion lag: the 24-72 hour window
Conversion lag is the delay between a user's click and the conversion being attributed back to it, because Google Ads waits to see whether a click converts before finalizing the number. For lead-gen accounts, most lag resolves within 24-48 hours; for high-consideration purchases, it can stretch to 72 hours or more. The operational rule: never judge a campaign the day it launched, and never pause or scale on a 24-hour snapshot.
Consent Mode V2: the signals you lose without it
Consent Mode V2 is Google's framework for adjusting tag behavior when a user declines or hasn't yet given cookie consent. Without it configured, users who decline cookies send no conversion signal at all, a meaningful share of conversions depending on your traffic mix.
Cross-domain tracking: when the session splits
Cross-domain tracking breaks when your landing page and your checkout or thank-you page sit on different domains or subdomains. Without proper configuration, GA4 treats the second domain as a brand-new session with a new user, and the conversion is attributed to "direct" instead of your PPC campaign.
Quick diagnostic reference
| Symptom | Likely mechanism | Where to look |
|---|---|---|
| Numbers don't match | Different attribution models and lookback windows | Compare in one system, not both |
| Conversions missing entirely | Tag not firing or event not marked as key event | Tag Manager Preview, GA4 Admin → Events |
| Reporting looks low for 1-3 days | Conversion lag | Wait 72 hours before editing |
| Conversions attributed to "direct" | Cross-domain session split | GA4 data stream domain settings |
| Signal drops after cookie banner | Consent Mode V2 not fully wired | CMP → Google tag consent parameters |
Conclusion
Tracking PPC conversions correctly is the difference between scaling what works and burning budget on guesses. Most accounts lose data to broken tags, wrong primary actions, and missing server-side setup, and they never know it.
Frequently Asked Questions
How can I track conversions in Google Analytics?
Create key events in GA4 by marking important user actions like form submissions or calls. Then link your Google Ads account and import those conversions. GA4 supports custom lookback windows of 1, 7, 14, 30, 60, or 90 days for click-through conversions, so you can match attribution to your sales cycle. Use DebugView to confirm events fire correctly before relying on the data.
How do I test Google Ads conversion tracking?
Use the Google Tag Assistant and GA4 DebugView to watch events in real time. Submit a test form or click a test call button, then check if the conversion action status shows 'Recording conversions.' You can also use the Google Ads conversion tracking tag preview mode in Google Tag Manager. If nothing records, check that your tracking pixel fires on the correct page and that the conversion action is set as Primary.
Why isn't Google Ads tracking my conversions?
Common causes include missing tracking codes on thank-you pages, broken event triggers, or account linking errors. Verify that your Google tag is present on every page and that the conversion tracking tag fires after the user completes the action. Also check that you have marked the conversion as Primary in Google Ads and that Consent Mode V2 is configured properly if you serve users in regulated regions.
Should I use Google Ads conversion tracking or GA4?
Many practitioners use both. Google Ads native conversion tracking is often more reliable for specific conversion steps, while GA4 provides cross-channel context and audience insights. Set Google Ads conversions as Primary and use GA4 events for supplementary performance tracking. This dual approach helps you spot data discrepancies and gives you a fuller picture of campaign performance.