Skip to content

Measurement

CRO & Analytics

Conversion rate optimisation, server-side attribution, CRM-to-ad-platform signal loops and the measurement work that determines whether every other service can actually be optimised against revenue or just against form fills.

  • Defensible blended ROAS that survives CFO scrutiny
  • Server-side tracking that recovers signal lost to browser blocking
  • Closed-loop CRM-to-ad-platform feedback for revenue-aware optimisation

CRO and analytics is the work that determines whether everything else in the marketing stack is being optimised against the truth — closed-won revenue — or against the proxy — form fills. Most marketing problems we diagnose are actually data infrastructure problems. The platforms can only optimise against the signals they receive; if those signals are noisy, incomplete or pointing at the wrong outcome, optimisation produces noisy results.

What this service covers

The standard programme covers:

  • Server-side tracking architecture (GTM Server, Meta CAPI, LinkedIn Conversions API, TikTok Events API) for resilience to browser-side data loss
  • Conversion definition cleanup across CRM, ad platforms and web analytics — what counts as a conversion at each funnel stage, written down and configured consistently
  • Closed-loop CRM signal: offline conversion imports from CRM to ad platforms, lifecycle stage events as intermediate conversions for long-cycle B2B
  • Attribution architecture: single source of truth for spend → conversion → revenue, even when imperfect (better imperfect-and-consistent than perfect-and-uncoordinated)
  • Landing page CRO: hypothesis-led variant testing on key conversion paths, integrated with the paid media optimisation loop
  • Form and funnel CRO: friction analysis, multi-step form optimisation, checkout flow improvement
  • Reporting infrastructure: live dashboards built on the actual signal layer, not a fortnightly slide deck

Why analytics is upstream of every other service

An autonomous system optimises against the signals it receives. If those signals are wrong, optimisation produces wrong results — confidently, at scale.

Two specific failure patterns dominate when analytics is broken:

  • Underreporting: real conversions don't reach the ad platforms (browser-side tracking blocked by ITP, ATT, ad blockers) so the optimisation algorithm thinks campaigns are performing worse than they are and pulls budget incorrectly.
  • Wrong-credit: conversions reach the platforms but get attributed to the wrong source (cookies expired, cross-device journey lost) so the algorithm reallocates spend toward channels that didn't actually drive the result.

Both failures are invisible to non-technical observers — campaigns look fine in the dashboards. They become visible when blended ROAS in the CRM diverges from channel-level ROAS in the ad platforms. Google's own analysis of measurement gaps documents 10-30% of conversions commonly missed in browser-only setups across consumer industries.

The measurement work

Analytics infrastructure

What gets built in a foundation engagement

Typical 60-90 day foundation phase that gets the measurement layer to a state where AI-led optimisation can actually work.

  1. Audit

    Tracking + CRM + attribution baseline

    Crawl the existing measurement layer end-to-end. Where is signal being lost? Where do CRM totals diverge from ad platform totals? What's deduplicated, what's double-counted? Quantified gaps before any work starts.

  2. Server-side

    Move tracking server-side where appropriate

    GTM Server (or platform-specific CAPI). Recovers 15-25% of conversions lost to browser blocking. Configured with consent integration and deduplication so server-side AUGMENTS rather than DOUBLE-COUNTS browser-side.

  3. Definitions

    Conversion definition cleanup

    What counts as a conversion at each funnel stage? Form fill vs MQL vs SQL vs closed-won. Documented, agreed across sales and marketing, configured in CRM and ad platforms consistently. Often the highest-impact part of the work.

  4. Closed-loop

    CRM-to-ad-platform signal wiring

    Closed-won revenue (with deal value) flowing back to ad platforms via offline conversion imports. Lifecycle stage events as intermediate conversions. The work that makes optimisation target revenue rather than form fills.

  5. Validate

    Three diagnostic checks before declaring ready

    Ad-platform vs CRM conversion count match within 10%. Server-side recovery rate 15-30% above browser-only. Deal-value flow-through traceable for a known closed-won deal. Without all three passing, the work isn't done.

