---
title: "Define it once: ending analytics drift"
url: https://revworx.ai/insights/define-it-once-ending-analytics-drift/
date: 2026-10-28T15:12:04+00:00
modified: 2026-10-29T06:37:29+00:00
lang: en_US
---

# Define it once: ending analytics drift

Most revenue teams know the meeting. Two systems report a different number of leads for the same month, and the hour that should have gone to acting on the number goes to reconciling it. The cause is rarely a bug. It is definitional drift: two systems counting the same thing slightly differently, because nobody decided which one owns the definition.

## One line, defended

The Data Plane starts by drawing one line: the state your business owns on one side, the data it merely reads on the other.

- **Owned state** has an explicit backup, retention and migration policy, because losing it means losing the business’s memory.
- **Read sources** are dependencies, each with its own rate limits, access terms and chance of disappearing.

![Figure 9. The Data Plane: the line between owned state and read sources](https://revworx.ai/wp-content/uploads/cra-figure-9-data-plane.png)

This line is what makes every other part of the stack replaceable. The master record lives here and in no tool, so any tool can be swapped without a data migration. It also lets the system cache what matters instead of re-querying outside sources on every interaction, which is cheaper, faster and more resilient. That only works once each thing has been assigned to one side of the line.

## Two analytics surfaces, on purpose

Analytics is where stacks quietly acquire two versions of the truth. The architecture runs two surfaces deliberately, with roles that do not overlap.

- **The platform analytics surface owns outcomes:** a lead generated, an appointment booked, a quote requested, a purchase made. These must flow to the ad platforms as conversions and join to spend.
- **The owned analytics surface owns engagement:** page views, guide reads with scroll depth, funnel paths. Because it is self-hosted, unsampled and unaffected by ad blockers, it is a credible owned substitute for third-party intent data.

## The one rule

**Define each event once, on a single surface, and never re-create it on the other.**

That rule is what designs out the reconciliation meeting. A lead is counted in one place. An engagement signal is counted in one place. Nothing is counted twice under two definitions.

## Neither surface is the truth

Neither analytics surface is the source of truth for your business. The CRM holds the master record, and the agent joins all three on the identity of the contact. Analytics tells you what happened. The record tells you who it happened with.

## What can change, and what cannot

The storage behind each store and the set of external sources can change. The line itself does not: which records are the master copy, and where they live. That stability is what lets everything else change.

Key takeaway

Keep the master record outside every tool and defend the line between owned and read. Define each analytics event exactly once. The most stable plane is what lets the others change.

Read the full section: [The Data Plane](/architecture/11/)

Cite as: revWorx (2026). A Composable Reference Architecture for Autonomous GTM Operations, First Edition, §11. revworx.ai.