Tracking & attribution engineeringClient work
Recover ownership of your tracking, pixels and Shopify apps from a previous agency or vendor — one owner per event, an ownership map and a rollback path.
Sounds familiar?
How I solve it
I build an ownership map for every tag, pixel and app, then rebuild the ones you keep under your own accounts. One owner per event, dead and duplicate tags removed, and every change shipped with a rollback path. On a store bought from a previous owner, the inherited setup is labelled by evidence instead of assumed. And each store gets its own app and its own revocable access, so an offboarding is a switch, not a negotiation.
The point is not to punish the previous vendor. It is to make the setup yours: visible, documented, and movable.
The process
6 steps. Scope and a fixed price are agreed before the first one.
Read-only ownership audit: every tag, pixel, app and ad account, attributed to a source or marked unknown.
Decide what stays: keep what works under your ownership, remove what is dead, duplicated or orphaned.
Move ownership: rebuild the kept tags under your own accounts, one owner per event.
Add the missing leg: order-level click-id stamping where attribution needs it.
Prove it on a real order, then detach the old access.
Hand over an ownership map, a change record and a rollback, and revoke the old tokens.
Handover
Built with
Proof
Client work Done for real clients. Client details are anonymised.
Before → after
Before, one client’s own GA4 property had been dark for about 21 months while the live site ran a GTM container owned by a third party. After the rebuild under the client’s own ownership, the first live ticket sale was traced end to end in the week-one follow-up on 2026-09-07.
US events and ticketing business
took analytics back from a third-party container into the client's own assets across 22/22 scoped items — Google Ads purchase conversions were set up through Fixel Pixel, with no Ads account access, so no Ads-side verification is claimed — then traced the first live sale end to end one week later.
UK pet-accessories store
after a store acquisition, mapped every tag owner, replaced a conflicting setup with a single purchase sender, and proved it with a real paid-click test order carrying the store's first ad click id.
Studio access
a separate, audited token service for client-store work: a reason is required on every call, the token is never printed, and on uninstall a grant is revoked rather than deleted.
He's stepped in and cleaned up work from previous employees that have not done as good of a job as [he] has done.
What you can look at
A redrawn ownership map and a change record on synthetic store data — tag, owner before, owner after, keep or remove, and the reversal path. No client identifiers appear in it.
Client details anonymised. Figures read from live platform APIs at handover in 2026. I am the founder of Fixel Pixel.
Price and timeline
A bounded recovery is a Focused Fix, quoted before it starts, from USD 450. If nobody can say what the current setup even contains, the honest first step is a read-only ownership audit — a Working Session (USD 195) or a Tracking Health Check (USD 395) with a written verdict. That is a real, documented result, not a sales stage.
QuoteFixed before work starts
A note from Daniilbefore you decide
If your team built the tracking and still owns it, with documented access, there is nothing to take back. This is for setups where the owner is a vendor or an unknown party. If the old provider is still delivering and the numbers are trustworthy, moving ownership is risk without reward — and I will say so rather than sell the migration.
— Daniil
Questions
Sometimes access can be transferred; sometimes the cleanest path is to rebuild the kept tags under your own accounts. The ownership audit answers which, before any work starts.
Then we start from what is publicly visible and rebuild forward. The ownership map records what is inherited and what is unknown, so the gap is documented rather than guessed.
By reading the live setup and matching events to real orders. A tag with no owner and no traffic is a candidate for removal, and removal ships with a rollback.
Every change is reversible and tested on a real test order before the old access is detached. The rollback record is part of the handover, not an extra.
No. Access is scoped, logged and revoked on offboarding, and each store has its own app rather than a shared key.
The first answer is free, within one working day. Or write directly: next@taskfordaniel.com
