Before you move budget, know which campaigns kept the revenue.

DriveMetaData turns ad-platform claims, orders, cancellations, returns, WhatsApp assists, CRM outcomes, and finance rules into one retained-revenue decision view.

Get a Free ROAS Reconciliation Audit See Reconciliation

Spend

Where to scale

Sales

What was kept

Data

Your reports

Action

Next move

Retained Revenue Console

Illustrative May audit

Platform Claim

5.68x

ad-network view

Order-Book ROAS

3.92x

-31% after orders

Refund-Window ROAS

2.74x

-52% after leakage

Budget-Ready ROAS

2.31x

finance-aligned

Campaign Rank (After Leakage)

Google Ads

2.97x

Meta Ads

2.31x

Paid Search

1.94x

3.42x

4.13x

Organic

1.73x

Affiliate

2.08x

Revenue Reconciliation

₹1.82 Cr

Retained

Recognized Revenue65%

Cancelled Orders18%

Returns & Refunds10%

Discounts5%

Others2%

Canceled Demand

-18.6L

orders that never became revenue

Return Drag

-26.3L

late leakage after spend moved

Discount Leakage

-7.2L

promo impact before margin review

Defensible Revenue

1.82 Cr

retained revenue for budget calls

Trusted by growth teams that cannot afford inflated ROAS.

D2C, retail, mobility, and financial-services teams use revenue-truth workflows to defend spend before the next budget move.

Customer proof

When did the ad dashboard stop matching sales?

Before you scale a campaign, see the first day the platform story split from store revenue and DMD-attributed revenue.

Daily Ad Claim Drift

Seven-day budget check: store revenue, DMD attribution, and ad platform value.

Audit this gap

Store revenue

DMD attributed revenue

Ad platform value

First red flag

Sep 02

The ad platform reported more value than the store actually kept.

What changed

2-day jump

Claimed revenue kept rising while sales stayed flat. Check windows, duplicate credit, and late returns.

Budget call

Pause scaling

Do not add spend to the claimed winner until the source report is reconciled.

Claim becomes budget action.

5.68x

Claim

2.31x

Retained

Act

Budget

Inputs

Metaad claims

Google Adsspend + ROAS

Shopifyorders + returns

WhatsAppassists

HubSpot CRMcustomer status

2. Match, remove, credit

Reconciliation layer

Match ordersRemove leaksCredit assists

Outputs

Clean ROASreal retained return

Leakage reasonswhy ROAS changed

Budget movesscale / hold / recover

Finance memoboard-ready proof

OrdersMatched

ReturnsRemoved

AssistsLinked

PolicyApproved

3. Outputs for budget calls

Leave with a clean ROAS number, the reason it changed, and what to do next.

Retained ROAS

2.31x

ClaimRetained

Increase budget

Pause and review

Recover lost revenue

Stop wasteful spend

Example calculation

From claimed ROAS to a finance-ready budget call.

This illustrative reconciliation calculation shows the full audit shape: problem, connected data, finding, action, result, and the next step for teams that need to defend spend.

Platform claim

5.68x

ad dashboard

Retained ROAS

2.31x

finance-ready

Revenue kept

1.82 Cr

after leakage

1. Problem

Platform ROAS looked safe while fulfilled revenue flattened.

The budget team was about to scale a paid campaign because the ad dashboard claimed 5.68x ROAS, but matched order revenue showed only 3.92x after fulfilled orders were checked.

2. Connected data

Spend, orders, returns, WhatsApp assists, CRM status, and finance policy were joined.

DriveMetaData connected ad claims, order status, return windows, WhatsApp recovery, CRM outcomes, repeat-purchase signals, and finance-approved revenue definitions before the budget review.

3. Finding

The retained number fell to 2.31x after leakage.

Canceled demand, late returns, duplicate credit risk, discount leakage, and assist credit changed which campaigns deserved more budget and which needed review.

4. Action

The budget memo separated scale, hold, recover, and suppress moves.

Growth kept spend behind cohorts with retained revenue, reviewed refund-heavy campaigns, and gave lifecycle teams recovery audiences before the next allocation.

5. Result

Finance, growth, lifecycle, analytics, and ecommerce reviewed one number.

The meeting moved from debating dashboards to reading the same retained ROAS view, leakage reason map, and action board.

Not ready to request the audit?

Use the revenue mismatch checker to estimate where ad claims and retained revenue may be drifting before the walkthrough.

Run Revenue Mismatch Checker

Get the ROAS gap reviewed before you rebuild the workflow.

Send the minimum context. We will map the likely claim, leakage, and source issues before your next budget move.

No production access required

Start from current reports

First reply focuses the audit

Stop scaling campaigns on ROAS you cannot prove.

Turn platform claims into a clear spend call: which campaigns to scale, pause, recover, or cut before budget is wasted.

Find where platform ROAS stops matching sales.

Show the first place ad-reported revenue separates from fulfilled orders, paid revenue, refunds, and customer status.

Gap finder

Show the revenue you can safely call won.

Separate claimed conversions from paid, delivered, non-refunded orders so teams know which campaign money is actually in the bank.

Revenue proof ledger

Spot the leaks hiding inside winning campaigns.

Expose the cancellations, returns, discounts, duplicate claims, and assists that make a campaign look stronger than it is.

Leakage reason map

Turn ROAS truth into tomorrow's spend move.

Give each campaign a clear next action: scale winners, review weak cohorts, recover demand, or cut waste.

Spend move board

Send the same action plan to every team.

Performance, lifecycle, analytics, and finance work from the same retained revenue truth instead of debating different dashboards.

Team action handoff

Find where platform ROAS stops matching sales.

Gap finder

