In this article
Start with the business action
A conversion signal begins with a decision about what happened. A checkout click, an accepted payment, and a fulfilled order are different actions. Before changing your tracking infrastructure, choose the action your team actually wants to measure and name the system that confirms it. That agreement prevents a technically successful integration from reporting the wrong outcome.
Write one sentence for each important event: send this event when this condition is true. Then list the information needed to interpret it, such as an order reference, amount, and currency. Keep the initial specification small enough that marketing, engineering, and operations can all review it.
Plan the collection address
A first-party collection domain is an infrastructure choice. Google's server-side tagging guidance describes both a subdomain and a same-origin path as deployment options. The right route depends on who manages your DNS, website delivery, and tagging service.
Choose the address early and record its owner. For a TagVolt project, confirm the exact configuration against current product documentation before making changes. A familiar-looking domain alone does not demonstrate that requests reach the intended container or that the event contains useful information.
Carry the visitor's choices
Consent belongs in the event journey. In Google's documented consent-mode architecture, the browser communicates consent choices to the server container, and Google product tags adjust their behavior. Consent mode itself does not supply the consent banner.
Make consent states part of the acceptance criteria. Ask what should happen before a choice, after acceptance, after rejection, and after a changed choice. Review each destination's behavior instead of assuming every tag follows the same rules. A successful request should never substitute for this review.
Verify the complete journey
Use a small, repeatable test: one action, one known result, and one written expectation. Compare the source action with the collected event and the destination record. Investigate differences in names, values, and repeated sends before considering changes to bidding.
Keep the test evidence with the implementation notes. When a report shifts later, that record helps the team distinguish a collection change from a real change in customer behavior. Better signals begin with an explainable process, and that process needs a clear owner after launch.
