Start with the action, not the tag
A donation, completed volunteer application or confirmed service enquiry has an understandable purpose. A routine homepage visit usually does not show the same commitment. Ask what would happen if Google found many more people completing the action you selected.
A useful intermediate action can support bidding when final outcomes are rare. The choice should reflect your organisation’s actual journey, not whichever event is easiest to generate. Avoid silently replacing donations with low-bar engagement and calling the higher total growth.
Make a measurement map
For each proposed action, record where success happens, who owns implementation, how duplication is prevented and how it will be used. Keep the record short enough that a colleague can understand it.
- Action: what the person successfully completed.
- Evidence: the success event or confirmed transaction.
- Value: a real donation amount or a defensible non-revenue interpretation.
- Use: bidding, diagnosis or reporting only.
- Owner: who can repair it when the site changes.
Test the full journey
A click on “Submit” is not the same as a successful form. Test valid and invalid submissions, the confirmation step, a page refresh and the journey on mobile. Use the platform’s debug tools and compare the result with the actual submission record.
For a donation flow that crosses into a third-party service, check how the integration records success. Do not assume the initial outbound click proves payment. Avoid sending names, email addresses or other personal form fields into Analytics event data.
Check which goals the campaign really uses
Primary and secondary settings matter, but also inspect campaign-specific and custom goals. Google Ads can use an action selected in a custom goal for bidding even when it is secondary. A label in one screen is not a complete audit.
Check duplicate sources too. Importing a GA4 donation and keeping an equivalent Google Ads donation tag as another bidding action can misrepresent outcomes if both record the same payment. Choose the intended measurement architecture and reconcile a sample.
Use GA4 engagement as context
The Google Ads GA4 reporting integration includes engaged-session percentage, events per session and average engagement duration per session where supported. These are diagnostic measures, not automatically valuable conversions.
Compare like with like. A short visit to find opening hours may succeed quickly. A long visit to a difficult application form may indicate friction. More events can also reflect a tagging change rather than a better experience.
Understand gaps before changing the campaign
Clicks and sessions are different measurements. Consent, incomplete page loads, processing delay and attribution choices can create discrepancies. If reporting changes abruptly, inspect the measurement history before concluding that the campaign’s audience changed.
Look at PMax engagement within GA4 when the corresponding imported Ads columns are unavailable. Do not fill missing values with zero or interpret unavailable data as poor performance.
Keep outcomes visible in the monthly report
Separate final outcomes from intermediate actions and diagnostic engagement. State any measurement changes alongside comparisons. End the report with a decision: improve the journey, fix tracking, expand a useful theme or gather more evidence.
Sources and scope
Google documentation supports product and policy details. The diagnostic order and examples are Grant Growth recommendations. Community resources are identified separately; they are not policy exemptions.