Fix broken or unreliable ecommerce conversion tracking.
We repair an agreed, testable tracking failure within a written scope, prove the result with a test order and hand over what changed. We won't promise that every advertising platform will match your store's numbers, because no honest fix can.
Symptoms
- Orders are coming in, but GA4 shows no purchases, or far fewer than it used to.
- Purchases are counted twice in GA4 or Google Ads.
- Purchase revenue is zero, in the wrong currency, or includes the wrong amounts.
- Tracking changed after a theme update, a new app or plugin, or a checkout change.
- Google Ads conversions stopped recording, or started recording from the wrong source.
If you can name the symptom, this page is for you. If you can't yet, start with a GA4 and GTM audit.
Likely failure points
Most broken purchase tracking comes down to a small number of places:
| Failure point | What typically goes wrong |
|---|---|
| Where the purchase event is generated | The tag lives in theme code that no longer runs on the order confirmation page, or in a script area the platform has retired |
| Duplicate sources | An app or plugin and a GTM tag both send purchase, so each order is counted twice. See duplicate purchase events |
| The order identifier | transaction_id is missing, empty or the same for every order, so de-duplication can't work |
| Value and currency | Value sent as text, including tax or shipping inconsistently, or currency missing |
| Consent handling | Tags wait for a consent update that never arrives, or fire before consent when they shouldn't |
| Trigger timing | The tag fires on a page view that a payment redirect skips, or on a page that reloads |
Shopify: the £495 fixed-scope offer
Shopify Purchase Tracking Fix
£495
A fixed-scope service for one Shopify store and one agreed GA4 purchase-tracking path.
Request a tracking fixIncluded:
- Review the current GA4 purchase-tracking implementation.
- Identify the agreed purchase event problem.
- Correct the selected implementation path, where technically feasible within scope.
- Check transaction ID, value, currency and the relevant ecommerce payload fields.
- Run a suitable end-to-end verification with your cooperation and an appropriate test order.
- Review consent handling for the selected event path.
- Provide a before and after evidence summary and a handover.
Payment is split in two: £247.50 after you accept the scope and before work starts, and £247.50 on completion of the agreed deliverables and handover.
If the selected event turns out to be working already, or the root cause needs out-of-scope work, Mikael explains the finding and agrees any change with you before going further. Nothing extra is charged without your agreement. More on Shopify specifics: Shopify tracking and Shopify purchases not showing in GA4.
Other platforms and other fixes
For WooCommerce, other platforms, or a fix that isn't a single Shopify GA4 purchase path, the defined fix starts from £495. Before any work, you receive:
- a written problem definition;
- an agreed implementation plan;
- the scope: one change or one cohesive set of changes.
The £495 starting price is not a promise to repair every GA4, Meta, Google Ads, WooCommerce and Merchant Center fault for that amount. Larger problems are quoted in writing first. WooCommerce stores, see WooCommerce tracking.
Testing methodology
A fix is only finished when the evidence shows it working:
- Baseline. We record what the current setup sends before changing anything, so the before and after can be compared.
- Debug check. GTM Preview, Tag Assistant or browser developer tools confirm the event fires once, at the right moment, with the right fields.
- Test order. With your agreement, a real test order goes through checkout. We note its order number, then confirm that the same
transaction_id, value and currency arrive in GA4 DebugView or Realtime. - Consent paths. The order path is tested with consent accepted and declined, and the behaviour is recorded for each.
- Follow-up look. Standard GA4 reports can take a day or more to process, so we check the reports again after processing rather than relying on Realtime alone.
An illustrative example of what we compare after a test order:
Store order: #1043 total 54.00 GBP
GA4 purchase: transaction_id "1043" value 54.00 currency "GBP" items 2
Result: one event, values match, sent once
Handover
- A short written summary: what was wrong, what changed, where it lives now.
- The testing evidence: screenshots or exported debug output for the test order.
- Remaining limitations, stated plainly, for example consent-declined visitors who are not measured.
- What to recheck after future theme, app or checkout changes.
Exclusions
- Full Google Ads and Meta rebuilds.
- Custom server-side infrastructure.
- Multiple storefronts.
- Broad theme or checkout redesign.
- Payment gateway engineering.
- Fixes to unrelated marketing apps.
- Backfilling historical data.
- Any promise that Shopify and GA4 revenue will match exactly.
- Any promise about attribution or campaign performance.
For Google Ads and Meta signals specifically, see Google Ads and Meta conversions. All prices are on the pricing page.
Introductory pricing. These are introductory prices for our current service packages. We agree the scope and price with you before work starts. Future prices may change, but an accepted quote won't change without your agreement.
FAQ
Will my GA4 numbers match my store's orders after the fix?
Closer, if a fault was causing the gap, but not exactly. Visitors who decline consent, ad blockers and refunds all create legitimate differences. We tell you which ones remain.
Do you need to place a real order?
For a purchase fix, yes, a test order is the only way to confirm the event end to end. You choose the product and refund it afterwards.
What if the problem is bigger than the agreed scope?
We stop, explain what we found and quote the extra work. You decide whether to go ahead.
Not sure what's wrong?
Send us your store address. Mikael will look at the public pages and tell you what he can see, and what he can't.