--- title: "Running analytics as an ongoing practice" description: "Analytics decays without ownership Sites change, campaigns launch, developers refactor, new tags appear, people leave. Without an operating rhythm, even…" url: https://optimizeall.com/learn/web-analytics-with-ga4/analytics-operating-rhythm updated: 2026-10-05 --- Web Analytics with Google Analytics 4 · Attribution, dashboards and analytics operations · lesson 18 of 20 · 10 min # Running analytics as an ongoing practice ## Analytics decays without ownership Sites change, campaigns launch, developers refactor, new tags appear, people leave. Without an operating rhythm, even a perfect implementation degrades within months. Treat analytics like a product with owners, routines and documentation. ## Roles and responsibilities (RACI-lite) | Activity | Responsible | Accountable | Consulted | Informed | |---|---|---|---|---| | Measurement plan | Analyst | Marketing lead | Leadership, sales | Whole team | | Tracking plan and tags | Analyst / implementer | Analytics owner | Developers | Marketing | | Data layer | Developers | Tech lead | Analyst | Marketing | | Consent and privacy | Analyst + legal | Data protection lead | Developers | Leadership | | Dashboards and reporting | Analyst | Marketing lead | Channel owners | Stakeholders | In a small business or solo consultancy, one person may hold several roles — the point is that each activity has a named owner. ## The rhythm ``` DAILY (5 min) Realtime/overview sanity check during active campaigns; alerts review WEEKLY (30 min) KPI review vs target; channel and landing page movers; anomaly notes MONTHLY (2 hrs) Tracking QA script on top journeys; PII audit; UTM Unassigned review; dashboard commentary; access review for leavers QUARTERLY (1 day) Measurement plan review; tracking plan clean-up; consent re-audit; attribution/experiment roadmap; stakeholder feedback on dashboards ON EVERY RELEASE Developer notice -> QA script -> change log -> annotation ``` ## The change log A shared change log is the cheapest, highest-value analytics artifact: ``` | Date | Change | By | Reason | Data impact | |------------|--------------------------------------|--------|------------------------|------------------------------| | 2026-03-02 | generate_lead moved to DL push | Hassan | Thank-you page false +ve | Leads drop ~ expected | | 2026-03-10 | Added gateway to unwanted referrals | Emma | Referral misattribution | Paid revenue rises | | 2026-04-01 | Consent default denied for EEA/UK | Legal | Compliance | Fewer observed users (EEA) | ``` When a number moves unexpectedly, the change log is the first place to look. ## Auditing an inherited property Agencies and new hires often inherit a messy GA4 property. A structured audit: 1. **Access and ownership** — who owns the account; who has admin; remove stale users. 2. **Configuration** — retention, filters, unwanted referrals, cross-domain, key events, links. 3. **Implementation** — duplicate tags, tag manager container state, data layer quality. 4. **Data quality** — (not set) rates, Unassigned channel share, PII leaks, revenue reconciliation. 5. **Consent** — pre-consent firing, CMP configuration, non-Google tags. 6. **Reporting** — which dashboards exist, who uses them, what is broken. Score each area (for example red / amber / green), then present a prioritized fix plan with effort and impact. ## Building analytics culture - **Teach questions, not clicks.** Train stakeholders to ask good questions; they will find the reports. - **Celebrate decisions made with data**, including decisions to stop something. - **Be honest about uncertainty.** Say "directionally" and "illustratively" when appropriate; credibility comes from calibrated claims. - **Keep documentation close to work** — link the tracking plan and glossary from the dashboard. ## Worked example: a 90-day plan for a new analyst ``` Days 1-30 Audit, access clean-up, fix critical issues (duplicates, gateway referrals, PII), agree measurement plan with leadership. Days 31-60 Rebuild tracking plan; implement key events via data layer; UTM builder launch; consent audit and fixes. Days 61-90 Leadership dashboard with commentary; weekly review rhythm live; first incrementality test designed with the paid media team. ``` ## Hands-on: automate the boring parts of the rhythm - **Daily**: a BigQuery scheduled query (module 3 health query) posts key-event and page-view anomalies to a team chat channel. - **Weekly**: a Data API script pulls the KPI table into a sheet; an AI assistant drafts the first version of the commentary from the aggregated table using a fixed prompt; the analyst edits and approves. - **Monthly**: the PII scan and UTM leak query run automatically; results are reviewed in the monthly session. - **Quarterly**: an AI assistant compares the tracking plan against the event names seen in the export and lists events that are live but undocumented, or documented but no longer firing: ```sql SELECT event_name, COUNT(*) AS events_30d FROM `my-project.analytics_123456789.events_*` WHERE _TABLE_SUFFIX >= FORMAT_DATE('%Y%m%d', DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)) GROUP BY event_name ORDER BY events_30d DESC; -- Compare this list with the tracking plan: undocumented events -> document or remove; -- documented events with zero volume -> investigate or retire. ``` ## Next steps To go deeper on consent-aware collection, server-side tagging and conversion APIs, take the **Privacy-First Measurement** course. To turn your GA4 data into decisions with AI-assisted analysis and statistics you can defend, take **AI for Data Analysis and Decision Making**. ## Second worked example: a Dubai e-commerce team's 90-day turnaround A new analyst inherits a property with duplicate tags, no change log and a dashboard nobody trusts. Days 1 to 30: audit, remove the hard-coded duplicate, fix payment-gateway referrals, add the PII scan. Days 31 to 60: rebuild the tracking plan, move purchase to a data layer push, launch the UTM builder, run a consent audit. Days 61 to 90: a leadership dashboard on BigQuery summaries with a weekly commentary, and the first geo holdout designed with the paid media team. At day 90, leadership meetings reference the dashboard by name, which is the real sign that the rhythm is working. ## Common mistakes - No change log, so historical anomalies become mysteries. - One person holds all knowledge and access (a "bus factor" of one). - Audits that list 80 issues without prioritizing. - Stakeholders who only see numbers, never the reasoning. - Routines that exist on paper only: if the weekly review keeps getting canceled, shrink it rather than abandon it. ## Handover pack Whenever an analyst, agency or freelancer changes, a handover pack prevents knowledge loss. It should contain the measurement plan, tracking plan and definitions register, the tag manager container export and version notes, the UTM taxonomy and builder, the consent configuration and privacy register, dashboard links with owners, the change log, and a list of open issues with priorities. Keep it in a shared location owned by the business, not in anyone's personal drive. ## Maturity checklist - [ ] Named owner for every analytics activity - [ ] Weekly and monthly routines running - [ ] Change log and annotations maintained - [ ] Release process includes analytics QA - [ ] Audit completed and fix plan prioritized ## Video lecture: Running analytics as an ongoing practice Lecture coming soon · 14 chapters · about 8 minutes. Read the full transcript below. 1. The analytics operating rhythm 2. Why it matters 3. Roles 4. The rhythm 5. The change log 6. Auditing an inherited property 7. Automate the rhythm 8. Example 1: a solo consultant 9. Example 2: a 90-day turnaround 10. Measuring the rhythm 11. Watch me do it 12. Culture 13. Mistakes and recap 14. Try this now ## Lecture transcript ### The analytics operating rhythm Here's a hard truth about analytics. You can build a perfect implementation in January, and by June it will be quietly broken. Sites change, campaigns launch, developers refactor, new tags appear, and people leave. Analytics decays without ownership. In this lecture you'll learn how to run analytics like a product: roles and responsibilities, a daily, weekly, monthly and quarterly rhythm, the change log, how to audit an inherited property, how to automate the boring parts, and how to build a culture where data is trusted. ### Why it matters Why does this matter? Because every number your organization trusts depends on dozens of small things staying correct: tags, triggers, consent settings, UTM habits, definitions. Without routines, those things drift, and nobody notices until a big decision is made on a broken number. An operating rhythm turns analytics from a project into a product, with owners, routines and documentation. It's not glamorous. It's the reason some teams trust their data and others don't. ### Roles Start with roles. Think of a simple RACI: who's responsible, accountable, consulted and informed. The measurement plan: the analyst is responsible, the marketing lead accountable. The tracking plan and tags: the analyst or implementer responsible, the analytics owner accountable, developers consulted. The data layer: developers responsible, the tech lead accountable. Consent and privacy: analyst and legal responsible, the data protection lead accountable. Dashboards: the analyst responsible, the marketing lead accountable. In a small business, one person holds several roles. The point is that every activity has a named owner. ### The rhythm Now the rhythm itself. Daily, five minutes: a sanity check during active campaigns, and alert review. Weekly, thirty minutes: K P Is versus target, channel and landing page movers, anomaly notes. Monthly, two hours: the QA script on top journeys, the PII audit, the Unassigned review, dashboard commentary, and an access review for leavers. Quarterly, one day: measurement plan review, tracking plan clean-up, consent re-audit, the attribution and experiment roadmap, and stakeholder feedback. And on every release: developer notice, QA script, change log, annotation. ### The change log The cheapest, highest-value analytics artifact is the change log. Date, change, who, reason, and data impact. For example: the second of March, generate lead moved to a data layer push, by Hassan, because the thank-you page created false positives, and leads dropped as expected. When a number moves unexpectedly, the change log is the first place to look. Think of it like a flight recorder. You hope you never need it, but when something goes wrong, it tells you exactly what happened. ### Auditing an inherited property Agencies and new hires often inherit a messy property. Audit it in six areas. Access and ownership: who owns the account, who has admin, remove stale users. Configuration: retention, filters, referrals, cross-domain, key events, links. Implementation: duplicate tags, the container's state, data layer quality. Data quality: not set rates, Unassigned share, personal data leaks, revenue reconciliation. Consent: pre-consent firing, the C M P setup, non-Google tags. And reporting: which dashboards exist and who uses them. Score each red, amber or green, then prioritize by impact and effort. ### Automate the rhythm Now automation, which makes the rhythm sustainable. Daily, a BigQuery scheduled health query posts anomalies to a team chat. Weekly, a Data A P I script pulls the K P I table into a sheet, and an AI assistant drafts the first version of the commentary from the aggregated numbers, which the analyst edits and approves. Monthly, the PII scan and UTM leak query run on their own. And quarterly, a simple query lists every event name seen in the last thirty days, which you compare with the tracking plan. ### Example 1: a solo consultant First example, a simple one. A solo consultant runs analytics for three small clients. She can't do everything, so she shrinks the rhythm to fit. A weekly twenty-minute review per client, reading from an automated sheet. A monthly thirty-minute check with the QA script on the top journey and the PII scan. And a quarterly one-hour review with each client. Her rule: if a routine keeps getting canceled, shrink it rather than abandon it. A small rhythm that runs beats a big one on paper. ### Example 2: a 90-day turnaround Second example, a business case. A new analyst at a Dubai e-commerce company inherits duplicate tags, no change log, and a dashboard nobody trusts. Days one to thirty: audit, remove the hard-coded duplicate, fix payment gateway referrals, add the PII scan. Days thirty-one to sixty: rebuild the tracking plan, move purchase to a data layer push, launch the UTM builder, run a consent audit. Days sixty-one to ninety: a leadership dashboard on BigQuery summaries with weekly commentary, and the first geo holdout designed with the paid media team. ### Measuring the rhythm How did they know it worked? At day ninety, leadership meetings referenced the dashboard by name, and the change log explained the two numbers that moved unexpectedly that quarter. That's the real measure of an operating rhythm: people use the data in decisions, and surprises have explanations. Other signs: fewer escaped errors found by stakeholders, faster answers to how was this measured, and no single person who holds all the knowledge. ### Watch me do it Watch me run the quarterly event inventory. In BigQuery, I select event name and count events over the last thirty days, sorted by volume. Then I paste that list next to the tracking plan. Two lists come out of the comparison. Events that are live but undocumented: either document them or remove the tag. And events that are documented but show zero volume: investigate whether they broke, or retire them. This week, I find a leftover test event from a vendor and a signup event that stopped firing after a redesign. ### Culture Building culture matters as much as routines. Teach questions, not clicks: train stakeholders to ask good questions, and they'll find the reports. Celebrate decisions made with data, including decisions to stop something. Be honest about uncertainty: say directionally and illustratively when you mean it, because credibility comes from calibrated claims. Keep documentation close to the work, linked from the dashboard. And whenever an analyst, agency or freelancer changes, hand over a pack: plans, container export, UTM taxonomy, consent setup, dashboards, the change log and open issues. ### Mistakes and recap Common mistakes. No change log, so historical anomalies become mysteries. One person holding all knowledge and access. Audits that list eighty issues without prioritizing. Stakeholders who only see numbers, never the reasoning. And routines that exist on paper only. Recap: run analytics like a product, with owners, a daily-to-quarterly rhythm, a change log, prioritized audits, automation with human approval, and honest communication. ### Try this now Try this now. Create a change log and a monthly analytics routine for your organization or a client, and schedule the first review in your calendar. If you have the BigQuery export, run the event inventory query and compare it with your tracking plan. And if you're ready to go deeper, the Privacy-First Measurement course covers consent-aware collection and server-side tagging, and AI for Data Analysis and Decision Making will help you turn these numbers into defensible decisions. ## Key takeaways - Analytics degrades without owners and routines — run it like a product. - A change log is the first place to look when numbers move unexpectedly. - Audit inherited properties systematically and prioritize fixes by impact. - Credibility comes from calibrated, honest claims about data quality. ## Try it Create a change log and a monthly analytics routine for your organization or a client, and schedule the first review in your calendar. - [Previous: Dashboards that drive decisions](https://optimizeall.com/learn/web-analytics-with-ga4/dashboards-that-drive-decisions) - [Next: The GA4 BigQuery export: setup, schema and SQL you will reuse](https://optimizeall.com/learn/web-analytics-with-ga4/bigquery-export-and-sql) - [All lessons of Web Analytics with Google Analytics 4](https://optimizeall.com/learn/web-analytics-with-ga4)