Tracking Audit
Goal: find gaps, duplicates, consent issues and unreliable events.
Potential deliverables
- Audit checklist
- Findings summary
- Prioritized fixes
- Implementation recommendations
Services
Concrete, modular support — from the initial assessment to a documented handover.
Service packages
The exact scope is shaped around your requirements, setup and team.
Goal: find gaps, duplicates, consent issues and unreliable events.
Goal: create a clean event structure, maintainable tags and useful GA4 data.
Goal: enable more robust data collection and cleaner vendor forwarding.
Goal: align tracking with consent state and improve trust in analytics data.
Goal: make raw analytics data useful for analysis and decision-making.
Collaboration
A transparent process keeps goals, implementation and data quality in view.
Discuss goals and open questions, then decide whether a full audit is necessary.
Analyze the existing setup at the appropriate depth and identify concrete areas for action.
Define measurement logic, events, consent dependencies and responsibilities.
Support teams with a maintainable, pragmatic implementation.
Systematically test events, data flows and relevant quality criteria.
Hand over results, decisions and next steps in a clear format.
Common questions
Privacy-compliant tracking treats GDPR and other relevant legal and privacy requirements as implementation guardrails. Consent and rejection signals from the consent manager determine which analytics or marketing measurements may run. If data is collected without consent, it should be collected without identifiers: no user IDs, client IDs, advertising IDs, cookie IDs, device fingerprints, or other personal or pseudonymous identifiers should be sent.
An audit reviews events, analytics and marketing tags, consent signals, data flows, and analytics settings such as GA4 settings. The findings and possible next steps are then discussed and prioritized together.
Server-side tracking helps control which data is sent to analytics and marketing platforms and which data is not. It can make data flows more robust and maintainable; whether it fits depends on goals, architecture, consent, and operational feasibility.
A tracking concept is developed together with stakeholders from business, marketing, or product management. It translates business goals and requirements into a concrete tracking implementation plan for IT and implementation teams.
A consent manager records whether users consent or reject. Its consent signals control which measurement and marketing activities may run or send data, ensuring those choices are respected.
BigQuery makes raw analytics data accessible through SQL and allows it to be combined with data from other systems such as shop systems or marketing platforms. This supports data models, reporting workflows, and continuous data quality monitoring.
Projects start with a short discussion of goals, stakeholders, and open questions. Together, we decide whether a full audit is needed or a short analysis of the existing setup is the right first step.
Collaboration can be project-based or continuous; both models are billed monthly. Continuous collaboration has no fixed monthly minimum: it can be 0 hours one month, 2 hours the next, or 3 days when needed. I can prepare a proposal if required.
Next step
Let’s discuss your requirements and a useful starting point.
Let’s discuss your requirements and a useful starting point.
Get in touchLet’s discuss your requirements and a useful starting point.
Choose an introduction timeLet’s discuss your requirements and a useful starting point.
View CV