Track the outcome you would pay for
Conversion tracking connects an ad interaction with a useful business action: a purchase, completed enquiry or qualified phone call. A loaded page or a clicked button can help diagnose a journey, but neither proves that a customer finished it.
Start by writing the event in plain language: “a visitor successfully submits the quote form”, rather than “someone clicks Submit”. The event definition should survive a failed form, a page refresh and a visitor returning later.
An installed GTM container is only the starting point
Google Tag Manager loads the tags published in a container. Its snippet does not prove a Google Ads conversion tag exists, uses the right account or fires at the right time. Check the container ID on the website, the published version and the trigger attached to the conversion tag.
Site to Spend can prepare conversion actions and publish tracking where the required permissions and integration are available. A website owner may still need to install the container or expose a reliable success event. Access to an existing container is required to change it.
Choose primary and secondary conversions deliberately
For a standard goal, a primary action is eligible for bidding when the campaign uses that goal. Secondary actions normally appear in “All conversions” for observation; a custom goal can also use secondary actions for bidding. Google explains the distinction in its primary and secondary conversion guide.
A useful starting point is a completed enquiry as the primary outcome, with pricing views and contact-button clicks recorded separately. Do not promote easy page visits into the main bidding goal simply to make the conversion count larger.
Worked example: one enquiry, one conversion
Hypothetical implementation example, not a customer result. A business has a quote form. After the server accepts it, the site shows a confirmation and emits a dedicated quote_request_success event.
- A visitor clicks an ad and lands on the service page.
- The form fails validation. No success event should fire.
- The visitor fixes the form and submits it. The accepted submission fires the success event once.
- The confirmation is refreshed. The same lead should not be counted again.
Use a submission or transaction identifier where your integration supports deduplication. Keep the identifier free of personal details. For a purchase, use the actual order value and currency; a lead value should be a defensible estimate, not a pretend sale.
Test the complete path before changing bids
- Open the site in GTM Preview and Tag Assistant and confirm you are testing the live container.
- Complete the real success action and verify that the intended tag fires once, after success.
- Check the Google Ads conversion ID and label against the intended customer account and action.
- Confirm the campaign uses that conversion goal, with the appropriate primary action.
- Test the consent states relevant to your visitors. Do not bypass consent controls to make a test look successful.
- Check a later real ad-attributed conversion in Google Ads after reporting has processed it.
Tag Assistant confirms implementation behaviour. A direct test visit without an attributable ad interaction does not prove a paid-ad conversion will appear in reports. “No recent conversions” can also reflect low volume; distinguish it from a tag failing to fire.
Keep website analytics and Google Ads reporting separate
Your website can count a successful enquiry even when Google Ads has no eligible ad interaction to attribute it to. Different attribution windows and reporting delays can also produce different totals. Reconcile a small sample of actual leads rather than demanding that every dashboard agree instantly.
Once the signal is trustworthy, use it to assess budget pacing and campaign delivery problems. If you want help preparing a campaign, compare ongoing management with a one-time setup and handover.