Set up Google Ads conversion tracking by defining a valuable business action and sending the conversion only when its success condition is met. Treat an accepted enquiry, a completed purchase and a confirmed booking as different actions, then test consent, repeated events and the campaign goal that uses each signal.
Before increasing advertising spend, establish which measurement you can trust. A visitor can tap a phone link without starting a conversation. A form button can be clicked while validation prevents submission. Reloading an order confirmation page can fire a purchase tag again. If those situations appear as equivalent business results, campaign decisions become difficult to defend.
This guide covers the decisions involved in website lead and purchase measurement. Account menus and available setup methods can change, so use the current interface alongside Google's official documentation. If you want help reviewing the existing implementation, explore WeAreMedia's conversion tracking services.
Write the success condition before creating the tag
Create a small measurement register. Record the business objective, the action on the website, the evidence of success, the system holding that evidence and the person responsible for the next step. For a quotation form, the website action is submission, the immediate success condition is acceptance by the application, and the later business step is qualification by the sales team.
A phone or WhatsApp link can provide a useful intent signal. Give the event a name that describes the action you can observe. A link click, an accepted enquiry, a qualified opportunity and a signed order belong to different stages. Start by reporting the stage your systems can verify. Add a later stage when the business has a reliable process for recording it.
Consider an illustrative installation business that receives quotation requests and job applications through a shared form. Before treating every accepted message as an advertising goal, distinguish the form's purpose or the sales team's outcome. This is a planning example. It does not describe a client campaign or establish a conversion rate.
| Action | Evidence required |
|---|---|
| Phone link | A link click |
| Accepted form | Application success response |
| Purchase | Unique order and amount record |
| Appointment | Confirmed booking record |
Confirm ownership and map the existing implementation
The business should retain control of its advertising account, analytics property and tag management system. Give the people doing the work access appropriate to their task. Record which account IDs belong to the site and who maintains the existing tags. That register makes a future agency handover or website change easier to manage.
Use platform access controls instead of sharing passwords. Avoid beginning an audit by deleting existing conversion actions. Live campaigns may rely on them. First establish which actions are active, which tags send to them, which campaign goals use them and where the reporting history is held. Record the starting configuration so subsequent changes have an explanation.
An implementation can also include a website builder, an ecommerce app and custom page code. Check all of those sources. Adding a new tag to a site that already sends the same action through another integration can create an apparent performance improvement that comes entirely from counting the action twice.
Choose a measurement route the team can maintain
Review the setup methods offered for your website in the current account. A direct Google Ads implementation and an eligible Google Analytics event imported into Google Ads can support different existing architectures. If the same lead or purchase is created through both routes, decide which conversion action will be used for campaign optimisation and which will be used for observation.
Maintenance matters alongside the initial setup. Who publishes the tag manager container? Who tells the measurement owner when the checkout or form changes? Is the linked Analytics property the intended one? Answer those questions before replacing the current route. Google's website conversion setup instructions describe the options available through its interface.
The implementation record should state the chosen source, the receiving account and the action being measured. A person reviewing the account six months later should be able to trace an event from the website to the relevant conversion action without guessing from an abbreviated tag name.
Review primary and secondary conversion actions
Use clear action names and categories. A label such as "quotation request accepted" is easier to interpret than "form" when several forms serve different purposes. Decide how values will be assigned as well. A purchase amount and an enquiry value require different business logic. If the business has no defensible model for lead value, avoid inventing a revenue figure for the event.
Google explains that primary actions can be used for bidding when the associated goal is used by the campaign. Secondary actions are generally observational, with an exception for actions included in a custom goal. Check the campaign's actual goal configuration as well as the action setting. Google's primary and secondary action guidance explains those distinctions.
For example, an accepted quotation request might be a business goal while a phone-link click is a supporting observation. That is a possible design, not a universal recommendation. A business that closes most sales by phone needs a separate review of its call measurement and its ability to verify outcomes.
Measure acceptance of the form
A submit-button click is insufficient evidence that an enquiry reached the application. Browser validation, a network problem or a server response can stop the process. Connect the measurement to a success signal from the form system. If the site uses a thank-you page, include direct entry and page reload in the acceptance tests.
Where several forms share the same success screen, use a standard form identifier to distinguish them. Keep the visitor's name, email address, phone number and free-text message out of general Analytics event parameters. A controlled service or market code may answer the reporting question without sending the contents of the enquiry.
Repeated submissions need a clear business rule. Preventing a page refresh from generating another lead should not suppress a genuinely new enquiry. Review the success identifier and application behaviour with the developer. A browser-only workaround may be inadequate if the same transaction can arrive through several channels.
Check purchase IDs, amounts and currencies
Define which stage of the checkout counts as a completed purchase. Payment confirmation, order creation and a later order-management status may represent different stages. The measurement plan should identify the chosen one. The amount and currency should come from the corresponding transaction record, with a consistent approach to tax, shipping and discounts.
A unique transaction ID helps Google Ads identify repeats for the same conversion action. Use a real identifier for each purchase. A fixed example value reused across transactions can cause undercounting. If a browser tag and another upload route report the same transaction, check identifier consistency across the two. Google's transaction ID documentation covers this behaviour.
Acceptance tests should include reloading the confirmation page, returning to it through browser history and checking the result against a safe test record. Work with the operational owner to choose an appropriate test environment. The test should verify the implementation without creating misleading production orders or customer messages.
- Define the action
- Verify success
- Check consent and data flow
- Test repeated events
Consider enhanced conversions after the base event is reliable
Enhanced conversions supplement an existing measurement setup using first-party data. Google distinguishes website and lead use cases. Check the current requirements for data preparation, the implementation channel and account eligibility. Enabling the feature does not repair a basic conversion event that fires before the intended business action has succeeded.
Hashing also does not settle every question about the collection and use of personal information. Assess the permitted data, visitor information, consent and platform terms. Sending an email address inside a general Analytics event is a different implementation from using an authorised enhanced-conversion data flow. Google's enhanced conversions overview is the starting point for that review.
Keep access to the implementation and its documentation limited to the people who need it. The business should know which system sends the data, which team maintains the mapping and what happens when a form field or checkout integration changes. Include this information in the handover.
Test the visitor's consent choices
Write the expected behaviour for a first visit, necessary cookies only, analytics consent, advertising consent and a later preference change. The site's default state and subsequent updates must match the measurement approach selected by the business. Check both the visible preference controls and the network behaviour of the tags.
Google's Consent Mode guide describes setting defaults and updating them following the visitor's choice. The technical implementation should follow the business's privacy assessment. If a preference is withdrawn, check that tags do not continue under an earlier state. Use the current Consent Mode implementation guide when reviewing these steps.
Include mobile navigation and restored browser sessions in the test plan where they affect the journey. A banner that works only on the first desktop visit is incomplete. The test record should explain which states were exercised and which behaviour was observed, rather than simply stating that consent was enabled.
Agree an acceptance checklist
- Test invalid, incomplete and successful form journeys separately.
- Confirm the intended account and conversion action receive the event.
- Compare tag manager preview with the platform's diagnostic information.
- Check repeat behaviour when the success page reloads.
- Verify purchase ID, amount and currency against a safe transaction record.
- Exercise the same business rules on mobile and desktop.
- Check rejected consent and later preference changes.
- Record the implementation date, owner and next review point.
Close the test with an evidence record. Describe the scenario, the expected event and the observed result. Keep examples free of customer information. The record becomes particularly valuable when a website redesign, form supplier or checkout update changes the journey later.
Interpret the reports after launch
Google Ads and Analytics totals can differ because their definitions, reporting dates, attribution and consent conditions differ. Compare the same action and completed reporting period before drawing conclusions. A phone-link event and a salesperson's completed conversation should not be added together as two equivalent leads.
For enquiry businesses, establish a recurring sales feedback process. Define invalid, duplicate, unsuitable and qualified requests. Once the classification is reliable, consider how later outcomes can inform advertising decisions. The campaign team needs to know whether an increase came from more relevant demand, a changed form or a revised measurement rule.
Read the reports together with operational capacity. A campaign can produce enquiries that the team cannot answer quickly enough. That is a different problem from a tag that fails to fire. Keep implementation defects, traffic quality and the handling of genuine requests visible in the review.
Scope, timing and practical next steps
The work depends on the number of forms, checkout integrations, existing tags, domains, markets and available access. Start with an inventory so the quotation reflects the implementation you actually need. Specify the event list, acceptance tests, responsibilities and post-release review in the scope.
If you also use Meta advertising, review the relevant setup through our measurement services. For campaign structure and ongoing decisions, see Google Ads management. When you contact WeAreMedia, share the site address, the business action you want to measure and the tools currently in use. Discuss a conversion tracking review so we can identify the missing success condition and agree the work required.
