Abrasim tracking and analytics guide
Every Marketing Channel Claims the Same Conversion
Reconcile conversions claimed by more than one channel.
By Tafadzwa BoriwondoPublished Evidence reviewed
- For
- CMO, CFO or Performance Marketing Lead
- Decision to make
- Separate platform attribution, deduplicated outcomes, contribution evidence and finance records before reallocating budget.
- Scope boundary
- This reconciliation or contribution question. Observational attribution cannot establish causation.
What the problem looks like and why it affects the business
When advertising platforms, analytics reports and partner dashboards each claim the same enquiry or sale, adding their conversion totals creates a larger number than the organisation actually received.
Bottom line: Duplicate credit can make total acquisition performance look stronger than finance or CRM outcomes, leading leaders to fund channels on incompatible claims rather than a reconciled commercial population.
Use this guide to reconcile conversions claimed by more than one channel. It is written for CMOs, CFOs or performance-marketing leads. Confirm budget approval with the CMO and CFO jointly. Scope: This reconciliation or contribution question. Observational attribution cannot establish causation. 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 separate platform attribution, deduplicated outcomes, contribution evidence and finance records before reallocating budget.
What to expect in the working pack
The Cross-Channel Conversion Reconciliation Workbook contains six XLSX sheets to complete as you follow the method:
- Decision charter records the decision about “every marketing channel claims the same conversion”, 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 separate platform attribution, deduplicated outcomes, contribution evidence and finance records before reallocating budget. 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 reconcile conversions claimed by more than one channel, compare relevant operational, customer, CRM, finance and platform evidence using authorised sources.
| Evidence | What it distinguishes | Minimum record |
|---|---|---|
| Outcome ledger | How many accepted outcomes actually exist | Stable outcome ID, type, time, status, value, reversal and authoritative system |
| Platform credit export | How each platform assigns credit | Platform, conversion action, model, window, interaction, value and export time |
| Analytics journey evidence | Which measured touchpoints preceded the outcome | Permitted journey ID, source, medium, campaign, time, key event and identity limit |
| Deduplication map | Which reported records refer to the same outcome | Outcome ID, platform record, analytics record, match basis, confidence and exception |
| Commercial reconciliation | Whether credited outcomes matured into accepted value | Lead disposition, order state, recognised value, refund, cost boundary and finance owner |
To reconcile conversions claimed by more than one channel, 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 reconcile conversions claimed by more than one channel. Agree any changes with the accountable owners. These are working definitions, not universal benchmarks.
| Measure | Working definition | Eligible population | Period | Source | Exclusions |
|---|---|---|---|---|---|
| Platform credit to unique outcome ratio | Total platform-credited conversions divided by unique accepted outcomes in the authoritative ledger | Comparable credited records and accepted outcomes | Mature reconciled cohort | Platform exports and outcome ledger | Non-comparable conversion actions shown separately |
| Outcome match coverage | Unique accepted outcomes matched to at least one permitted platform or analytics record divided by unique accepted outcomes | Unique accepted outcomes | Mature reconciled cohort | Deduplication map | Outcomes intentionally outside measured channels |
| Unresolved value variance | Absolute unexplained difference between platform value and accepted commercial value | Matched outcomes with value | Mature reconciled cohort | Platform exports, CRM and finance records | Approved tax, currency and timing differences |
For “every marketing channel claims the same conversion”, 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: Separate platform attribution, deduplicated outcomes, contribution evidence and finance records before reallocating budget. 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 “every marketing channel claims the same conversion” 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: Separate platform attribution, deduplicated outcomes, contribution evidence and finance records before reallocating budget.
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 a comparable reporting cohort and export each platform's conversion definition, attribution model, lookback window, counting method and time basis before totals change.
Use in the working pack: Decision charter and QA and reconciliation.
Required output: A dated current-state record of “every marketing channel claims the same conversion” 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
Define one authoritative outcome population with stable IDs and separate submitted, accepted, qualified, won, recognised and reversed stages rather than calling them all conversions. 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 separate platform attribution, deduplicated outcomes, contribution evidence and finance records before reallocating budget, with distinct definitions for unlike measures.
Decision gate: Reproduce each measure from authorised evidence. A platform display cannot, by itself, support the decision to separate platform attribution, deduplicated outcomes, contribution evidence and finance records before reallocating budget.
Step 4: Trace source, collection and transformation
Build a crosswalk from each platform and analytics record to the outcome ledger, retaining one-to-many credit as platform evidence while deduplicating the commercial outcome population. 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 “every marketing channel claims the same conversion” that exposes broken, duplicated, delayed, transformed or non-comparable evidence.
Decision gate: Pause work on every marketing channel claims the same conversion wherever the source records and transformations cannot explain the reported value.
Step 5: Test contradictions and negative cases
Test exact matches, duplicated claims, unmatched platform credit, unattributed outcomes, late adjustments and value disagreements; investigate samples rather than forcing every record to match. 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 “every marketing channel claims the same conversion” with source evidence, destination evidence, discrepancies, disposition and retest ownership.
Decision gate: Include failed and exception cases when investigating every marketing channel claims the same conversion. 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. Publish separate platform-credit, deduplicated-outcome and commercial-value views, then change budget only through an approved decision rule that states confidence and causal limits.
Use in the working pack: Issues and actions.
Required output: Prioritised actions for “every marketing channel claims the same conversion”, with definition, collection, source, operating and decision-use changes recorded separately.
Decision gate: The owner must accept the corrected evidence for its intended use: Reconcile conversions claimed by more than one channel. Confirm its limits before release; technical completion alone is insufficient.
Step 7: Record the decision and later learning
Record the decision about “every marketing channel claims the same conversion”, 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: Every reported layer states whether it represents assigned credit, unique outcomes or accepted commercial value; duplicates and unmatched populations are visible; material differences have owned dispositions; and budget decisions do not add incompatible platform totals.
Decision gate: A changed report does not resolve “every marketing channel claims the same conversion”. 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, CFO or Performance Marketing 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
Three platforms report 146 conversions in total, but the CRM contains 83 unique accepted enquiries for the cohort. The team maps 71 enquiries to one or more platform claims, keeps multi-platform credit visible, excludes rejected duplicates from the commercial denominator and presents 83 accepted outcomes rather than 146 customers.
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 separate platform attribution, deduplicated outcomes, contribution evidence and finance records before reallocating budget, 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 “every marketing channel claims the same conversion” 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: Every reported layer states whether it represents assigned credit, unique outcomes or accepted commercial value; duplicates and unmatched populations are visible; material differences have owned dispositions; and budget decisions do not add incompatible platform totals.
Use at least one negative case. A row appearing in three platform reports is not three customers, while forcing all three claims into a single winning channel discards useful journey evidence.
Record failed tests for “every marketing channel claims the same conversion” 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 attribution models, windows and counting settings with every recurring report.
- Require stable outcome IDs and stage definitions in channel-to-commercial reporting.
- Reconcile credited totals to a mature authoritative cohort before budget reviews.
- 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 Analytics Help : Get started with attribution : Official guidance defining attribution as assigned credit and describing the available attribution models, path evidence and model behaviour.
- Google Analytics Help : Select attribution settings : Official guidance on reporting attribution models, eligible channels, lookback windows and prospective effects of configuration changes.
- 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 “every marketing channel claims the same conversion”; 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, Audit attribution and decision evidence. 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: “Every Marketing Channel Claims the Same Conversion”.
Situation: every marketing channel claims the same conversion
Decision to make: Separate platform attribution, deduplicated outcomes, contribution evidence and finance records before reallocating budget.
Scope boundary: This reconciliation or contribution question. Observational attribution cannot establish causation.
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.
