Why Marketing Reports and CRM Revenue Disagree After Switching Agencies

When a new agency’s report disagrees with CRM revenue, the first question should not be “which team is wrong?” Reports may use different source fields, attribution windows, stage definitions, currencies, close dates, or deduplication rules. The Revenue Reconciliation Sheet makes the disagreement observable before the business changes budget or replaces another system.

Salesforce’s Campaign Influence guide describes campaign influence as a configured relationship across records. Google Analytics’ attribution documentation explains that model choice changes credit. A report can be internally consistent and still not answer the same question as CRM revenue.

Freeze the agency handoff

Record final report date under the old agency, first report date under the new one, account and property access, tag changes, source-register changes, dashboard definitions, and CRM migrations. Preserve exports, queries, filters, and calculation notes from both periods.

Do not let the new agency silently redefine history before the baseline is archived.

Define the commercial outcome

Write what “revenue” means: booked contract, invoiced amount, collected cash, recurring value, gross margin, or delivered value. Add currency, timezone, close date, cancellation, refund, and attribution rules. Compare like with like before asking why totals differ.

If the CRM contains multiple revenue fields, name the authoritative one for the decision and list the rest as context.

Compare event and stage definitions

Map report metrics to CRM events: click, session, form, accepted conversation, opportunity, closed-won, and revenue. Record entry and exit rules, owner, timestamp, and exclusions. A marketing-qualified lead in one system may be a raw inquiry in another.

Calculate counts at every join. Unmatched and duplicate records stay visible; they are evidence of a data break, not noise to hide.

Reconcile identity and time

Compare campaign ID, source, medium, contact, account, opportunity, timezone, attribution window, and currency. B2B journeys may include multiple contacts, offline interactions, and long delays. A revenue record can be real without a complete digital trail.

Use a ledger with raw count, matched count, deduplicated count, accepted count, opportunity count, and revenue count. Label each value observed, estimated, or unknown.

Check agency-specific changes

Ask what changed: tags, UTM rules, landing pages, CRM fields, integrations, reporting logic, media mix, creative, budget, or sales handoff. Separate implementation changes from performance changes. A tracking migration can make revenue appear to move even when sales behavior did not.

Review the first few records manually with both agency and internal owners. A small sample often reveals a naming or stage mismatch faster than a dashboard meeting.

Review attribution without false precision

Show first touch, last touch, platform-reported conversion, and configured campaign influence separately. Do not add them together. If the agency reports a percentage of revenue influenced, require model, window, denominator, and exclusions.

An attribution model can distribute credit; it cannot prove that the campaign created the sale. Use the model for a stated decision and keep causal claims modest.

Choose the reconciliation route

| Finding | Route | |—|—| | definition mismatch | agree metric contract | | missing or broken join | repair integration and backfill cautiously | | duplicate or late data | preserve raw counts and correct rule | | real performance change | investigate audience, offer, sales, and capacity | | unknown cause | bounded test and recheck |

Assign one owner for each repair and a sign-off owner for the final metric dictionary.

Protect the next transition

Store account access, source register, dashboard logic, CRM field map, and change log in the owner’s workspace. Do not make a vendor the only holder of the evidence needed to challenge or reproduce its report.

Run a monthly reconciliation while the new process stabilizes, then reduce cadence only after definitions and joins remain stable.

Ask both agencies to sign the metric dictionary for the handoff period. Include report owner, source system, filter, calculation, currency, timezone, attribution model, stage definition, and known exclusions. A signed dictionary does not make a metric true, but it makes disagreement specific and repairable.

Reconcile a small set of known accounts manually. Follow first interaction, campaign membership, contact, opportunity, close date, and revenue field. This sample is not a forecast; it is a diagnostic fixture that reveals whether the automated join is plausible.

If the new agency cannot reproduce the prior report, preserve both outputs and document why. Do not overwrite history with a blended number designed to end the conversation.

Add a stop rule for budget decisions while reconciliation is open. The business may continue essential activity, but a disputed report should not be the sole basis for a major increase, cut, or vendor performance claim.

Capture the disputed decision in writing: which number is being used temporarily, what risk it carries, who accepted that risk, and the date by which reconciliation must be revisited. A temporary operating number is safer when its expiry is visible.

When the definitions are aligned, compare the same account cohort rather than only monthly totals. Note which records entered before the agency switch and matured afterward; that bridge often explains why a report appears to move before CRM revenue does.

Verdicts

Definition break: reports answer different commercial questions.

Data break: events, identities, fields, or integrations do not join.

Attribution difference: credit shifts under different models or windows.

Real performance change: definitions and joins are stable, but commercial results changed.

Insufficient evidence: the handoff archive or source records are missing.

The Revenue Reconciliation Sheet is complete when it freezes the handoff, defines revenue, maps stages, reconciles identities and time, records agency changes, separates attribution, assigns repairs, and protects the next transition. A disagreement is useful when it reveals which decision the business can actually support.