Define the business event before configuring tags
A conversion is a completed action that matters to the business, not an interaction that happens to be easy to tag. For ecommerce, that commonly means an accepted order, not an add to cart or payment-button click. For lead generation, it may be a submitted enquiry that meets stated criteria, a booked appointment, or a sales-qualified lead. Write this in business language before translating it into an event.
For each conversion action, record its trigger, inclusion and exclusion rules, value, count rule, identifier, accountable owner, and system of record. Example: “accepted paid order; one event per order ID; order revenue under the company’s stated rule; commerce database reconciles it.”
Use primary and secondary actions deliberately
Google Ads says primary conversion actions appear in the Conversions column and are used for bidding when the relevant standard goal is used for bidding. Secondary actions are for observation in All conversions and ordinarily are not used for bidding. Primary is therefore not a quality badge: it controls the signal optimization learns from.
Make only direct, repeatable campaign outcomes primary. Keep form starts, brochure downloads, account creation, chat opens, and phone clicks secondary unless one is the deliberate optimization outcome. If campaigns serve different objectives, govern goals by campaign rather than letting a generic default steer everything. Note the date and old setting whenever a goal changes so reports are interpreted in context.
Build consent into the measurement design
Consent is not a banner added after tags are live. Google’s consent-mode guidance says to set a default consent state before commands that send measurement data, then update it after a person makes a choice. Its examples cover ad storage, analytics storage, ad user data, and ad personalization. Consent mode does not decide your legal basis or policy; implement the state your organization has approved.
Requirements vary by place and facts. UK ICO guidance says people must be told about cookies, clearly told what they do and why, and give active, clear consent, subject to limited essential-service exceptions. EU business guidance says cookies requiring consent cannot be set on initial load, consent should be purpose-specific, and withdrawal should be easy. Obtain qualified privacy review for your markets, vendors, and data flows. Do not put raw emails, phone numbers, order notes, or unnecessary customer data in URLs, event parameters, or transaction IDs.
Deduplicate the underlying business event
A confirmation page can be reloaded, revisited from history, or reached after a failed state change. Google Ads recommends a unique transaction ID for each purchase so a second conversion with the same conversion action and ID is treated as a duplicate. The ID must be dynamically generated and unique per transaction; reuse across different orders can undercount. Use an opaque order identifier, not customer-identifying data.
Also map the architecture. If a browser tag, server event, CRM import, and payment web hook can report one sale, decide which route is authoritative and which shared ID permits deduplication. An ID does not replace the count setting: one controls how many conversions follow an ad click, while an ID protects the same order from being sent twice. Define a controlled adjustment or exclusion process for refunds, cancellations, and invalid leads with the relevant operations team.
Report attribution as credit, then reconcile to operations
Attribution assigns credit under selected rules; it does not observe every influence or prove causation. Google Ads describes last click as giving all credit to the last-clicked ad, while data-driven attribution distributes credit using account data for that action. The selected model affects the Conversions and All conversions columns and can affect bidding. A model change is therefore both an analysis change and a production optimization change.
Maintain two views. The platform view supports campaign decisions: spend, attributed primary conversions, attributed value, model, window, and date basis. The operating view contains accepted orders, revenue under business rules, qualified leads, cancellations, and refunds. Reconcile directionally and investigate material persistent variance using permitted identifiers. Exact agreement is not expected: consent, browser limits, cross-device paths, timing, eligibility, and modeling can differ.
QA releases as conversion-path reliability work
Test outside production where possible, then use controlled live tests that operations can identify and reverse. Google Tag Manager preview and debug mode connects the previewed site to Tag Assistant, showing fired tags, order, and data processed. Inspect trigger, value, currency, ID, consent state, and destination, then inspect the order or lead record. A green tag status is not proof that the right business event was counted.
Cover paid landing URLs, redirects, form validation, cross-domain checkout, payment return, confirmation, CRM handoff, and refund handling. Google notes that click identifiers can be lost in trackers or redirects and gives cross-domain guidance where landing and conversion domains differ. Preflight and version tag, consent, checkout, and redirect changes. If a path or signal fails, restore the verified configuration and reconcile the affected interval rather than guessing from a dashboard.