Abrasim tracking and analytics guide
Agency and Internal Analytics Reports Use Different Evidence Rules
Agree evidence and acceptance rules across agency and internal teams.
By Tafadzwa BoriwondoPublished Evidence reviewed
- For
- CMO, Procurement or Analytics Lead
- Decision to make
- Define access, metric contracts, QA, reconciliation, reporting, change control, knowledge transfer and exit.
- Scope boundary
- Shared evidence and controls, without assuming internal or external delivery is better.
What the problem looks like and why it affects the business
Agency and internal reports can disagree even when both teams are competent because they use different definitions, access, attribution settings, source cutoffs, incentives and acceptance rules.
Bottom line: Unresolved evidence rules create duplicated work, supplier disputes and budget decisions shaped by whichever report is presented most confidently rather than by a shared commercial population.
Use this guide to agree evidence and acceptance rules across agency and internal teams. It is written for CMOs, procurement teams or analytics leads. Confirm budget approval with the CMO or procurement owner accountable for the delivery model. Scope: Shared evidence and controls, without assuming internal or external delivery is better. Check commercial figures against the authoritative source, keep correlation separate from causation and collect only data that serves the decision.
What you should be able to decide
Use the evidence to decide what to keep, correct, investigate, pause or retire. The task is to define access, metric contracts, QA, reconciliation, reporting, change control, knowledge transfer and exit.
What to expect in the working pack
The Analytics Delivery Governance Workbook contains six XLSX sheets to complete as you follow the method:
- Decision charter records the decision about “agency and internal analytics reports use different evidence rules”, its authority, economic or service exposure, scope and evidence threshold.
- Metric contracts prevents labels from hiding different populations, periods, exclusions or meanings.
- Collection and lineage traces permitted records and events from source through transformation and destination.
- QA and reconciliation keeps expected results, observed results, discrepancies and evidence classifications separate.
- Issues and actions converts verified problems into owned, reversible work with acceptance gates.
- Decision and learning log preserves the decision, confidence, limitation, review date, observed outcome and reopen trigger.
Open the pack before Step 1. Record the task to define access, metric contracts, QA, reconciliation, reporting, change control, knowledge transfer and exit. Use stable IDs such as DEC-001, MET-001, LIN-001 and TST-001 to connect the decision to its sources and tests. Update the sheets as you work so the audit trail does not depend on memory.
What evidence distinguishes the real cause
One dashboard cannot establish the cause. To agree evidence and acceptance rules across agency and internal teams, compare relevant operational, customer, CRM, finance and platform evidence using authorised sources.
| Evidence | What it distinguishes | Minimum record |
|---|---|---|
| Metric contract comparison | Where meanings differ | Metric, internal definition, agency definition, population, period, exclusions and owner |
| Access matrix | Whether both parties can reproduce evidence | System, role, data scope, publisher rights, restriction, owner and expiry |
| QA and reconciliation rule | What both parties consider accepted | Test, sample, source, tolerance, discrepancy, evidence class and approver |
| Change and release history | Who changed measurement and when | Change ID, version, reviewer, publisher, production date, rollback and effect |
| Commercial governance | How incentives and exit affect evidence | Deliverable, acceptance, dependency, knowledge asset, transfer duty and exit state |
To agree evidence and acceptance rules across agency and internal teams, label each material item VERIFIED, INFERRED, PROPOSED or REQUIRES VALIDATION. A verified item has an authoritative source or reproducible test; it does not make the conclusion universally true. Explain inferences and alternative causes. Keep proposed controls separate from existing ones, and mark missing authority, access or evidence as requiring validation.
Establish the metric contracts before interpreting movement
Use the definitions below in Metric contracts to agree evidence and acceptance rules across agency and internal teams. Agree any changes with the accountable owners. These are working definitions, not universal benchmarks.
| Measure | Working definition | Eligible population | Period | Source | Exclusions |
|---|---|---|---|---|---|
| Shared metric-contract coverage | Material reported metrics with one accepted cross-party contract divided by material reported metrics | Material reported metrics | Governance review | Shared metric register | Exploratory metrics labelled separately |
| Reproducible report coverage | Material report outputs reproducible by an authorised independent reviewer divided by material report outputs | Material report outputs | Acceptance review | Sources, transformations and report evidence | Restricted evidence with approved alternate assurance |
| Knowledge-transfer acceptance | Required operating assets accepted by the accountable owner divided by required operating assets | Required operating assets | Delivery or exit gate | Handover and acceptance register | Supplier-owned intellectual property recorded as a dependency |
For “agency and internal analytics reports use different evidence rules”, capture data freshness, sampling, thresholding, cardinality, missing values and late-arriving outcomes wherever they could change the decision. A platform can correctly process the data it received while the organisation still has the wrong definition, an incomplete population or an unsafe conclusion.
How to fix it step by step
Step 1: Charter the decision and the exposure
Write the exact decision before discussing a dashboard, event or metric: Define access, metric contracts, QA, reconciliation, reporting, change control, knowledge transfer and exit. Name the accountable authority, the economic or customer exposure, the scope boundary and the latest useful decision date.
Use in the working pack: Decision charter.
Required output: A charter for “agency and internal analytics reports use different evidence rules” with a stable Charter ID, named authority, scope, evidence threshold and a condition for stopping or escalating.
Decision gate: Agree who can authorise this task before continuing: Define access, metric contracts, QA, reconciliation, reporting, change control, knowledge transfer and exit.
Step 2: Preserve the current evidence before changing it
Capture the reports, source records, definitions, dates, filters, exclusions, versions and meeting or workflow evidence that currently produce the symptom. Freeze representative internal and agency outputs with definitions, dates, filters, models, sources and known incentives before asking either party to make their numbers agree.
Use in the working pack: Decision charter and QA and reconciliation.
Required output: A dated current-state record of “agency and internal analytics reports use different evidence rules” that another reviewer can reproduce without relying on screenshots alone.
Decision gate: For this investigation, treat missing source access, unexplained transformations or changed historical reports as visible limitations, not permission to infer the missing evidence.
Step 3: Define the measures and their boundaries
Create shared metric contracts, role-based access and evidence classifications, protecting independence of review while removing avoidable information asymmetry. For each retained measure, write the name, definition, eligible population, period, dimensions, source of truth, exclusions, owner and version.
Use in the working pack: Metric contracts.
Required output: Metric contracts for the decision to define access, metric contracts, QA, reconciliation, reporting, change control, knowledge transfer and exit, with distinct definitions for unlike measures.
Decision gate: Reproduce each measure from authorised evidence. A platform display cannot, by itself, support the decision to define access, metric contracts, QA, reconciliation, reporting, change control, knowledge transfer and exit.
Step 4: Trace source, collection and transformation
Define source ownership, transformation lineage, QA samples, reconciliation tolerances, change review, publishing authority and rollback across internal and supplier boundaries. Link the originating record or permitted event through every material transformation and destination. Record consent or lawful-use state when personal information or identifiers are present.
Use in the working pack: Collection and lineage.
Required output: A source-to-decision lineage for “agency and internal analytics reports use different evidence rules” that exposes broken, duplicated, delayed, transformed or non-comparable evidence.
Decision gate: Pause work on agency and internal analytics reports use different evidence rules wherever the source records and transformations cannot explain the reported value.
Step 5: Test contradictions and negative cases
Run joint tests on normal, exception, delayed, duplicate and disputed records; require each party to explain contrary evidence and preserve unresolved differences visibly. Use a bounded sample that includes normal records, exceptions, missing values, delayed outcomes, duplicates and a case expected to fail. Record expected and observed evidence separately.
Use in the working pack: QA and reconciliation.
Required output: Reproducible tests for “agency and internal analytics reports use different evidence rules” with source evidence, destination evidence, discrepancies, disposition and retest ownership.
Decision gate: Include failed and exception cases when investigating agency and internal analytics reports use different evidence rules. Evidence that passes only the easiest route or hides important contradictions is insufficient.
Step 6: Choose, own and release the correction
Turn each verified gap into an action with severity, affected decision, evidence reference, owner, dependency, rollback trigger and acceptance gate. Adopt shared acceptance, service, knowledge-transfer and exit controls without pre-deciding internal or external delivery, then review performance on evidence quality and decision support rather than report volume.
Use in the working pack: Issues and actions.
Required output: Prioritised actions for “agency and internal analytics reports use different evidence rules”, with definition, collection, source, operating and decision-use changes recorded separately.
Decision gate: The owner must accept the corrected evidence for its intended use: Agree evidence and acceptance rules across agency and internal teams. Confirm its limits before release; technical completion alone is insufficient.
Step 7: Record the decision and later learning
Record the decision about “agency and internal analytics reports use different evidence rules”, who made it, which evidence was used, the confidence and every known limitation. Assign the action and schedule a review after enough time has passed for the relevant outcome or guardrail to be observed.
Use in the working pack: Decision and learning log.
Required output: A recorded decision that can be checked against this acceptance condition: Material metrics have shared contracts, access supports reproducible independent challenge, QA and change controls are agreed, unresolved evidence remains visible, delivery assets pass knowledge-transfer gates and the operating model decision is based on capability and accountability rather than preference.
Decision gate: A changed report does not resolve “agency and internal analytics reports use different evidence rules”. Close the work when the owner accepts the evidence for the decision and schedules a later outcome review.
Who must be involved
| Responsibility | Minimum role |
|---|---|
| Accountable decision | CMO, Procurement or Analytics Lead with authority for the affected decision |
| Metric meaning | Business or functional owner who can accept the definition and exclusions |
| Source and transformation | Authorised system, analytics or data owner who can reproduce the lineage |
| Commercial or service reconciliation | Finance, CRM, sales, service or operational owner appropriate to the claimed outcome |
| Privacy and control | Information Officer, privacy, security or legal authority when personal information, protected groups or material control consequences are in scope |
| Independent challenge | A person sufficiently independent of the original design or performance incentive to test contrary evidence |
The six value paths cross functional budgets, evidence and ownership; diagnosis therefore needs cross-functional authority, access and independent challenge, whether led internally or externally. A capable internal team can lead when it has the required authority, source access, domain competence and ability to challenge the original assumptions. Escalate or use qualified external support where material evidence is contested, privacy or legal judgement is required, system access is fragmented, or the same incentives that produced the measure could suppress contrary findings.
Worked example
An agency reports 420 leads while the internal CRM reports 270. Joint reconciliation shows the agency counts repeated submissions and the internal report excludes delayed imports. The teams agree a mature accepted-lead contract, retain both operational exception counts and change supplier acceptance to the shared definition.
This is a hypothetical method example, not an Abrasim client result, benchmark or performance promise.
How to verify the data can support the decision
To check whether the correction supports the task to define access, metric contracts, QA, reconciliation, reporting, change control, knowledge transfer and exit, test collection, definitions, reconciliation, decision use and later outcomes separately. A firing tag, populated report or better-looking dashboard is insufficient:
- Collection gate: the permitted event or record needed for “agency and internal analytics reports use different evidence rules” is observed with the expected fields and consent or lawful-use state.
- Definition gate: the metric can be reproduced from its contract, population, period, exclusions and version.
- Reconciliation gate: representative normal and exception records agree with the authoritative source within an approved, explained tolerance.
- Decision gate: the accountable owner can interpret the measure, its confidence and its limits and can choose an authorised action.
- Outcome gate: after the relevant lag, the action and later customer, operational, commercial or risk evidence are reviewed separately.
Accept the work only when: Material metrics have shared contracts, access supports reproducible independent challenge, QA and change controls are agreed, unresolved evidence remains visible, delivery assets pass knowledge-transfer gates and the operating model decision is based on capability and accountability rather than preference.
Use at least one negative case. Giving every participant publishing access does not create transparency, and choosing the internal number by default is not independent reconciliation.
Record failed tests for “agency and internal analytics reports use different evidence rules” rather than deleting or overwriting them. Reopen the decision when the definition, source, transformation, ownership, material market condition or observed relationship changes. Roll back a release that duplicates outcomes, hides an unknown population, breaks a control, exposes personal information or removes an evidence path needed for this decision.
How to keep the problem from returning
- Version shared metric, QA and reporting contracts with both parties.
- Review access, publishing rights and supplier dependencies quarterly.
- Exercise knowledge transfer and exit before a contract or key-person transition becomes urgent.
- Review metric contracts, lineage and decision use at the recorded review-by date and after material system or operating changes.
- Retain source evidence and version history long enough for the authorised review while following approved access, retention and deletion controls.
- Keep implementation acceptance, operating adoption and later business movement as separate records.
Primary sources and evidence boundary
Primary guidance was reviewed at the 30 August 2026 source cutoff:
- Google Tag Manager Help : Managing users and permissions : Official access-control guidance covering account and container roles, multiple administrators and organisation-controlled ownership.
- Google Tag Manager Help : Publishing, versions and approvals : Official guidance on workspace review, version creation, environment publishing, history, approvals and restoring a previous version.
- Google Analytics Help : Add, edit and delete Analytics users and user groups : Official access-management guidance for account and property levels, user groups, roles and removal.
- US Government Accountability Office : Assessing Data Reliability : Primary government audit material covering planning, source review, testing, control consideration and explicit reliability determinations.
The sources above establish controls relevant to “agency and internal analytics reports use different evidence rules”; they do not prove Abrasim client outcomes or the cause of a specific organisation's performance. POPIA, privacy, employment, financial and sector-specific decisions remain with qualified authorised owners.
Where definitions, sources, ownership or commercial consequences remain contested, Assess the capability and governance model. You can use this guide internally. Seek support when the decision needs cross-team access, independent challenge or assurance over a high-risk change.
Use the method with AI
A prompt to help you work through this guide
Use this prompt to organise your analysis. Share only evidence you are authorised to provide to that model. A person must remain responsible for the decision, privacy limits and final action.
Copy and adapt
You are helping me apply the Abrasim tracking and analytics guide: “Agency and Internal Analytics Reports Use Different Evidence Rules”.
Situation: agency and internal analytics reports use different evidence rules
Decision to make: Define access, metric contracts, QA, reconciliation, reporting, change control, knowledge transfer and exit.
Scope boundary: Shared evidence and controls, without assuming internal or external delivery is better.
Use only the evidence I provide. Do not invent facts, benchmarks, sources, outcomes, customer research or legal conclusions. Keep VERIFIED, OBSERVED, INFERRED, PROPOSED and UNKNOWN separate. Ask focused questions when the evidence or authority is missing.
Help me work through this method by returning:
1. An evidence table with claim, source, date, confidence and limitation.
2. The strongest competing explanations, including what would disprove each one.
3. Decision options with trade-offs, dependencies and the cost of waiting where evidence supports it.
4. The next smallest evidence-gathering action, its accountable owner and acceptance test.
5. A proceed, change, validate, defer or stop recommendation that a named human decision-maker can review.
Treat the attached Abrasim working pack as a blank working record. Do not fill missing rows with plausible data. Flag privacy/POPIA, security, accessibility, safety and authority issues. Cite primary sources for external claims and show uncertainty. End with the conditions that would make us change course or stop.
My organisation-specific evidence and constraints:
[Paste evidence, links, dates, decisions and limitations here]Working rule: AI can help organise evidence and expose questions; it cannot establish truth, approve risk, make the business decision or replace qualified legal, privacy, security or accessibility review.