Data Foundation Audit

When the platforms disagree, your decisions break first.

An audit of how your data is collected and reported, from the tag to the dashboard, scoped to your stack. We document what is running, where the gaps are, and what to do about each one, then hand you the documentation that holds.

  • Tailored to your stack
  • Typically three weeks
  • Read-only access
Learn more

Most teams don't find out their tracking is broken until a quarterly review stops adding up.

  • Google Ads reports more conversions than the CRM can account for.
  • Meta tells one story, GA4 tells another.
  • A plugin update quietly broke the lead-form success event months ago.
  • Consent, the data layer, the conversion APIs: any one can be subtly wrong, and the errors compound.
  • The monthly report takes days to assemble, and nobody quite trusts the total.

We come in once, audit the whole stack, and leave you with documentation that holds.

The diagnostic

What a marketing measurement audit covers.

By default we read the whole chain, from the tag to the dashboard. If only one half is in question, the collection or the reporting, we scope the audit to that half.

Collection
01 · Container

GTM installed the way Google prescribes.

We check the container is installed via the official method or an approved plugin, and flag Google tags hard-coded into the theme that should sit in GTM. The container should be the single source of truth for tagging.

02 · Consent

Consent that does what the banner promises.

We map the CMP, verify Consent Mode v2 is wired correctly, and check every tag respects the consent signal. Most failures are not about whether a banner exists, but that tags ignore it.

03 · Platforms

GA4 and the ad platforms you actually advertise on.

We audit the platforms that matter to the business, scoped to what is in use, and still flag legacy tags left in containers after a platform sunset.

Reporting
04 · Pipelines and joins

What gets joined, what doesn't, and why.

We follow the data out of the platforms: the connectors, the warehouse, the CRM join. We document what is actually stitched together, what is quietly dropped on the way, and where a report is built on a partial table.

05 · Definitions

A metric that means the same thing on every row.

Google counts interactions, Meta counts clicks, the CRM counts deals. We check whether your reporting reconciles those definitions before the data lands, or adds them up and calls it a total. What cannot be compared should be named as such, not averaged.

06 · Current governance

The documentation your team already relies on.

We review your existing tracking plan, data dictionaries, and naming conventions, and show exactly where the internal documentation drifted from what the code actually fires. The Blueprint you receive starts from that gap.

The deliverables

What you receive.

A findings deck.

Severity-ranked, one finding per slide. Each finding named, evidenced with a screenshot, and paired with a recommendation and an effort estimate. Concise on purpose, so it gets read.

The Blueprint.

The single source of truth for how your data is defined. Depending on the scope, that is your tracking plan, your data dictionary, your naming conventions, or all of them: one row per conversion and per metric, one consistent name across every platform, a verification status next to each. Structured to be handed to your team or your next agency.

Both deliverables stay yours.

Whether we continue together afterwards or not, the deck and the Blueprint are yours to keep.

The process

How it works.

012 min

Your request.

The short form on this page: what you are seeing, and your site.

021 working day

A price range.

We read your stack from the outside, then send you a range. Fifteen minutes on a call if you would rather talk it through.

03Before we start

Fixed price, then access.

You confirm the platforms, the markets and the tools. We fix the price on that, and only then ask for read-only access.

043 weeks

The audit.

We document as we go and clarify in writing rather than tying up your team. It ends with a sixty-minute handover of the findings, the plan, and the order we would fix things in.

What clients say
“They were proactive, transparent with the numbers, and always came with smart ideas to test and improve performance.”
Bjarne SorensenDigital Marketing Manager · Centre Patronal
Before you ask

The questions we get first.

Do you need admin access to our accounts?

No. We work read-only. You grant view access to the platforms in scope, and we document from there. Nothing in your accounts changes during the audit.

What if we don't continue with you afterwards?

The findings deck and the Blueprint are yours to keep either way. Plenty of teams take them straight to their in-house team or their existing agency. There is no lock-in.

Our tracking is solid. Can we take just the reporting half?

Yes. The audit reads the chain from tag to dashboard, but the two halves scope separately. If collection is already clean we say so quickly and the time goes to the pipelines, the definitions and the reporting. The reverse works too: some teams only need the collection layer read.

What does it cost?

Pricing scales with the number of platforms we audit and the market you are in. You get a range within one working day of your request, and a fixed price once the platforms, markets and tools are confirmed. No sales call required to find out. What is fixed either way is what you get: a severity-ranked findings deck and the Blueprint, yours whether we continue or not.

Who actually does the work?

The senior engineer who runs your audit is the person who answers your request, not a sales rep who hands you off. The same person walks you through the findings at the end.

How long until we see something?

Typically three weeks from kickoff to the handover call, a little more for a large multi-platform stack. We document as we go and clarify in writing rather than tying up your team with status meetings.

Find my tracking gaps