Skip to content

Tracking & attribution engineeringClient work

Not on Shopify? Conversion Tracking for WooCommerce, Magento and Custom Carts

Conversion tracking for WooCommerce, Magento, PrestaShop and custom carts — GA4, Google Ads and Meta set up and proven against real orders.

For
Non-Shopify stores
Checked

Sounds familiar?

Tick what applies to you

The situation Tracking & attribution engineering
Your checkout is not Shopify, and the tracking tools assume it is.

Tick the lines that describe your case.

Describe my task

How I solve it

What I build

I build conversion tracking on the carts Shopify’s app store does not cover: WooCommerce, Magento 1.9 and 2, PrestaShop, 3dcart, Volusion and custom carts. GA4 e-commerce with real transactions and revenue, Google Ads and Meta conversion tags, dynamic remarketing with matching product IDs, and a cross-domain path for hosted or third-party checkout — proven against real orders, not a test tag.

The same work runs in both directions: I have set e-commerce tracking up on these platforms from scratch, and I have fixed it after an update, a migration or a previous developer left it half-done.

The process

How it works

6 steps. Scope and a fixed price are agreed before the first one.

  1. Read-only map: what owns each event today, from the theme, a plugin or an old snippet, and what is dead.

  2. Choose the source of truth for a purchase: the order record, the thank-you page or the dataLayer.

  3. Send transactions and revenue to GA4, with the item data catalog ads need, not just a total.

  4. Wire Google Ads and Meta conversions, and add a server leg with dedup where the browser alone is not enough.

  5. Fix the cross-domain hop for third-party or hosted checkouts so the session and the click id survive.

  6. Verify on real orders, then hand over a change record and a rollback.

Handover

What you get

  • A purchase event that fires once per order and carries its value and its items.
  • GA4 e-commerce — transactions, revenue and item data — so catalog and remarketing work.
  • Google Ads and Meta conversion tags, with dedup if a server leg is added.
  • A cross-domain path for hosted or third-party checkout, so attribution survives the hop.
  • A change record and a rollback, and an ownership map of what owned each event before.

Built with

  • WooCommerce
  • Magento 1.9 and 2
  • PrestaShop
  • 3dcart
  • Volusion and custom carts
  • GTM web and server
  • GA4 e-commerce
  • Google Ads
  • Meta CAPI
  • My first-generation product also shipped source-platform adapters for WooCommerce and Funnelish on one server-side pipeline

Proof

Done before, with dates and numbers

Client work Done for real clients. Client details are anonymised.

Before → after

Before, purchases on these carts routinely went missing: a WooCommerce checkout flow that broke at Klarna, a Magento multistore conversion path, and custom carts with no purchase event at all. After, transactions and revenue are sent from the thank-you page or the dataLayer as GA4 e-commerce. The body of work behind this is 52 completed e-commerce-analytics and 93 GA/GTM contracts on Upwork (averages 4.93★ and 4.96★, 2016–2020), and the v1 pipeline shipped WooCommerce and Funnelish adapters across 632 commits from 2022-01 to 2026-05.

  • Upwork e-commerce analytics track

    2016–2020 · 52 contracts, average 4.93★

    GA enhanced e-commerce on Shopify, WooCommerce, Magento 1.9/2, PrestaShop, 3dcart, Volusion and custom carts.

  • Upwork GA/GTM track

    2016–2020 · 93 contracts, average 4.96★

    tag management and tracking, including sites moved from hard-coded snippets into GTM without losing existing goals.

  • Fixel Pixel v1

    archived 2022–2026

    source-platform adapters for Shopify, WooCommerce and Funnelish on one server-side pipeline that sent storefront and order events to Meta, TikTok, Pinterest and Snapchat; superseded by 2.0.

Rated 5 out of 5 on Upwork.

Super efficient and knowledgeable. He is one of the most thorough people I have ever hired in UpWork. His documentation is excellent.

Eduardo Y., ClickMinded Upwork · 2017

What you can look at

A redrawn order-to-platform flow for a non-Shopify cart — checkout → order record → GA4 / Ads / Meta — on a synthetic checkout, with the plugin or theme owner shown at each step. No client data appears in it.

Client details anonymised. Figures read from the Upwork export and the archived platform records. I am the founder of Fixel Pixel.

Price and timeline

What it costs and how it runs

A bounded repair is a Focused Fix, quoted before it starts, from USD 450. A rebuild across the cart and its checkout is a Custom Engineering Project, quoted in writing from USD 1,500. If the first honest step is to find out what exists, that is a read-only sequencing question we settle before any tag changes.

QuoteFixed before work starts

Price
Focused Fix from USD 450 for a bounded repair, or a Custom Engineering Project from USD 1,500 for a full rebuild across a cart and its checkout, scoped and quoted in writing. Discussing the task is free.
Timeline
Focused Fix: fixed quote before start. Full rebuild: scoped and quoted in writing. The verification order is agreed before any tag changes.
First step
Describe the task. I reply within one working day, free, and tell you which option fits — or that you can fix it yourself.
Describe a task like this

A note from Daniilbefore you decide

When you don’t need this

If your cart already has a supported first-party integration and its purchases agree with the storefront, keep it. A rebuild pays off when purchases are missing, doubled, or unattributable, or when a hosted checkout breaks the session. If the platform has no real event to hook, the honest first step is a read-only audit to find what does exist — and I will say that rather than sell a rebuild.

— Daniil

Questions

What people ask about this

Do you only work on Shopify?

No. A large part of my Upwork track record is e-commerce tracking on WooCommerce, Magento, PrestaShop and custom carts, and I am comfortable in a stack I did not build.

The purchase fires but with the wrong value — is that different?

Often it is the same root cause: the tag is reading the wrong source. I check where the value comes from before changing the tag.

Can you track a hosted third-party checkout?

Usually, yes, through a cross-domain path or a server-side event. Whether the platform exposes enough to do it cleanly is a scoping answer, not a promise.

Will you need access to my theme or plugins?

Usually read-only access to the cart and the tag manager. Where the platform gives me no interface, I hand over paste-ready instructions instead.

What if a previous developer left conflicting tags?

That is common. The first step is an ownership map, then one owner per event — the same discipline I use on any platform.

More like this

All situations
Daniil Maximkin

Hi, I’m Daniil.

I work with you from defining the problem to implementation and handover. You talk to the person who does the work. I work in English and Russian.

My story My work

Have a task like this?

Describe your task

The first answer is free, within one working day. Or write directly: next@taskfordaniel.com