Chapter 11
Maintenance and monitoring
Table of contents
Server-side tracking is not a project that ends on go-live day. Platforms change their interfaces, store systems get updates, cookie banners are replaced. Any of these changes can quietly distort your measurement.
Why do tracking errors go unnoticed for so long?
Because broken tracking does not produce an error message in the store. The store keeps selling; only the numbers are wrong. If the purchase event disappears after an update, marketing sees a revenue drop that isn't real and may cut campaigns that are performing well. If a tag fires twice after a plugin update, campaigns look better than they are. Both are often only noticed weeks later.
What does regular maintenance include?
Configuration check: Do all important events arrive completely, especially purchases and leads?
Data reconciliation: Do measured purchases remain in a stable ratio to actual orders?
Interface updates: Google, Meta and other platforms regularly change their APIs and requirements. The tag templates in the server container need to stay up to date.
Consent check: After changes to the cookie banner, do marketing tags still not fire without consent?
Server load: Is the booked plan still sufficient, or is the data volume approaching the limit?
Troubleshooting: Using the tracking server's logs, DebugView in GA4 and the ad platforms' diagnostics.
When should you check additionally?
Regardless of the fixed schedule: after every store update, after theme or template changes, after switching cookie tools, after installing new apps or plugins and before high-revenue periods such as Black Week.
Who is responsible for maintenance?
This question should already have been answered in the pre-analysis. Three things need to be defined: how often checks take place, who verifies that everything works and what happens when something looks wrong. Without this, nobody ends up owning the tracking, and that is exactly when the expensive mistakes happen.
Can it be automated?
Partly. An automatic daily comparison of store orders with measured purchases reveals breaks within a day rather than after weeks. arboro clients see such metrics in arboro.PULSE, the diagnostic system for online stores. The professional judgment of why a deviation occurs remains a human task.
Questions for your maintenance plan
Is it defined how often tracking is checked?
Is it defined who is responsible for the check and who is informed when something looks wrong?
Is there a regular comparison between store orders and measured purchases?
Is tracking briefly tested after every store update?
Frequently asked questions
At least monthly, and additionally after every change to the store, the cookie banner or apps. A separate check before high-revenue periods is worthwhile.
)