Start with access and a written measurement plan
Before changing measurement settings in a Google Ads account, confirm that you can manage the account and the website or app where events will be measured. An account being delivered to you does not automatically provide control over every related property, tag, analytics account, domain, or payment arrangement. Check that the access you have is appropriate for the work, and ask the relevant owner or administrator to grant any missing access through official channels.
Treat the account as a working product that must be operated within Google’s terms and policies. Do not try to work around a restriction, verification request, or access control. If you find an account issue, use the official support or appeal process and address its cause. Keep account ownership, business information, and access details accurate.
Before installing anything, write a short measurement plan. For each action you want to measure, note what a real user does, where it happens, and why it matters to the business. Also record who can confirm that the event is working, who controls the relevant website or app, and where you will document the final setup. This keeps the configuration understandable when access or responsibilities change.
Use this checklist as a preparation guide, not as a substitute for current product instructions. Google Ads and Google Analytics interfaces and setting names can change. Check Google’s official help pages for the current steps and definitions before making changes.
Define the conversion actions you actually need
- List the meaningful actions a visitor or customer can complete, such as submitting a lead form, making a purchase, or completing a key step in an app.
- For each action, describe the event in plain language. Be specific enough that another person can distinguish it from a page view or a general site visit.
- Decide whether the action is a primary outcome for campaign optimization or is useful mainly for observation and reporting. Check the current Google Ads guidance on conversion action goals and optimization settings.
- Identify which actions represent distinct outcomes. Avoid setting up several conversion actions that all count the same user action unless you have a clear reporting reason.
- Confirm whether the action takes place on a website, in an app, or in another supported flow. The implementation and available import options can differ.
Do not create conversion actions just because an option is available. A long list of loosely defined events can make reports harder to interpret and may direct optimization toward activity that is not useful. Conversely, do not omit an important step simply because it is less visible than a final transaction. The right scope depends on the business process and the decisions you need to make from the data.
Write down what should count and what should not. For example, if the intended action is a completed form submission, distinguish that from opening the form or clicking its submit control before the submission succeeds. Confirm the expected behavior with the person responsible for the site or app.
Choose how each action will reach Google Ads
For every conversion action, decide whether to use a Google Ads tag or import an event from Google Analytics, where that approach fits your measurement setup. Do not assume that both methods are needed for the same action. Duplicate measurement can cause the same outcome to appear more than once in reporting or optimization.
A Google Ads tag may be suitable when the action is measured directly for Google Ads. An Analytics import may suit a setup in which events are already collected and reviewed in Google Analytics. The appropriate choice depends on the existing implementation, access, reporting needs, and the current capabilities described in Google’s documentation.
Before implementing either route, check:
- Which account or property owns the existing measurement setup.
- Whether the event already exists and whether its definition matches the action you intend to count.
- Whether a tag or event is already sending the same outcome to Google Ads.
- Who can make and verify changes to the website, app, or analytics configuration.
- Whether the selected conversion action is configured for the reporting and optimization role you intend.
If you inherit a setup, inspect it before adding new measurement. Ask for a description of existing tags, events, and account links, then compare that description with what you can see in the relevant Google interfaces. If ownership or access is unclear, resolve that through the account owner and official support channels rather than creating a workaround.
Install or import the event carefully
For a direct tag setup, follow the current Google Ads instructions for the selected conversion action. Confirm that the tag is placed or triggered in the intended context and that it does not fire merely because someone visits an unrelated page. If a tag management system is already used, coordinate with its administrator and follow the current instructions for that system as well.
For an Analytics import, first make sure the intended event is being collected in the correct Google Analytics property and has a clear, consistent definition. Then use Google’s current help guidance to link the relevant accounts and import the appropriate event or conversion. An event existing in Analytics does not, by itself, prove that it is available in Google Ads or that the import is configured correctly.
Keep a record as you work. Note the conversion action’s purpose, the measurement method, the website or app location, the responsible administrator, and any relevant account or property identifiers. Record the setting location in words that will still make sense if the interface changes, such as the product area and the type of setting, rather than relying only on an old screenshot or a button label.
Avoid copying tags or event configurations from an unrelated account without checking their ownership and purpose. Do not use false identity details, borrowed credentials, or hidden account relationships to complete setup. If you lack the permissions needed to implement measurement, request legitimate access from the appropriate owner.
Link Google Ads and Google Analytics where appropriate
An account link is a connection between products; it is not the same thing as an event being recorded. If you plan to import Analytics events, check that the Google Ads account is linked to the intended Google Analytics property and that the link is active and accessible to the people responsible for the setup. Follow Google’s official instructions, since the navigation and labels may change.
Check that you are connecting the right accounts. Similar names or multiple properties can make it easy to select the wrong destination. Record which Google Ads account is linked to which Analytics property, who administers each side, and where the link can be reviewed. Confirm that the link is permitted and appropriate for the account and business arrangement.
A link can be present while no relevant events are collected. The reverse diagnostic is also useful: an event may exist in Analytics, but the accounts may not be linked, the event may not be imported, or the action may not be configured as intended in Google Ads. Check each layer separately rather than treating “linked” as proof that measurement is complete.
Do not link accounts simply because they are available. Use a connection only when it supports the measurement plan and you have authority to manage both sides. If the account is restricted, under review, or awaiting verification, do not try to use another account to bypass that state. Resolve the matter through Google’s official channels.
Run a test event before spending budget
Test measurement before launching paid traffic. A campaign can generate activity without giving you reliable evidence that the intended conversion is being recorded. If the event is missing, duplicated, or firing at the wrong point in the user journey, reports and optimization may be misleading. Testing first helps you catch configuration problems before they affect campaign decisions.
Use a controlled test that follows the same path a genuine visitor would take, without submitting false business information or creating misleading transactions. If the action involves a live purchase or another consequential process, coordinate with the site owner on an appropriate test method. Do not create fake leads or transactions merely to force a signal.
During the test, check the relevant layers:
- Did the intended site or app event occur?
- Did the tag or Analytics event register in the appropriate product?
- If importing, is the Google Ads and Analytics link active and does the intended event appear in the import setup?
- Is the corresponding conversion action configured for the intended role?
- Does the reporting view show the event as expected, allowing for any processing or interface behavior described in Google’s current documentation?
A test tool or status indicator can help identify implementation problems, but no single status should be treated as proof of the entire setup. Check the current Google help pages for how diagnostics work and what their statuses mean. If results are unclear, pause campaign activation and ask the relevant site administrator or Google support for help.
Diagnose “no events” versus “events not linked”
When Google Ads shows no event activity, first determine whether an event is being generated at all. Test the website or app flow and inspect the relevant tag or Analytics event using the available official diagnostics. If nothing registers at the source, investigate the implementation, trigger conditions, consent or access configuration where applicable, and whether the tested action actually completed.
If the event is visible in Google Analytics but not in Google Ads, the issue may be farther along the chain. Check whether the correct accounts are linked, whether the event is eligible and selected for import, and whether the conversion action is configured as intended. Confirm that you are inspecting the right account and property. A visible Analytics event is evidence that collection occurred there, not proof that Google Ads received or imported it.
If Google Ads has a conversion action but reports no activity, check whether its tag or import path is functioning, whether the action corresponds to the event you tested, and whether the reporting view you are using is appropriate. Consult Google’s documentation for the current meaning of status messages and reporting delays; do not infer a precise cause from a label alone.
If the event appears more than once, compare the direct tag and import configurations and look for overlapping measurement. Correct the underlying setup rather than ignoring the duplication in reports. When you cannot tell whether a problem is in the site implementation, account link, import, or reporting view, document what you tested and contact the responsible administrator or Google’s official support channel.
Keep a handover record and recheck changes
Measurement is easier to maintain when the configuration is documented. Keep a concise record that includes the conversion action’s business meaning, its measurement method, the related website or app event, the Google Ads account and Analytics property involved, and the person or team responsible for each part. Note where the setting is located, using current product terminology where possible.
Record the test path and outcome, including what you verified and what remains uncertain. Do not store passwords, sensitive customer details, or unnecessary personal data in the handover note. Keep access under the control of the legitimate account owner and use Google’s supported access-management processes.
Recheck measurement after changes to a site, app, tag configuration, analytics property, account permissions, or linked accounts. A previously working event can stop firing or begin firing under different conditions after an implementation change. Before starting or adjusting paid activity, review the conversion actions and test the path that matters to the campaign.
For every unresolved issue, state the next responsible party and the official channel to use. Current settings, eligibility, and troubleshooting steps are described in Google Ads and Google Analytics help and policy pages. Use those sources for the latest instructions, and fix the underlying cause rather than working around a restriction or creating an unverified setup.