The campaign report shows more enquiries than the inbox. We investigate the tracking with your team: what is counted, where does the discrepancy arise and what needs changing in development?
View the analytics data check See a working exampleWhich figure do you need for the next campaign decision? Identify the report and period. That defines which events should be reviewed.
See the exampleBoth call them enquiries. One may mean a form click and the other an actual received contact. All parties should align those meanings first.
Did the form and tracking change together? Then comparison with the previous month needs an explanation.
For doubts about tracking, choose the analytics data check. The shop diagnosis examines the purchase journey with existing data. For ongoing hosting and service expenditure, consider the technical cost review.
Which events does your tracking actually count? We check one analytics property for gaps and conflicting figures.
We examine one purchase journey and the available analytics data. The report sets out findings, open questions and the next tests.
Hosting, tools and ongoing services: we organise up to ten cost items and include the work involved in a possible switch.
The shop diagnosis does not include a full analytics data check. Your data question determines the choice.
In a GA4 or Matomo review, we trace selected events back to the actions they should represent. A chart alone does not show that connection.
Analytics data checkA click, a submitted form and a saved enquiry are different actions. Analysis needs a defined meaning. For orders, we might check whether reloading the page counts the purchase again.
The report records the agreed action, observed trigger and necessary corrections so marketing and development can discuss the same location.
First align periods, time zones and filters. Then examine collection: duplicate events, missing consent or different campaign attribution. Matomo describes such differences in its documentation.
Sometimes systems intentionally count differently. The report records their definitions rather than prematurely labelling a figure wrong.
Matomo: reasons for differences in analytics reportsIf an event now counts only saved enquiries, its curve may fall without customer behaviour changing. Include the change date in the analysis.
Also record campaign launches and offer changes during the period. Otherwise a relaunch can too quickly receive the blame for changed demand.
The current trigger already sends the Enquiry event.
The form requests a correction. Nothing has been saved.
The person leaves the page, but the report still contains the attempt.
The measurement point comes before the success it is intended to demonstrate.
One specific discrepancy is enough to start. We agree the necessary read access afterwards.
Which metric differs, in which report and for which period? Aggregated information is enough for an initial description.
A new form, tag manager update or relaunch can help locate when the discrepancy began.
Who knows the events? Who can implement a correction? Someone in marketing or development should be able to route questions.
Your team receives findings and verification steps. Open points can be discussed in the included written follow-up round.
Once the initial diagnosis exists and your team has implemented changes, a quarterly review can compare the new state. Record what changed and when.
The review requires this baseline measurement. Start and scope of recurring reviews are agreed separately. Sending an enquiry does not start support.
If no data is collected yet, you first need a measurement plan and setup. The data check reviews existing tracking.
Ask us for advice How a project worksWe agree the key events and period in one tracking environment. Then we investigate when those events fire, which signals are missing and what they can tell you about your question. The analytics data check defines the included scope.
Aggregated figures and the affected journey are enough for the initial description. Read access is agreed separately. Do not send passwords or personal customer records through the enquiry form.
Yes. The review record identifies the location, observed behaviour and suggested verification step. Unresolved causes are explicitly identified. One round of written follow-up questions is included.
Repairs and new setups are separate work. Your developers or agency can take on the tasks. Before implementation, agree how the corrected event will be checked.
After an initial diagnosis, when changes are documented and comparison is possible. The review requires that baseline. An enquiry does not start a subscription or ongoing support.
