Shoryaku AI

GA4 vs Google Ads conversions: why counts differ and how to check

Marketing14 min

If GA4 and Google Ads show different conversion counts, do not add another tag immediately. First check whether you are comparing the same outcome, scope, date basis, and counting method. Definition differences and missing measurement require different responses.

This guide provides a comparison sheet to separate expected definition differences, discrepancies that need tracking investigation, and cases with insufficient information. In our own investigation, GA4 signup events and an unreceived Google Ads action could not be compared before aligning their scope.

What differs between GA4 and Google Ads conversions?

GA4 measures website and app activity as events, with important actions designated as key events. Google Ads conversions report actions configured as advertising outcomes.

Even if both measure signup, all-traffic totals and outcomes attributed to advertising cover different scopes. Website-tag measurement and GA4 imports also have different routes to investigate.

Look beyond the name: identify what triggers the event, where it is sent, and which column reports it before reviewing the possible causes below.

Separate events, key events, and actual signups

Even when signup is your goal, these figures may count different things.

Figure What it counts First check
Actual signup records Completed registrations in the service Whether tests or duplicates are included
GA4 event count Occurrences of a sent event Whether it fires before signup completion
GA4 key event count Events designated as outcomes Event name and counting method
Google Ads conversions Ad outcomes for selected actions Actions, reporting column, and period

A signup-button click is different from a completed signup. A total across several GA4 key events is also different from signup alone. Start by selecting the specific event you want to compare, such as sign_up.

All-traffic GA4 key events and outcomes credited to Google Ads have different scopes. A site-wide total including organic search and direct visits need not match ad outcomes. Google's guide to creating conversions from GA4 events explains scope and date-related discrepancies.

Align six comparison conditions

Condition What to check in GA4 What to check in Google Ads
Scope Property, event, and traffic scope Account, campaign, and conversion action
Measurement route Event marked as a key event Website tag or GA4 import
Column and goals Event count or key event count Conversions or All conversions; goals in use
Dates Outcome date, period, time zone Ad interaction or outcome date, period, time zone
Counting Once per event or session One or Every; action-specific settings
Freshness and history Retrieval time and key event changes Import start, receipt status, conversion window, changes

1. Website tags and GA4 imports are different routes

For a Google Ads website tag, seeing an event in GA4 does not prove that the Ads tag sent the conversion. For a GA4 import, check the linked property and Ads account and which event is included.

Several actions with similar names do not establish double counting. Check which route each action uses and which actions the campaign actually uses.

2. Check primary, secondary, and campaign goals

Normally, primary actions appear in “Conversions,” while secondary actions appear in “All conversions.” Bidding use also depends on the campaign's goals. A secondary action included in a custom goal is an exception: it is used in reporting and bidding. See Google's explanation of primary and secondary actions.

Do not conclude that a secondary action has no effect, or that two primary actions necessarily mean double counting. Inspect action-level figures and goals. Changing an action to primary just to align totals may also change the outcomes bidding optimizes for.

3. The same date range can use different date bases

The standard Google Ads conversion column assigns an outcome to the ad interaction that led to it. GA4 key events use the date the outcome occurred. A click at month-end followed by a signup in the next month can therefore create different monthly figures.

Inspect Google Ads columns based on conversion time when investigating date differences, and align time zones. Matching dates does not guarantee matching counts if scope or counting rules still differ.

4. Once per event and One are not the same counting rule

GA4 key events can be counted once per event or once per session. Google's counting-method documentation explains that changes do not apply retroactively.

Google Ads also has action-specific counting settings. Record both settings and when they changed. Check suspected repeated event sends or completion-page reloads. Do not directly equate unique signup records with event counts.

5. Today's gap alone does not prove lost measurement

Metrics do not all update simultaneously. Google Ads data freshness documentation describes differences by metric and measurement method. For recent outcomes, record retrieval time and decide when to check again.

Do not assume that GA4 history from before an import began will be backfilled into Ads. Check whether the measurement route was active during the period when outcomes occurred.

How we separated GA4 events from an unreceived Ads action

In our investigation, GA4 showed signup events over the previous 28 days, and signup was marked as a key event. The Google Ads signup action, however, indicated that it had not yet received data.

The advertising account had a website-tag signup action, while the manager account had a GA4-imported signup action. The Search campaign we inspected used the website-tag action, not the GA4-imported one.

We could establish three things:

  • GA4 had observed the event.
  • The campaign used a different measurement route.
  • GA4's previous 28 days and outcomes immediately after ad launch were not aligned scopes.

We could not conclude that every GA4 event was missing from Ads or that both signup actions were being used for bidding. Before adding tags, our next checks were the route, goals in use, actual ad-driven signups, and receipt status.

Steps to investigate a conversion discrepancy

  1. Select one outcome, such as signup or purchase.
  2. Identify the GA4 property, Ads account, campaign, and action.
  3. Compare traffic scope, date basis, counting method, and goals.
  4. Separate update delays from outcomes with unconfirmed receipt.
  5. Reconcile against actual records and choose the measurement route to investigate.

If definitions explain the difference, document the comparison conditions instead of forcing settings to match. If an outcome occurred but delivery is unconfirmed, investigate event destinations and triggers with the measurement owner.

Before changing settings, review bidding implications. Adding actions or making them primary solely to match totals can change what advertising optimizes for.

A comparison sheet to copy

Start with settings and aggregate figures. Do not paste personal information or account credentials into an external AI tool.

Business outcome:
Records used to verify actual outcomes:
Period, time zone, and data retrieval time:

GA4:
- Event being compared:
- Event count or key event count:
- All traffic or an advertising-specific figure:
- Key event counting method:
- Configuration date and change history:

Google Ads:
- Campaign and conversion action:
- Website tag or GA4 import:
- Primary/secondary, goals in use, any custom goal:
- Conversions or All conversions:
- Ad interaction date or conversion time:
- Counting method and conversion window:
- Tracking/import start, diagnostics, and receipt status:

Classification:
- Differences explained by definition or scope:
- Actual outcomes requiring tracking investigation:
- Differences with insufficient information:

Next screen or record to check, owner, and review conditions:

If an outcome occurred but receipt is unconfirmed, investigate event timing, destination, association with ad clicks, and consent state with the person responsible for measurement. Tag loading alone is not successful outcome transmission. Our zero-impression and measurement checklist makes this distinction too.

Ask ChatGPT or Gemini to organize the checks

Append this to the completed comparison sheet:

Organize the difference between GA4 and Google Ads outcome counts.
Use only the supplied settings and aggregate figures.

Rules:
- Do not recommend settings changes merely to make totals match.
- Separate all traffic from ad outcomes, and events from actual signups.
- Multiple actions alone do not establish double counting.
- Tag loading alone does not establish conversion receipt.
- Do not fill in unknown settings or figures.

Output:
1. Aligned comparison conditions and conditions that differ
2. Definition differences, tracking investigations, and unresolved gaps
3. The next screens or records to check and what each will establish
4. Effects of any proposed change and what to record before changing

Review figures together without adding overlapping outcomes

For CPA, record which outcome is the denominator. The high Google Ads CPA checklist moves from measurement checks to cost and outcome analysis. For reporting, add definitions and unresolved items to the monthly marketing report template.

Shoryaku AI brings connected GA4 key events and Google Ads cost and conversions into one view. You can discuss changes in chat and summarize them in a monthly review. Start with channel-specific figures rather than adding overlapping counts as total signups. Tracking changes and reconciliation against actual signup records remain separate work.

Shoryaku AI's reporting features show how to review collected figures together with the actions you took.