GA4 import vs native Google Ads conversion
Both routes bring purchases and leads into Google Ads. They differ in attribution model, latency, value logic and what is possible with enhanced conversions. This comparison shows which route delivers the better bidding basis.
In short
A GA4 import is convenient and gives a shared view with Analytics. It also inherits the attribution logic and processing steps of GA4. A native conversion action measures directly in the Ads account, reacts faster and is the basis for enhanced conversions. In most accounts with serious ad spend the native action is the better bidding basis, and GA4 stays for the analysis.
The differences in detail
A
GA4 import
Conversion taken over from Analytics
B
Native Ads conversion
Measured directly in the Google Ads account
| Criterion | GA4 import | Native Ads conversion |
|---|---|---|
| Data source | The event is processed in GA4 and then transferred to Ads. | The event reaches the Ads account directly. |
| Attribution | Follows the GA4 attribution logic. | Follows the Google Ads attribution logic. |
| Latency | Additional processing and transfer time. | Considerably shorter, which helps bidding. |
| Enhanced conversions | Not the intended route. | The intended route for hashed first-party data. |
| Value and currency | Inherited from the GA4 event. | Set directly from the data layer and verifiable on its own. |
| Transaction ID | Depends on what GA4 received. | Set explicitly and usable for deduplication. |
| Counting method | Dictated by the GA4 definition. | Freely selectable between every and one conversion per click. |
| Debugging | Two systems in which the fault can sit. | One system, with a directly verifiable network request. |
| Analytical value | Consistent with the reports in Analytics. | Can deviate from GA4, which is explainable and gets documented. |
| Migration risk | Low, but the weaknesses remain. | Present: a new action needs comparison data before it becomes primary. |
The import can stay when
- there is little or no ad spend
- analysis in GA4 matters more than bidding
- enhanced conversions are not planned
- there is no access to the data layer
- the measurement is being rebuilt anyway and stability comes first
The native action pays off when
- smart bidding depends on fast and complete signals
- enhanced conversions should be used
- value, currency and transaction ID come reliably from the data layer
- the counting method should be a deliberate choice
- the campaign optimises for revenue rather than completion count
What to watch during the migration
What this comparison does not decide
GA4 and Google Ads will still show different numbers after the switch. That is not a defect but the consequence of different attribution models and processing logic. What matters is that the difference is explainable and documented.
FAQ
Do I have to switch off the GA4 import?
Not immediately. The native action can run as a secondary goal until there is enough comparison data. Only then does the primary goal change and the import gets demoted.
Why do GA4 and Ads deviate from each other?
They use different attribution models, time windows and processing steps. A residual difference is normal. It only becomes notable when the difference cannot be explained or changes abruptly.
Do I lose the history?
No. The existing conversion data stays in the account. What changes is only what the campaigns optimise against from the cutover date onwards.
Does this apply to leads as well?
Yes. The same logic applies to lead generation, with a unique lead ID instead of a transaction ID. Enhanced conversions for leads and later offline feedback build on that.
Are your campaigns optimising against the right basis?
The Tracking Check reviews conversion actions, counting methods, value logic and imports, and shows which change is worth making.