The CRO work

Once the measurement layer is reliable, CRO becomes possible. Without it, you're testing into noise — variant A vs variant B differences that are smaller than your measurement error.

Conversion rate optimisation

How CRO testing runs

Hypothesis-led, statistically rigorous, integrated with the paid media optimisation loop.

  1. Identify

    Friction analysis on key conversion paths

    Funnel analytics, session recordings, form abandonment data. Where in the funnel is conversion leaking? What's the value of fixing each leak?

  2. Hypothesise

    Specific testable hypotheses with predicted lift

    Not 'try a new headline' — 'changing the form from 5 fields to 3 will lift completion rate by ~15% based on similar sites in this sector'. Falsifiable, sized, prioritised.

  3. Test

    A/B testing with statistical rigour

    Sample size calculated upfront based on baseline rate and detectable effect. Tests run to significance, not to deadline. Results documented honestly — including the failed tests.

  4. Ship

    Winners scaled, losers buried, learnings captured

    Winning variants ship to production. Failed tests documented as institutional learning so the same hypothesis isn't re-tested in 6 months. Patterns build the brand's CRO knowledge base.

AI-powered vs traditional CRO + analytics delivery

Operating model

What changes when this work runs through the AOS

Dimension
AI-powered (this service)
Traditional CRO/analytics consultancy
Tracking deployment
Server-side default; client-side as backup
Client-side default; server-side as upgrade
Closed-loop signal
Wired from day 1 of any engagement
Often a separate phase 2 project
Test cadence
Continuous on key paths
Project-based test cycles
Reporting
Live dashboard with same metrics the optimisation layer uses
Monthly slide deck
Integration with paid media
Native — same platform, shared signal layer
Coordinated separately; data handoffs

Foundation engagement vs ongoing programme

Two engagement shapes:

Foundation engagement

60-90 days, fixed-scope work. Audit, server-side build, definition cleanup, CRM signal wiring, validation. Suitable for businesses preparing for AI-led marketing or trying to fix attribution problems on an existing programme. Typical investment: £8-25k for fixed-scope work.

Ongoing programme

Monthly retainer covering continuous CRO testing, ongoing measurement maintenance, attribution refinement and reporting. Best paired with paid media services so the optimisation layer benefits directly from the analytics work. Typical investment: £4,500-£12,000/month depending on test cadence and infrastructure complexity.

Interactive · Cost Calculator

Compare against your current CRO + analytics setup

Set in-house analytics headcount, third-party tools and current attribution spend. The calculator gives you a baseline for the comparison.

Your current setup

Current annual cost (excluding media)

£180,000

People + agency + tools. Media spend is held constant on both sides.

AI-powered agency · annual cost (excluding media)

£85,202

Management fee on £20,000/month spend at 23.0% + your existing tools.

Difference

£94,798/year

£7,900/month freed up. Reinvested into media, that’s an extra 4.7 months of working spend each year.

Build your growth plan

Indicative only. Loaded cost per head includes salary, oncosts, software seats and overhead. Real proposals model your specific channel mix, attribution and margin targets via the discovery.

