Can you fix duplicate conversions (double counting)?

Yes. It’s usually caused by overlapping triggers, multiple containers, hardcoded scripts, or duplicate tags. I dedupe and document what’s firing where.

Do you handle Meta Pixel and consent-mode/cookie banners?

Yes. I can wire consent correctly, ensure tags behave as expected, and validate attribution-related events where possible.

Do you set up e-commerce events for WooCommerce?

Yes. I can implement or fix key e-commerce events and conversions, then verify they’re reporting correctly.

Tracking

GA4, GTM & Pixel Tracking — tracking that’s boring and correct

Tracking should be reliable and consistent — not “it fires but doesn’t count”. I fix broken GA4 conversions, messy GTM containers, duplicate tags, consent issues, and attribution problems so your data becomes usable again.

Get help with tracking See work

UK-based • Debug-first • Clean setup

Diagnose

Find the real cause

Identify where it breaks: site events, GTM logic, consent, GA4 config, or platform limitations.

Fix

Clean conversion tracking

Fix events, conversions, and dedupe issues so reporting becomes trustworthy.

Stabilise

Make it stay working

Document event naming, mappings, triggers, and what’s wired where — so it doesn’t break silently later.

The goal

You should be able to answer: “what counts as a conversion?”, “where does it fire?”, and “how do we test it?” without guessing. That’s what I aim for — clean tracking you can trust.

Who this is for

This is for teams who need tracking to reflect reality — especially when ads or conversion decisions rely on it.

✅ E-commerce and lead-gen sites

✅ Businesses running Google Ads / Meta Ads

✅ Sites with broken conversions or mismatched numbers

✅ Teams inheriting messy GTM containers

Based in South Yorkshire

UK tracking support

I’m based in Rotherham, working with clients across Sheffield, Leeds and the UK. If you need tracking fixed quickly and properly, I can help.

Request help All services

Common fixes

What I typically fix

DebugView • GTM Preview • Real tests

Common tracking issues

✅ GA4 conversions not tracking

✅ GTM triggers/tags misfiring

✅ Duplicate tags (double counting)

✅ Meta Pixel events + attribution issues

✅ Consent-mode / cookie banner implications

✅ “It fires in preview but doesn’t show in GA4”

Where it usually goes wrong

✅ Wrong event names or parameters

✅ Incorrect GTM trigger conditions

✅ Consent blocking tags unexpectedly

✅ SPA / dynamic DOM changes not handled

✅ Multiple containers / hardcoded scripts

✅ Incorrect GA4 settings, filters, or conversions

Fix my tracking See outcomes

Deliverables

What you get

The goal is simple: clean tracking you can trust — and a setup that’s understandable and maintainable.

✅ Clear event naming + mapping

✅ Tested conversions (GTM Preview / GA4 DebugView)

✅ Reduced duplication / cleaner container

✅ Notes so it stays stable

View the full process Get a quote

Approach

How I fix tracking

① Confirm desired conversions and definitions

② Inspect existing GTM/GA4 + consent setup

③ Test with GTM Preview + GA4 DebugView

④ Fix event names/params and remove duplicates

⑤ Document the setup so it stays correct

FAQ

Tracking questions

Clear answers • No fluff

Why does it show in GTM Preview but not in GA4?

Often it’s event naming/parameters, GA4 config, consent behaviour, or filtering. I test end-to-end and fix the actual break.

Can you fix duplicate conversions?

Yes — usually caused by multiple tags/containers, hardcoded scripts, or overlapping triggers.

Do you handle Meta Pixel + consent?

Yes — including consent-mode implications, cookie banner wiring, and ensuring events fire correctly when allowed.

What does it cost?

It depends on complexity. Send a brief and I’ll reply with a quote range and next steps.

Want tracking you can trust?

Tell me what you’re trying to measure and what’s currently broken — I’ll suggest the simplest safe fix and reply with a quote range.

Request help Browse services