Demand Gen uses conversion information to report and optimize performance. Configure a conversion that represents the business result, then prove it works before publishing.
Install and validate the Google tag plus the completion event that represents the campaign's real outcome.
BY THE END OF THIS LESSON, YOU CAN
- 01Define one primary conversion and its completion state
- 02Choose an appropriate Google tag installation method
- 03Configure the event or phone snippet correctly
- 04Reconcile test conversions with the business system
BEFORE YOU BEGIN
- Administrator or tag-manager access to the website
- The exact primary conversion and confirmation state
- Google Ads administrator access
- A test form, booking, call, or purchase path
- Privacy and consent guidance for the business and market
THE GMAIL ADS PATH
Conversion tracking
THE LEAD ATLAS METHOD
A Lead Atlas Data list can be built for the same campaign categories and regions while the Gmail conversion system measures which paid visitors become usable business outcomes.See how custom list research works ↗Why this step comes now
Google's current guidance uses the Google tag with an event or phone snippet for website conversion tracking. A base tag alone does not prove that the important action is recorded correctly.
This is guide 4 in the ordered Gmail Ads path. Finish the account, ownership, measurement, and campaign decisions in sequence so later settings do not sit on an incomplete foundation.
Prepare before opening the platform
Collect the information and permissions first. Platform setup becomes confusing when the owner, billing country, destination, offer, or success event is still undecided.
Use real business details and individual user access. Do not share passwords, create placeholder businesses, or let an outside provider become the only person who can control an asset.
- Administrator or tag-manager access to the website
- The exact primary conversion and confirmation state
- Google Ads administrator access
- A test form, booking, call, or purchase path
- Privacy and consent guidance for the business and market
Create, install, and test the conversion
Open Goals or the current conversion area in Google Ads, create the website conversion action, install the Google tag through an approved method, add the event for the completed action, and use diagnostics plus a real test.
Platform labels and recommendations can vary by account, device, country, eligibility, and rollout. Read every on-screen permission and confirmation before saving instead of forcing an older tutorial's wording.
- 01Define the primary conversion
Choose the completed action that creates business value and decide how repeat conversions should count.
- 02Create the conversion action
Use accurate category, value, counting, attribution, and primary-action settings.
- 03Install the Google tag
Place it across the website through a supported integration, tag manager, or careful code implementation.
- 04Install the event
Trigger the event only when the intended lead, booking, purchase, or call condition occurs.
- 05Test and reconcile
Complete the path, inspect diagnostics, and match the Google Ads record with the business system.
Installed site-wide or connected through an approved platform route.
Runs only at the intended completion point.
Receives and diagnoses the conversion action.
Confirms the lead, booking, call, or purchase.
Simplified website conversion path based on Google's current tag guidance.
Make the marketing decision explicit
Use one primary conversion for the first campaign and keep page views, button clicks, and form starts as secondary diagnostics when they do not represent completed value.
Write the choice in the campaign brief, including the person responsible and the evidence that would justify changing it. Clear decisions make later troubleshooting much faster.
Avoid the three most common measurement mistakes
Do not install the same Google tag through a platform integration, tag manager, and hard-coded site at the same time without a deliberate architecture. Do not fire the conversion when the form opens instead of when it succeeds. Do not optimize toward every easy interaction as a primary action.
Test with an identifiable record and timestamp. Check the event under relevant mobile and consent conditions, then match it with the CRM, calendar, call system, or order database.
A troubleshooting starting point, not a substitute for the current Google tag diagnostics.
Verify before continuing
Do not treat a saved screen as proof that the setup works. Test the customer path, confirm access from the correct accounts, and record the current state before continuing.
If one check fails, fix it at this stage. Adding more campaigns, assets, or automation on top of a broken dependency usually makes the original problem harder to locate.
- The tag is detected
- One completed action creates one conversion
- Test events can be identified
- The business system receives the same outcome
- Consent and sensitive-data handling are appropriate
Move to the next guide
Continue to guide 05 and prepare the mobile landing page, images, logo, headlines, descriptions, business name, and CTA required for the Gmail ad.
Keep a short setup record with the date, asset names, owner, destination, and current status. That record becomes the baseline for the next guide and for future access reviews.
KEY TERMS
Create the Google conversion test ledger
Record conversion name, category, value method, counting, primary status, trigger, tag source, consent state, test time, Google diagnostic result, and matching CRM or order record.
THE TAKEAWAY
Complete this checkpoint before moving forward: One verified Google Ads conversion action that records the campaign's primary lead, booking, purchase, or other real customer outcome. The next guide assumes this work is finished and verified.OFFICIAL REFERENCES