The short answer
AI can remove much of the navigation and settings work from Google Ads conversion management. A good workflow still separates three different jobs: creating a native Google Ads conversion action, importing an existing GA4 key event, and updating an action that already exists.
Those jobs are not interchangeable. Creating an action does not install its tag. Importing a GA4 event requires an existing Analytics link and key event. Updating whether an action is primary can change the signal used by Smart Bidding.
The safest pattern is simple: inspect first, choose the correct measurement source, preview the intended settings, make one controlled change, and validate the full tracking chain before trusting the numbers.
Table of Contents
Start with the measurement decision, not the button
Before creating anything, decide where the conversion should originate.
Use a native Google Ads website conversion when Google Ads should own the conversion action and the Google tag or Google Tag Manager will send the event directly.
Import a GA4 key event when the event is already defined and validated in Analytics, and you want that same event available for Google Ads reporting or bidding.
Update an existing action when the measurement source is correct but its name, category, value, counting behavior, lookback window, status, or primary/secondary role needs attention.
Do not create a new action merely because an old one looks untidy. Duplicate lead or purchase actions are easy to introduce and can silently inflate the Conversions column or send mixed signals to automated bidding.
Step 1: review the current setup
Begin with an inventory, not a mutation. Check auto-tagging, the account's conversion-tracking status and ownership, existing conversion actions, GA4 link evidence, and which GA4 key events are already imported or available to import.
Copyable prompt
Review conversion tracking for Google Ads account [CUSTOMER_ID]. Show auto-tagging, conversion-tracking status and ownership, existing conversion actions, GA4 properties detected, imported GA4 key events, and events available to import. Do not change anything. Flag possible duplicates by business outcome.
A clean review should answer five questions:
- Which outcomes does the business actually want campaigns to optimize toward?
- Which platform currently owns each event: Google Ads, GA4, another import source, or an offline process?
- Are two actions measuring the same lead, sale, booking, or signup?
- Which actions are primary and therefore eligible to influence standard goal-based bidding?
- Is the event firing and deduplicating correctly in the browser, tag manager, and destination platform?
A missing GA4 signal is not always proof that the accounts are unlinked. If the linked property has no synced key events, the Google Ads surface may not provide enough evidence to distinguish that from an absent link. Confirm the connection in the interfaces before diagnosing the integration as broken.Step 2: create a native Google Ads website conversion action
For a new website conversion, define the settings before asking AI to create it. At minimum, specify a clear name and category. For a production-ready decision, also review counting, primary/secondary status, value behavior, and conversion windows.
A practical setup brief
Name: Demo request - website
Category: Submit lead form
Count: One per ad interaction for lead generation
Optimization: Secondary until the tag is validated and duplicate actions are ruled out
Value: Use a deliberate fixed value only if it represents the business outcome; otherwise preserve dynamic values when they are available
Click-through and view-through windows: match the realistic consideration cycle and the account's measurement policy
Copyable prompt
Create a native Google Ads website conversion action in account [CUSTOMER_ID].
Name it 'Demo request - website', use the submit-lead-form category, count one per click, set it as secondary for now, and use the approved conversion windows.
Before creating it, summarize the proposed settings and warn me if a similarly named action already exists.
The creation step only creates the Google Ads object.
It does not install a Google tag, create a GTM trigger, confirm consent behavior, or prove that the conversion fires once.
Treat the returned conversion ID and label as implementation inputs, not as evidence of working measurement.Step 3: implement and validate the website signal
Complete the browser-side implementation before making the action primary.
Install the Google Ads event through the Google tag or Google Tag Manager.
Pass value, currency, and transaction ID when the business case requires them.
Test the actual user journey, not only a tag preview screen.
Verify that one real action produces one platform event and that repeat page loads or refreshes do not create duplicates.
Check diagnostics and the conversion-action status after data has had time to arrive.
Keep the action secondary until it is technically valid and strategically intended for bidding.
Google's current setup guidance distinguishes URL-based, code-based, and Google Tag Manager implementation paths. The right path depends on whether the conversion can be defined by a page URL or needs richer event data such as values and transaction IDs.
Step 4: import an existing GA4 key event
Use the GA4 path when the event is already defined and tested in Analytics. Before importing it, confirm that Google Ads and GA4 are linked, auto-tagging is enabled, the event is marked as a key event, and the exact event name is visible to Google Ads.
Copyable prompt
In Google Ads account [CUSTOMER_ID], show GA4 key events available to import.
Find event [EVENT_NAME] from GA4 property [PROPERTY_ID].
If there is one exact match, import it as a secondary conversion, keep its existing value behavior unless I explicitly approve a change, and return the final settings.
Do not import anything if the match is ambiguous.
Use the property ID when the same event name exists in more than one linked property.
Also expect sync delays: an event may not appear immediately after it is marked as a key event or after the accounts are linked.
Google may initially treat Analytics-based conversions as secondary to reduce the risk of bidding on duplicate goals.
That is a useful safety default, not an instruction to switch every imported action to primary.
First compare it with any existing native Google Ads action measuring the same outcome.Step 5: update one setting at a time
Existing conversion actions often need cleanup after a takeover, tagging migration, CRM change, or shift to value-based bidding. AI is most useful here when it turns a vague request into a precise before-and-after change.
Common updates include:
Rename an action so its business outcome and source are obvious.
Change its category for clearer goal grouping and reporting.
Choose one-per-click or many-per-click counting to match leads versus transactions.
Set or revise default-value behavior without overriding trustworthy dynamic values by accident.
Change click-through or view-through lookback windows when the current settings do not match the buying cycle.
Move an action between primary and secondary only after checking which campaigns and goals rely on it.
Pause or otherwise change status only where the action type, origin, ownership, and Google Ads rules permit it.
Copyable prompt
Inspect conversion action [CONVERSION_ACTION_ID] in account [CUSTOMER_ID].
Show the current value settings, counting type, category, lookback windows, attribution model, status, and primary/secondary role.
Then propose the smallest change needed to [BUSINESS_OBJECTIVE].
Do not apply it until I approve the exact before-and-after fields.
Not every field is editable for every action.
The source, ownership, conversion type, and Google Ads eligibility rules can restrict changes.
If an action cannot be edited safely, preserve it and recommend the correct migration or replacement path instead of forcing a mutation.How to review changes that affect bidding
Primary and secondary are operational settings, not labels. Primary actions normally feed the Conversions column and can influence Smart Bidding through the goals a campaign uses. Secondary actions remain available for observation in All conversions without becoming the default optimization target.
Before changing an action to primary, review:
The campaigns using account-default goals or campaign-specific goals.
Whether another action measures the same business outcome.
Recent conversion volume, lag, and value quality.
Whether the action represents a true business result or a shallow engagement event.
The timing of other major budget, bid-target, landing-page, or measurement changes.
After a material goal change, annotate the date and monitor both reported volume and downstream lead or revenue quality. Avoid stacking several unrelated changes into the same evaluation window.
Use HireOtto as the action layer - with review gates
HireOtto can keep this workflow in one conversation: review conversion-tracking readiness, distinguish imported GA4 events from events available to import, create supported native conversion actions, import an eligible GA4 key event, and update supported settings such as name, category, counting, primary status, values, attribution, and lookback windows.
The useful boundary is equally important. HireOtto does not make a newly created website action start tracking by itself. A person still needs to implement and test the website or GTM signal, resolve consent and deduplication, confirm the intended business goal, and approve changes that can alter reporting or bidding. Some settings remain restricted by Google Ads based on the action's type, source, or ownership.
Use the Manage Google Ads conversions walkthrough for the end-to-end product flow, consult the Google Ads MCP tools reference for current parameters and limitations, and follow the HireOtto quickstart to connect your AI assistant.
Final review checklist
The business outcome and measurement owner are clear.
No existing action measures the same event in a way that would double count.
The action name identifies both the outcome and source.
Counting and value behavior match the business model.
Primary/secondary status is intentional and campaign-goal dependencies were reviewed.
The browser or server event was implemented and tested outside the Google Ads object-creation step.
Consent, transaction IDs, and deduplication were checked where relevant.
The change was documented and performance will be monitored before another major optimization change.
Frequently asked questions
Can AI create a Google Ads conversion action?
Yes. An AI assistant connected through a write-capable workflow can create supported conversion-action objects. That does not automatically implement or validate the website signal required to record conversions.
Can AI import a GA4 event into Google Ads?
Yes, when the Google Ads and GA4 accounts are already linked and the event is available as a GA4 key event. If multiple properties expose the same event name, identify the property explicitly.
Should an imported GA4 conversion be primary?
Not automatically. Keep it secondary while you rule out duplicate goals and validate data quality. Make it primary only when it is the intended bidding signal for the relevant campaigns.
What is the difference between One and Every?
One is usually appropriate when repeated completions after one ad interaction should count once, as with many lead forms. Every is commonly used when each transaction has value, as with purchases. The business model and event design should decide the setting.
Can HireOtto install the conversion tag?
Creating a website conversion action does not install or test its Google tag or GTM configuration. Complete and validate that implementation separately before relying on the action for reporting or bidding.
About Me
I’m Suyash – badminton junkie, ex‑GroupM ad‑ops grunt, first marketer at a B2B SaaS startup, and creator of Hiretto: Google Ads MCP Server.
My mission: less clicking, more thinking.
Let’s build leverage together.