// Analytics & conversion tracking

KNOW WHATCOUNTS.THENCOUNT IT.

// The useful starting point

Measure the actions that matter and understand the gaps. Clear event definitions, tested tracking and reporting that helps you decide what to do next.

// 01 / The short answer

A dashboard is only as useful as its definitions.

Conversion tracking records agreed website actions so you can assess marketing and the customer journey. I help define the outcomes, review existing analytics and tags, configure supported events and test what is actually recorded. The work can cover website analytics, advertising conversion signals and a practical reporting view within an agreed platform scope.

We separate intent from completion and business value. Clicking a phone link is not the same as having a conversation; submitting a form is not the same as becoming a suitable lead. Reports explain those differences and the limits created by consent choices, browser restrictions, external platforms and attribution methods. Good tracking improves your evidence; it does not manufacture campaign performance.

// 02 / Where this fits

Get the definitions straight.

Useful when the business needs to trust a specific decision, rather than collect more charts.

// 01

Platforms disagree

Your website analytics, ad account and enquiry inbox show different totals. We inspect definitions, date settings, attribution and duplicate signals before treating any one figure as the whole truth.

// 02

Everything is called a conversion

Reports combine button clicks, form starts and submissions. We define a meaningful primary outcome and keep supporting actions visible without inflating the headline number.

// 03

A launch needs reliable measurement

A new site, campaign or form changes how actions happen. We map the journey and test measurement before launch, including what cannot be observed on external systems.

// 03 / What I do

A measurement plan with working checks.

The engagement covers agreed setup and verification, with enough documentation for your business to keep control.

// 01

Outcome and event specification

Define each action, trigger, required values and intended use. Identify primary business outcomes versus diagnostic events. Agree naming, ownership and the reporting question each event answers before adding tags.

// 02

Account and implementation audit

Review the agreed analytics, tag management and advertising accounts, existing plugins and consent configuration. Locate duplicated tags, missing paths and access gaps. Check which system generates an event and which destinations receive it.

// 03

Configuration and verification

Implement the supported events and connections in scope. Test success, validation errors, repeat actions and relevant consent states; check that completion signals fire at the correct point and avoid accidental duplication. Do not put form contents or unnecessary personal information into analytics events.

// 04

Reconciliation and useful reporting

Compare recorded actions with the available business records over an agreed period. Explain attribution windows, reporting delays and observability gaps. Deliver event documentation and a report or dashboard built around decisions, with responsibility for future checks.

// 04 / In application

Different actions need different proof.

Illustrative measurement plans. These examples do not report client traffic, bookings or revenue.

// Trades

Separate contact intent from a suitable job.

An ad account reports conversions, but the contractor cannot relate the number to worthwhile enquiries.

The approachSeparate phone-link clicks and successful form submissions. Add a practical lead-quality review, with any offline status connection assessed against the available systems and permissions.

What to checkReport observed actions and suitable enquiries as distinct stages, explaining unmatched or unobservable contacts.

// Golf, coaching and venues

Measure the booking handoff honestly.

The website sends players to an external booking provider without exposing confirmed bookings to website analytics.

The approachTrack the relevant outgoing action, check provider-supported completion data and document any cross-domain limitation. Label a booking-link click as a handoff until completion can be verified.

What to checkUse observed handoffs and separately available provider totals without treating them as interchangeable.

// Furniture and product businesses

Keep orders and custom enquiries distinct.

A product business sells standard items and receives made-to-order requests through the same site.

The approachDefine separate purchase and enquiry events. For supported ecommerce tracking, check order identifiers, value handling and duplicates against actual order records; define cancellations and refunds in reporting.

What to checkReport completed orders, order value and custom enquiries separately, with the measurement and reconciliation limits stated.

// Illustrative event acceptance checks

What happened, exactly?

An event should have a definition and a test before it becomes a headline in a report.

What happened, exactly?
ActionWhat to recordAcceptance check and limit
Visitor clicks a phone link.Contact intent from the relevant page.Record the click once; do not label it a completed call or qualified lead.
Form shows a validation error.A diagnostic error signal only if needed and safely defined.No successful-submission event; exclude entered personal details from analytics.
Form submission succeeds.Successful submission for the agreed form.Verify the success path and actual delivery; check refresh or duplicate tag behaviour.
Visitor moves to an external booking system.Outgoing booking handoff.Confirm the link and label the observability boundary until completion data is supported.
A supported store records a completed order.Purchase with an agreed identifier and value definition.Check one event per order and reconcile to order records; explain refunds and attribution separately.
// 05 / The method