Where this service wins

  • Programmes with meaningful traffic and conversion volume (£10k+/month media spend, 100+ conversions/month) where statistical testing has signal to detect
  • B2B and high-ticket businesses where the gap between platform CPL and CRM-qualified-CPL is structurally large — closed-loop fixes it
  • Operations preparing for or running AI-led paid media — the measurement layer is the structural prerequisite that determines whether AI delivers value
  • Businesses with attribution disputes (marketing thinks programme A is winning, sales thinks it's losing) — usually a measurement problem dressed as a strategy disagreement

Where it doesn't fit

  • Programmes below ~50 monthly conversions — statistical testing requires volume to detect meaningful effects in reasonable time
  • Brands without a CRM or with a CRM that sales doesn't reliably update — the closed-loop signal depends on accurate stage progression, which requires sales hygiene
  • Operations seeking quick attribution fixes without the underlying CRM data work — measurement quality is upstream of attribution accuracy

Read deeper on this

  • Conversion tracking foundations for AI-led marketing — the technical reference for the server-side work this service handles.
  • CRM data quality: what 'good enough for AI' actually means — the upstream prerequisite for closed-loop signal working.
  • Offline conversion imports: the missing piece for AI optimisation — step-by-step on the highest-leverage signal-loop fix.
  • Marketing ROI calculator: model blended return across channels — the ROI framing that defensible analytics enables.

FAQs

Common CRO + analytics questions

Do we need server-side tracking if we have GA4 working?

Yes. GA4 is for understanding user behaviour; server-side tracking is for sending reliable conversion signals to ad platforms. Different jobs. GA4 alone leaves 10-30% of conversions invisible to your ad platforms even when GA4 itself sees them.

How long does a foundation engagement take?

60-90 days for mid-market businesses with reasonable existing tooling. Larger or more complex setups (multiple brands, regions, CRMs) take 4-6 months. Foundation engagements that drag past 6 months usually have organisational blockers (sign-off cycles, stakeholder alignment) rather than technical ones.

What does it actually cost to fix the analytics layer?

£8-25k for a fixed-scope foundation engagement at mid-market scale. Pays for itself in marketing efficiency improvements typically before the first month of the next ongoing engagement — better tracking + closed-loop signal makes any operating model more efficient.

Will this work with our existing CRM?

Almost certainly. We've built closed-loop signal from HubSpot, Salesforce, Pipedrive, Zoho, Monday CRM and several custom CRMs. The work is well-understood; only the integration mechanics vary by platform.

How do you handle privacy compliance?

Consent Mode v2 (or equivalent for non-Google platforms). Server-side tracking respects consent flags. Hashed user data for offline imports. Privacy policy updates documented as part of the engagement. We won't ship tracking that violates user consent — it's both unethical and increasingly a Google policy violation.

Can we do CRO without fixing analytics first?

Technically yes; practically no. Without reliable measurement you're testing into noise — small effects can't be reliably distinguished from measurement error. The first 60 days of any CRO programme typically includes baseline analytics work to ensure tests have signal to measure against.

What's a healthy CRO test cadence?

Depends on traffic. 100k+ monthly visitors can run 2-4 simultaneous tests with reasonable statistical power. 10-50k monthly visitors typically run 1 test at a time, longer cycles. Below 10k monthly visitors, qualitative research (user testing, session recording) usually beats statistical testing for finding wins.

How do you measure CRO impact?

Test-level lift (statistical significance, confidence intervals), programme-level conversion rate trend, blended ROAS contribution from CRO improvements. Reported continuously; reviewed monthly. We document failed tests as institutional learning — they're as valuable as the wins for avoiding repeated effort.

Can you work with our existing analytics team?

Yes. Hybrid is common — your team owns ongoing reporting and ad-hoc analysis; we provide the technical infrastructure work and CRO testing. The platform's measurement layer is configured to support whatever reporting cadence your team needs.

What if we already have an attribution platform (Triple Whale, Northbeam, Rockerbox)?

We can work with it. Most third-party attribution platforms address the cross-channel attribution problem but rely on the same upstream signal quality. The server-side tracking and CRM signal work we do feeds those platforms cleaner data, making them more accurate. We don't replace the attribution tool — we strengthen what it can see.

Sources and further reading

  • Google — Measurement gaps and Enhanced Conversions — Google's documentation on signal loss and recovery via Enhanced Conversions.
  • Meta — Conversions API documentation — Meta's official guide to server-side conversion tracking.
  • Apple — App Tracking Transparency — primary source on the iOS attribution changes that drove most of the server-side migration.

Next step

Put an AI-powered agency behind your marketing.

Run the Growth Planner for a tailored plan, or scope an end-to-end engagement with our team.