AI Infrastructure / Attribution
iOS 14.5 and the privacy changes that followed quietly broke the pixel that your entire paid strategy depends on. Browser-side tracking now misses a large share of conversions, your platforms fight over the credit they can still see, and you are scaling spend on numbers that no longer add up. I rebuild attribution on server-side tracking so your measurement is trustworthy again.
App Tracking Transparency let users opt out of cross-app tracking, and browser changes piled on with shorter cookie lifetimes and blocked third-party scripts. The practical result is that the client-side pixel only fires for a fraction of your real conversions. Meta and Google each see a different partial slice, so they both over-claim, your blended numbers double-count, and the dashboards stop matching the bank.
You cannot fix this with a setting. The conversions that the browser can no longer report have to be captured server-side, where ad blockers and cookie limits do not reach, and sent to each platform through its server API with proper deduplication. That is an engineering and measurement project, and it is the one that makes every paid channel readable again.
A server-side tracking layer that captures conversions the browser drops, then forwards them cleanly to each platform. See server-side GTM.
Meta Conversions API and Google enhanced conversions wired with deduplication and advanced matching for high signal quality.
One source of truth that reconciles Meta, Google, and your store so platforms stop double-claiming the same sale.
Dashboards that show real contribution, so budget decisions rest on data you can defend to a board.
I measure how far your reported conversions sit from reality and find where signal is leaking, so we fix the biggest holes first.
I stand up server-side tracking and wire the Conversions API and enhanced conversions with deduplication, so platforms see complete events again.
I reconcile the platforms into one source of truth, document the system, and hand your team reporting they can run without me.
This is not a problem I hand to a vendor. I build server-side tracking and attribution for the ecommerce and SaaS brands I run growth for, and I run my own marketing operation on a self-hosted stack of n8n, the Claude API, and Postgres where the same measurement discipline applies. I led acquisition at Elementor from roughly $200K to over $20M ARR as it passed five million users, and I led growth at cnvrg.io ahead of its acquisition by Intel announced in November 2020 (TechCrunch). I drove 337% MRR growth at Riverside on measurement I trusted. See the n8n and AI infrastructure work.
| Good fit | Not a fit |
|---|---|
| Ecommerce or SaaS spending real money on paid | No paid spend and no conversions to track |
| Reported ROAS no longer matches revenue | Happy to keep guessing on partial data |
| Want one operator across tracking and growth | Want a tag-manager tweak, not a rebuild |
| Ready to invest in the measurement layer | Looking for a free quick fix |
Attribution rebuilds run as an infrastructure project or fold into a broader operator role.
2-4 week audit of your growth stack plus a 90-day roadmap. Fixed scope, converts to a retainer.
No. The conversions the browser can no longer report have to be captured server-side and sent through each platform’s server API. That is a build, not a setting.
Meta’s server-side endpoint for sending conversion events directly from your server, bypassing the browser limits that broke the pixel. Google’s equivalent is enhanced conversions.
Each platform only sees a partial slice of conversions and claims credit for what it can see, so the same sale gets counted twice across platforms. Reconciliation into one source of truth fixes that.
Yes. I build server-side tracking and the Conversions API on both, which covers most ecommerce stores, as well as SaaS apps.
A fixed-scope diagnostic sprint runs $6,000 to $8,000. Infrastructure builds start at $5,000 per month. A full embedded operator engagement runs $8,000 to $18,000 per month.
The core server-side layer is usually live within a few weeks, after which reported conversions converge with real revenue and scaling decisions become trustworthy.
Both options exist. On an advisor engagement I spec it for your engineers. On an infra or operator engagement I build it myself.
Directly. Once measurement is trustworthy, Meta and Google relearn on complete signal and scaling decisions stop being guesses. See Meta ads and Google Ads.
Book a 15-min call. I will tell you how far your reported conversions sit from reality and what the rebuild involves.