Skip to content

Connect campaigns to qualified leads, sales and revenue.

Ad platform, analytics and CRM records are reconciled, so reporting follows each campaign beyond form fills to qualified leads, sales and revenue, as far as your CRM and business data record them, and states where attribution stays uncertain.

Problems it solves

Why do your tools report different answers?

Each platform measures with its own rules and its own incentives. Without a layer that reconciles them against CRM outcomes, reporting turns into an argument about whose number is right.

  • Platforms disagree

    Meta, Google Ads, GA4 and the CRM report different conversions for the same period.

  • Reporting disconnected from revenue

    Dashboards count leads, not qualified leads, sales or revenue.

  • KPIs without definitions

    The same metric name means different things to different teams.

  • Manual, late reporting

    Numbers arrive after the decision they were meant to inform.

Measurement connects marketing activity to business outcomes. It starts by deciding which system owns each number, then explains why the systems report different totals.

Which system owns which number

Metric hierarchy
  1. Media

    Impressions · Clicks · Spend

    System of record
    Ad platforms
  2. Acquisition

    Sessions · Leads

    System of record
    Analytics (GA4)
  3. CRM

    MQL · SQL · Opportunities

    System of record
    CRM
  4. Business

    Customers · Revenue · Margin · Lifetime value

    System of record
    CRM and finance

    The level budget decisions are judged against.

Why the totals disagree

Ad platforms, analytics and the CRM count different things at different moments. Reconciliation documents each difference, so the gap between them is explained rather than argued about.

Where the counts differ
SystemCountsWhenWhy the total differs
Meta AdsLeads attributed to adsWithin its click and view windowsCredits view-through conversions and models conversions it cannot observe.
Google AdsConversions attributed to adsOn the date of the clickReports by click date, so late conversions move between reporting periods.
GA4Lead eventsIn the session of the submissionMisses visitors who declined analytics consent and applies its own attribution model.
CRMLeads and deals receivedWhen the record is createdKeeps one record per person, with qualification and revenue attached.

Reporting architecture

Reports read from one prepared layer instead of from each tool separately, so every dashboard uses the same definitions.

Reporting architecture
  1. Sources

    Ad platforms · GA4 · CRM

  2. Scheduled extraction

    APIs on a fixed schedule, with completeness checks.

  3. Database or warehouse

  4. Measurement layer

    Definitions, joins and reconciliation rules, written once.

  5. Reports and decisions (key stage)

Decision use and limits

Reconciled records help choose metrics for a decision and explain differences between reported performance and commercial outcomes. Attribution describes credited activity; it does not by itself establish incremental impact or prescribe a budget move.

Deliverables

  • Measurement architecture

    Which metrics exist, where they come from and which decisions they serve.

  • Cross-platform reconciliation

    A documented explanation of why platforms, analytics and CRM differ.

  • CRM revenue connection

    Qualified leads, pipeline and revenue joined to acquisition data.

  • Dashboards

    Looker Studio or Power BI reporting built on reconciled data.

  • Analysis

    SQL or Python analysis of funnels, cohorts and customer value where data permits.

Process

  1. Map decisions

    Start from the decisions reporting must support.

  2. Define metrics

    Write definitions, sources and owners for each metric.

  3. Reconcile

    Join platform, analytics and CRM data and explain the gaps.

  4. Report

    Build dashboards and automate the refresh.

Tools and systems

  • GA4
  • Looker Studio
  • Power BI
  • SQL
  • Python
  • PostgreSQL
  • CRM platforms

Questions

Which number is the right one?

Usually none of them on its own. Each tool answers a slightly different question. The measurement layer documents what each number means and which one to use for each decision.

Do we need a data warehouse?

Not always. Smaller setups can reconcile data in a lighter way. A warehouse becomes useful when several sources, markets or long histories need to be joined reliably.

Can you work with our existing dashboards?

Yes. Existing reporting is reviewed first; it is rebuilt only where the underlying data or definitions cannot support it.

Related research

Discuss your measurement setup