What I
build.
Tracking audits, server-side infrastructure, offline conversions, lead automation, and audience suppression, for businesses where the data between ad platforms and CRM needs to actually agree.
Tracking Audit & Data Reconciliation
When Meta shows more leads than your CRM, blame tends to move fast: media buyers suspect the pipeline, and developers point at attribution setup or GTM configuration. Usually both are right to be confused and wrong about the cause. The discrepancy almost always lives in a layer neither team fully owns: I audit it, find the source, and explain it clearly enough that everyone can stop questioning each other's systems. In one recent engagement the gap was 35–41%, caused by three simultaneous issues, none of which either team had caught because each one only shows up when you look across the full tracking stack at once.
What you get · Fixed fee · about a week from access to report
You get a written root-cause report your media buyer and your developer can both read, plus a prioritised fix plan, yours to act on whether or not I implement it.
- Meta vs CRM lead count diagnosis
- CAPI & pixel deduplication fix
- Auto-event and attribution audit
- Root cause report for media and tech teams
Meta: 20 · CRM: 16
↓
Identify the inflation source
↓
Fix deduplication logic
↓
One agreed number
Tracking & Data Architecture
A meaningful share of your conversions never reaches the ad platforms: ad blockers stop the pixel from loading, Safari caps cookie lifetime, iOS strips identifiers, and consent banners block tags before they fire. The conversions still happen; the platforms just never hear about them. So reported ROAS looks worse than reality, and the algorithm optimises on partial signal. I build the server-side layer that sends events from your own infrastructure instead of the user's browser, so your data is complete before anything else gets built on top of it.
- Server-Side GTM Implementation
- Meta CAPI with deduplication
- GA4 event architecture
- Consent Mode v2 configuration
Browser event fires
↓
Server-side GTM container
↓
Meta CAPI · GA4 · Google Ads
Offline Conversion Tracking
Ad platforms optimise toward whatever outcome you tell them to. If you only send leads, they find more leads, not necessarily buyers. I route your CRM's closed-sale data back to Google and Meta so the algorithms learn from revenue.
- Meta Offline Conversions (CAPI)
- Google Ads Offline Conversion Import
- HubSpot & ActiveCampaign integration
- Make.com & n8n webhook pipelines
Deal closed in CRM
↓
Make.com or n8n webhook
↓
Google Ads OCT · Meta CAPI
Lead & Data Automation
Leads that sit in a form submission for hours decay fast. I build the pipelines that move data between your ad platforms, CRM, and internal tools the moment something happens.
- Real-time CRM routing
- Meta Lead Ads & Typeform automation
- Slack & email alert pipelines
- n8n anomaly detection for ad spend
Lead form submitted
↓
Make.com or n8n
↓
CRM · Slack · Email
Audience Suppression & Customer Match
When someone buys, they should stop seeing your acquisition ads immediately. Most brands don't do this, not because they don't want to, but because their CRM data never syncs back to the ad platform in time. I automate that sync so converted customers get excluded the moment they close, and moved into retention or upsell segments instead.
- Meta Custom Audience automation
- Google Customer Match sync
- CRM-based suppression lists
- Post-purchase audience segmentation
Customer converts in CRM
↓
Make.com or n8n
↓
Excluded from acquisition ads
↓
Moved to retention segment