Show the first place ad-reported revenue separates from fulfilled orders, paid revenue, refunds, and customer status.

Platform claim

5.68x

ad dashboard

Store reality

3.92x

orders kept

Verified gap

-31%

Gap exposed
before scale

Sep 02 spike

claim up, sales flat

Flag drift

Meta + Google

duplicate credit risk

Check source

Claimed winner

proof pending

Hold scale

Budget review

before spend moves

Audit now

Campaign Spend Action Board

Ranked moves from claimed ROAS, verified revenue, and the operational reason behind the gap.

Board-ready view

CampaignSignalImpactMove

Sep 02 spike

claim up, sales flat

Flag drift

Meta + Google

duplicate credit risk

Check source

Claimed winner

proof pending

Hold scale

Budget review

before spend moves

Audit now

Board-ready ROAS proof, not another spreadsheet.

Start with what ad platforms claimed, remove the revenue the business did not keep, and leave teams with one number they can defend in a budget meeting.

Get the memo

Claimed by ads

2.45Cr

Starting point

Revenue kept

1.82Cr

Finance-ready

ROAS to report

2.31x

After leakage

What changed the number

The reasons finance will ask for before approving the next spend move.

-25.5%

Canceled orders-18.6L

7.6% of claim

Returns & refunds-26.3L

10.7% of claim

Discount leakage-7.2L

2.9% of claim

Proof layer

Amount (INR)

% of claim

ROAS effect

Ad Platform Claim

Amount2,45,00,000

% Claim100%

Effect5.68x

Matched Order Revenue

Amount1,98,60,000

% Claim81.1%

Effect3.92x

Canceled Orders

Amount-18,60,000

% Claim-7.6%

Effect-0.82x

Returns & Refunds

Amount-26,30,000

% Claim-10.7%

Effect-1.16x

Discounts & Adjustments

Amount-7,20,000

% Claim-2.9%

Effect-0.31x

Net Revenue (Finance-Ready)

Amount1,82,50,000

% Claim74.5%

Effect2.31x

One truth, five teams, zero debate.

The same reconciled ROAS number becomes the right next move for every owner in the room.

2.31x

ROAS

Teams

Memo

Shared source

2.31x

Retained ROAS

Claim5.68x

Kept revenue1.82Cr

DecisionDefend spend

CMO / VP Growth

Budget story

Campaign rank

Performance Marketers

Spend move

Scale / hold

Ecommerce Operators

Leakage reason

SKU + refund drag

Analytics / Data Teams

Definition log

Rules + joins

Finance Teams

Revenue review

2.31x defended

Connect the stack. Govern the number.

Model revenue once, then let every team read the same retained ROAS and budget action views.

No migrationVisible rulesFinance-ready

Source cubes

Ad Spend

Orders

Returns

CRM

Finance

Semantic layer

Revenue Truth Model

Identity match

Order match

Refund window

Revenue policy

Attribution rules

Deduplication

Claim -> adjustment -> retained revenue

Decision views

Retained ROAS View

2.31x

net revenue

Budget Action View

Scale

hold / recover

API

Audit

FAQ

ROAS reconciliation questions teams ask before budget review.

Clear answers for growth, finance, analytics, ecommerce, and lifecycle teams deciding whether platform ROAS is safe to use.

What is ROAS reconciliation?

ROAS reconciliation compares platform-reported revenue with business revenue after orders, cancellations, returns, refunds, WhatsApp assists, CRM outcomes, and finance definitions are matched.

How do you calculate retained ROAS?

Retained ROAS is calculated by dividing finance-approved retained revenue by the ad spend tied to that revenue. The retained revenue side removes canceled orders, returned orders, refunds, duplicate claims, and revenue that does not meet finance rules.

What data is needed for ROAS reconciliation?

A useful audit needs ad spend and conversion exports, order data, cancellations, returns, refunds, payment or COD status, CRM lifecycle status, WhatsApp touchpoints, customer identifiers, campaign identifiers, and finance revenue definitions for the period being reviewed.

Why do Meta, Google Ads, Shopify, CRM, and finance reports disagree?

They disagree because each system uses different attribution windows, timestamps, identifiers, deduplication rules, order states, refund timing, currency or tax treatment, and revenue definitions. ROAS reconciliation aligns those rules before budget decisions are made.

How long does a ROAS reconciliation audit take?

Most teams can complete an initial ROAS reconciliation audit in a few business days once source access or exports are available. Timing depends on the number of ad accounts, stores, CRM sources, refund windows, and finance rules that need to be matched.

Is this different from attribution reporting?

Yes. Attribution reporting explains which touchpoints deserve credit for a conversion. ROAS reconciliation checks whether the credited revenue was actually retained after order status, cancellations, refunds, assists, CRM outcomes, and finance rules are applied.

Should platform ROAS be ignored?

No. Platform ROAS is useful for in-platform optimization. It should not be treated as final budget truth until cancellations, returns, retained revenue, channel contribution, and finance definitions are reconciled.

How is WhatsApp contribution measured?

WhatsApp contribution is measured by matching WhatsApp touches to recovery, order confirmation, COD verification, support, repeat purchase, reactivation, cancellation prevention, and retained revenue.

Bring the real ROAS number to your next budget meeting.

Request a free ROAS Reconciliation Audit and get the claim, adjustment, source, and next move your team can review together.

No migration

Start from existing reports

No black box

Every adjustment has a reason

Decision output

Scale, hold, recover, or suppress

Request your reconciliation audit.

Use the audit form above to share your stack, challenge, spend range, and website. We will map the revenue gap your team needs to defend.

Platform claim versus retained revenue

Leakage reasons finance will ask about

Recommended scale, hold, recover, or suppress move

Request the reconciliation audit