adev.build
Adem replies within the hourStart a project

Your ads can only optimise on the sales they can see.

I fix the technical layer between your ad spend and your revenue. That means Shopify checkout customisations rebuilt on Functions and Checkout Extensibility, plus server-side tracking with GTM, Meta Conversions API and GA4 that matches what's really in your Shopify orders.

Shopify Checkout & Server-Side Tracking, part of Commerce & Growth

Check your site free: tracking & pixel checker

The orders your ad platforms can see, before and after the fix

Sound familiar?

  • Meta, Google and Shopify all report different purchase numbers, and none of them match your bank account.
  • Your discounts, shipping rules or payment customisations rely on Shopify Scripts or checkout.liquid that are being retired.
  • iOS privacy changes, ad blockers and consent banners have quietly cut the conversions your ad platforms receive.
  • Pixels fire twice, purchase events are missing values, or consent mode was "set up" but nobody has checked it.

Who it's built for

  • Shopify and Shopify Plus brands spending $5k+ a month on paid ads
  • E-commerce teams migrating off Shopify Scripts and checkout.liquid
  • Performance marketing agencies that need a technical partner for tracking implementation

See how it fits e-commerce & dtc brands.

Built by someone who ships

I build and run production software myself, from pricing engines to automation platforms. Your build gets the same care: tested before real customers touch it, monitored after.

Two problems, one buyer

Shopify brands in 2026 face two technical problems that land on the same desk:

  1. Checkout is being rebuilt underneath you. Shopify is retiring Scripts and checkout.liquid in favour of Shopify Functions and Checkout Extensibility. Custom discounts, tiered pricing, shipping rules, payment method rules and checkout tweaks built the old way have to be rebuilt, or they simply stop working.
  2. Your ad platforms are flying half-blind. Between browser privacy features, ad blockers, iOS changes and consent banners, a large share of purchases never reach Meta or Google through the browser pixel. Their algorithms optimise on the conversions they see. Missing or duplicated purchase events directly inflate your cost per acquisition.

Both need someone who understands Shopify’s platform, tag management and how ad platforms consume conversion data. That’s why I offer them as one service.

What a proper tracking setup looks like

  • One source of truth. Purchase events carry the Shopify order ID, value, currency and items, so every platform can be checked against real orders.
  • Browser and server events, deduplicated. The browser pixel and the server-side event share an event ID, so Meta and Google count each purchase once while recovering the ones the browser missed.
  • Server-side GTM. A server container, for example hosted on Stape, sends clean conversion data to Meta CAPI, Google Ads enhanced conversions and GA4 from a first-party endpoint.
  • Consent that actually works. Consent mode v2 is wired to your banner, and tags respect what the visitor chose. That’s checked with real test sessions, not assumed.
  • Documentation. Every tag, trigger and event is listed, so the next marketer or agency doesn’t have to reverse-engineer the setup.

Scripts to Functions: the migration

For checkout customisations, the work usually looks like this:

  1. Inventory every Script, checkout.liquid edit and checkout-related app.
  2. Map each one to its modern equivalent: a discount, delivery or payment customisation Function, a Checkout UI Extension, or an existing app that now covers it.
  3. Build and test it on a development store with real cart scenarios.
  4. Switch over with a rollback plan, then compare discount and checkout behaviour to the old setup.

Start with an audit

Most brands don’t need to rebuild everything. The fixed-price Tracking Audit + Fix shows you exactly how far each platform’s numbers drift from your real orders, fixes the browser-side problems straight away, and tells you whether server-side tracking is worth it at your spend. If your store also needs accessibility work, see Accessibility Audit & Remediation.

What you get

  • A tracking audit comparing each platform's conversions to your Shopify orders
  • Clean browser-side tracking with correct purchase values, currencies and IDs
  • Server-side tracking via sGTM (e.g. on Stape) and Meta Conversions API, if included in scope
  • Scripts-to-Functions migration and checkout UI extensions for your customisations, if included in scope
  • Documentation of every tag, trigger and event, plus a handover call

How the build runs

  1. Audit

    I compare what each ad platform and GA4 recorded against your actual Shopify orders for the same period, and inventory every pixel, tag and script.

  2. Plan

    You get a short list of what's broken, what it's costing you in lost signal, and a fixed price for the fix, from a quick browser-side repair to a full server-side setup.

  3. Implement

    Tracking and checkout changes are built and tested on a development theme or store first, with test orders verified end to end.

  4. Verify

    After go-live, I monitor event coverage and match quality, then compare platform numbers to orders again to confirm the gap has closed.

Built with tools like Shopify, Shopify Functions, Checkout UI Extensions, Customer Events, Google Tag Manager, Server-side GTM, Stape, Meta Conversions API.

Questions owners ask

Why do Meta, Google and Shopify show different numbers?

Some difference is normal because each platform uses its own attribution model. Big gaps usually mean lost signal, from ad blockers, browser privacy limits, consent banners blocking more than they should, or events that fire incorrectly. Server-side tracking and proper deduplication typically close much of that gap.

Is server-side tracking compliant with GDPR and consent rules?

It can be, if it's set up to respect consent. Server-side tracking isn't a way around a user's choice. Done properly, it sends better-quality data for users who consented, and limited or no data for those who didn't. I configure consent mode v2 and respect your banner's signals, but your legal team or CMP provider should confirm your overall policy.

When do Shopify Scripts stop working?

Shopify has announced the retirement of Scripts and the move away from checkout.liquid in favour of Shopify Functions and Checkout Extensibility, with deadlines reported around mid-2026. Check your admin for your store's exact date. If your discounts, shipping or payment rules use Scripts, they need to be rebuilt as Functions before then.

What does server-side tracking cost to run?

A hosted server-side GTM container (for example on Stape) typically costs somewhere between a few dollars and around $100 a month, depending on traffic. I'll recommend the smallest plan that fits your volume.

Do you work with agencies?

Yes. Many performance agencies handle strategy and creative, and bring me in for implementation. See the partner page for white-label terms.

Often paired with

Want this quoted for your business?

You'll get a reply within 1 business hour, from me, with questions or a first plan and price.