Define. Implement. Verify. Explain.

// 01

Agree the measurement question

Start with the business decision, action definitions and accounts involved. Identify data owners, consent settings and any third-party journey boundary.

// 02

Audit and configure

Inspect existing tags and events, remove agreed duplication and implement the scoped measurement plan. Keep a record of changes and account responsibilities.

// 03

Exercise the real paths

Test successful, failed and repeated actions across the relevant devices and consent states. Check event receipt and the underlying form, order or handoff rather than relying on an installed tag alone.

// 04

Reconcile and hand over

Compare an agreed sample with business records, document differences and explain the reporting view. Give your team the event definitions and a checklist for rechecking after site or platform changes.

// 06 / A clear agreement

Know what is observed and what is inferred.

The right scope makes the work useful. Agree the deliverables, dependencies and responsibilities before starting.

Included in the agreed work

  • Outcome definitions, event plan and agreed account audit
  • Supported analytics and advertising event configuration
  • Documented checks for success, failure, duplication and relevant consent states
  • Reconciliation, reporting setup and account-owner handover within scope

Separate or out of scope

  • Recovery of historic actions that were never recorded
  • Perfect attribution across people, devices and platforms
  • A full CRM, data warehouse or unrestricted custom integration
  • Server-side infrastructure, paid call-tracking tools or ongoing monitoring unless agreed

What shapes the cost

Scope follows the platforms, events, forms, ecommerce requirements, consent setup, external handoffs and reporting connections. A straightforward lead form differs from a store with order data and several advertising destinations. Tool fees and specialist integration work are identified separately.

What shapes the timing

Definitions and account access come first. Configuration is followed by live-path testing; reconciliation needs an agreed observation period and access to the relevant business records. A platform’s reporting delay is not the same as an implementation fault.

Who owns what

I define, implement and verify the agreed measurement. You own the accounts, approve data collection choices and supply access plus business records for reconciliation. Your team or adviser owns privacy policy decisions; third-party providers determine which completion data their systems expose. Future site changes need an assigned recheck owner.

// 07 / Work you can inspect

Verification is the deliverable.

The event acceptance table shows how actions are distinguished and implementation is checked. Russley’s website connects visitors with an existing DotGolf booking route: a useful example of the kind of external handoff that needs its own measurement definition. The tracking scope starts by checking what that external system can actually report.

Russley Golf Centre website

A documented website project with an existing external booking handoff.

// 08 / Useful questions

Before we start.

Why do Google Ads and website analytics show different conversions?

They can use different definitions, attribution windows, date treatment and measurement methods. Duplicated tags, consent choices and reporting delay can add further differences. We compare the specific action and settings before reconciling totals; disagreement alone does not prove either account is broken.

Can you track every lead and sale?

No. Some actions happen by phone, offline, across devices or on systems that do not expose completion data. Consent and browser choices also create gaps. We define what is observed, what comes from business records and what remains an estimate instead of promising complete visibility.

Is a thank-you page enough to track a form?

Sometimes it is part of a useful implementation, but the real success path needs checking. A page may be revisited, loaded directly or used by several forms. The test should establish that a genuine successful submission is recorded as intended and that errors are not counted as success.

Do you handle GA4, tags and ad conversions?

These can form part of the agreed scope. We review your website platform, analytics, tag manager and advertising accounts, then specify the supported events and destinations. Ecommerce, offline outcomes, call tracking and server-side setups each need their own capability and scope check.

Will new tracking recover our old data?

It cannot recreate events that were never collected. Existing records may help explain a historic period, but they should not be presented as newly measured website behaviour. We document the implementation date and any breaks in comparability when reading later reports.

What will we receive at handover?

An event definition list, the scoped configuration, test evidence, known limitations and the agreed reporting view. Your business retains account ownership. We also identify when checks should be repeated, such as after a form replacement, site release or connected-platform change.

// A useful next step

COUNT THE RIGHT THINGS.

Bring your website, platforms and the report you are trying to trust. We can define the important actions, check the gaps and scope a measurement setup you can use.