Measurement plan
We define target actions: successful application, registration, purchase. For each, we fix the trigger condition, parameters, and verification method. Clicking a button and submitting a form are different events.
Understand where traffic and purchases are coming from. We adjust the measurement to your business questions and check the data on real site scenarios.
When needed
Ads work, but no purchases reported; applications are counted twice; events disappeared after updating the site; the team compares metrics that mean different things. We start by checking the current data collection so that we don't rebuild what is already working.
Composition of work
We define target actions: successful application, registration, purchase. For each, we fix the trigger condition, parameters, and verification method. Clicking a button and submitting a form are different events.
We check the path from viewing the product to purchase, cost, currency and order ID. If the site does not transmit the necessary data, we prepare a task for the developer.
We coordinate UTM tags, check transitions between domains and payment pages. We prepare reports based on agreed key events, sources and devices.
Let's go through test scripts, check events in DebugView, resubmissions and behavior after user consent. We document the limitations found.
Collaboration result
Event map with parameters, configured GA4 resource, test validation protocol and agreed reports. The team receives an explanation of exactly what is being measured and how to read the indicators. Historical data that was not previously collected is not restored by the setting.
Preparation
Access to GA4, GTM if available, developer contact and list of important site actions are required. For the store, it is possible to make a test order. No need to pass passwords: access is provided through user roles.
Cost
The number of sites and domains, events, payment scenarios, availability of product data and the need for revisions. We agree on the work of a programmer and integration with CRM separately.
After getting acquainted with the task, we agree on the composition of work, terms and cost before the start of cooperation.
Sequence of work
We describe the necessary events, parameters, sources and conditions of operation together with those responsible for the site.
Implementing agreed settings. We check for positive and false positives, duplication and data transfer.
We transfer the event map, inspection protocol and reports. Explaining the difference between a GA4 key event and a conversion for Google Ads optimization.
GA4 collects and displays analytics data. GTM manages the connection of tags and the rules for their activation. They can work together, but solve different tasks.
Reasons can be user consent, blockers, different time zones, rollbacks, duplicates, or transmission errors. We compare the definitions of indicators and test specific scenarios.
Sometimes yes: for example, to transmit the composition of an order or the fact of a successful application. First, we check the available data, then determine the necessary changes.
Let's start with the conversation
A few words about the business and the task. Let's discuss what next step would be useful.