A native Google Ads conversion and a conversion created from a GA4 key event can both support Google Ads measurement. Choose based on the business outcome, required Ads features and ownership of the event. Then verify which actions the campaign actually uses.
Two routes to an Ads conversion
A native website conversion uses Google Ads measurement for the agreed action. A GA4-based conversion begins with an Analytics event or key event shared with Ads through the linked setup. Google's GA4-to-Ads conversion documentation explains the account linking and creation path. It also states that imported Analytics conversions do not provide view-through conversions; that feature requires native Ads measurement.
This choice concerns the source and capabilities of an Ads conversion. It is different from asking why the totals in two reports disagree. For that problem, use the existing Google Ads and GA4 reconciliation guide. A reporting difference does not by itself justify replacing your conversion source.
Compare the requirements that affect your decision
| Question | Native Ads measurement | GA4-based conversion |
|---|---|---|
| Who owns the source? | The Ads measurement owner maintains the conversion implementation. | The Analytics event owner and Ads owner need an agreed handoff. |
| Need view-through measurement? | Native Ads measurement is the documented route. | Analytics imports do not provide this feature. |
| Existing reliable GA4 event? | A second implementation needs a clear purpose. | Can reuse that event definition, subject to linking and configuration. |
| Bidding eligibility? | Inspect action optimization and campaign goals. | Inspect the same settings; an import is not automatically the intended bidding signal. |
The practical risk is measuring one business outcome twice as two campaign goals. A transaction identifier within one action is not a general promise that separately configured conversion actions will cancel each other out. Inventory the actions and their business meanings before adding another source.
Primary, secondary and custom goals need a separate review
Google's primary and secondary action documentation says primary actions are used for bidding when the relevant standard goal is used. Secondary actions are generally observational, but actions in a custom goal are used for bidding regardless of their primary or secondary label. That exception makes “we set it to secondary” an incomplete migration check.
Inspect account-default goals, campaign-specific goals and custom goals for the campaigns affected. Record the current configuration before changing anything. A clean event payload can still feed an unintended bidding objective if the campaign configuration is wrong.
One sale, two conversion actions
Illustrative scenario: an ecommerce team has an established Ads purchase action. An analyst adds a GA4 purchase conversion for comparison. Both represent the same completed order. The useful question is not which produces the larger number; it is whether the team intentionally wants both counted in the campaign's selected goal.
A controlled comparison can keep the existing approved bidding signal and examine the alternative observationally, after checking custom-goal exceptions. The team compares event definition, value, currency, counting choices and attribution settings. It documents the reporting differences before deciding whether a source change is warranted.
If the native action fires on a checkout click while GA4 fires on confirmation, the sources are measuring different milestones. Correct the definitions before comparing their counts. If both use confirmation but one omits discounts from value, resolve the value contract. Switching source names will not settle either issue.
A migration brief your Ads owner can review
- Write the business outcome and exact point at which it becomes confirmed.
- List the existing conversion actions, their sources and the campaigns using them.
- State the requirement motivating a change: feature coverage, ownership or a verified implementation limitation.
- Compare values, currency, counting, attribution and reporting timing on a like-for-like basis.
- Specify the observation period, success evidence, authorized switch and rollback plan.
- Check the final campaign goals after the switch rather than relying on an action's label alone.
A GA4-based conversion is reasonable when the existing event is reliable and its capabilities meet the requirement. Native measurement is reasonable when Ads-specific requirements call for it. Maintaining both can be useful for a controlled comparison, but needs explicit ownership and goal settings.
Track & Optimize can review an agreed existing conversion path in a scoped diagnostic. Campaign changes and implementation require their own agreed work. This comparison is decision guidance, not permission to change a live campaign's goals.