ATTRIBUTION·APR 17·9 MIN
Reconciling GA4, Meta, and Shopify purchase counts
The short, full, and nuanced answer on ga4 meta shopify reconciliation. Five sources of variance and the one number to trust per question asked.
READ →
Topical cluster
Attribution & CAPI
Everything about getting Meta, Google, and Klaviyo to agree on what a conversion is. Pixel to CAPI migrations, event_id dedup patterns, consent-mode gotchas, and the forensic work of finding the 30% of conversions your reports are missing. Each piece is grounded in a real DTC rebuild.
12 postsFor: DTC operators $2-10M who suspect their tracking is lying to them
Go deeper
ATTRIBUTION·MAR 18·13 MIN
Hashing PII for CAPI purchase events without leaks
A tutorial on capi purchase event pii hashing. The six-step pipeline that normalizes, hashes, and keeps raw values out of every log sink in production.
READ →
ATTRIBUTION·MAR 16·9 MIN
Debugging CAPI payload mismatches in production
A postmortem on capi payload mismatch debugging. Three root causes, the verification sequence, and the fix that held in production at a Shopify DTC.
READ →
ATTRIBUTION·MAR 14·10 MIN
Why DTC brands should run lift tests over last-click
A contrarian case on lift test vs last click dtc attribution. Why last-click misreads incrementality and how a cheap geo lift gives the real answer.
READ →
ATTRIBUTION·MAR 6·15 MIN
Consent Mode v2 and CAPI - what actually fires on your server
A pattern-library breakdown of consent mode v2 capi behavior across four consent states, with the DTC failure modes each one produces on Meta attribution.
READ →
ATTRIBUTION·FEB 27·11 MIN
CAPI for subscription commerce without double counting
A tutorial on capi subscription commerce. How to fire new-acquisition and rebill events so Meta optimizes against the right DTC cohort, not rebills.
READ →
ATTRIBUTION·FEB 19·12 MIN
Event_id strategy across Shopify Pixel, CAPI, and GTM
A shopify event_id strategy that holds across Pixel, CAPI, and GTM. Five steps with Liquid, GTM web, and server snippets from a Q2 2024 rebuild.
READ →
ATTRIBUTION·FEB 14·8 MIN
Attribution windows after iOS and Android privacy updates
Field notes on how attribution windows ios android shifts changed what Meta and GA4 actually measure, and what DTC operators should do in 2026.
READ →
ATTRIBUTION·FEB 5·13 MIN
Wiring CAPI events around Klaviyo flow triggers
A pattern-library look at capi klaviyo flow integration. Three DTC failure modes where server events and triggers fire out of order, and the fix.
READ →
ATTRIBUTION·FEB 5·14 MIN
Pushing Meta CAPI match quality score from 6 to 9
A tutorial on meta capi match quality score improvement. The field-by-field moves that took a DTC Shopify store from a 6 to a 9 in a production rebuild.
READ →
ATTRIBUTION·JAN 18·9 MIN
Stape vs self-hosted GCP for a server container
A decision log on stape vs gcp server container hosting for a Shopify CAPI rebuild. Costs, control, and the tradeoffs that changed my mind on the pick.
READ →
Why this matters.
Server-side tracking is the part of the DTC stack that quietly decides whether your ad spend is making money. The Meta pixel sees roughly 60-70% of what actually happened on a clean store; once iOS privacy and ad blockers compound, the gap widens. CAPI closes most of it, but only if event_id deduplication, hashed user data, and consent state are all correct on the same payload. Get any one of them wrong and Meta either undercounts conversions or double-counts them, both of which corrupt the optimization signal the algorithm uses to spend your budget.
The articles in this cluster cover the full chain: from the Shopify or Next.js side that fires the event, through the server endpoint that hashes and forwards it, into the Events Manager match-quality score, and back out to the bid surface. Each post is grounded in a real audit or rebuild, with code samples that work in 2026 (App Router, GA4, Consent Mode v2) instead of repeating 2022 advice.
If you run a $2-10M DTC store and your platform reports disagree by more than 10%, the leak is almost always in this layer. Start with the hub article, then read the dedup and consent-mode pieces before touching production.
Put this to work
Server-side tracking, dedup, and the math behind DTC attribution.
> Get the CAPI Leak ReportOther clusters
Shopify
DTC Shopify Infrastructure
Theme architecture, metafields, agent-orchestrated builds, Hydrogen decisions.
Healthcare
Healthcare & Compliance
HIPAA-aware Next.js, audit trails, and regulated DTC patterns.
Solo brand
Creative-Tech Solo Brand
The hybrid creative-director-who-codes operating system.
Pricing
Services Business & Pricing
Productizing services, pricing strategy, and the retainer exit.
Lifecycle
Email & Lifecycle Marketing
Klaviyo flow architecture, retention math, and the LTV playbook.
Agents
AI Agent Engineering
Claude Code sub-agents, MCP servers, skills, and the orchestration stack.
Analytics
Analytics & Data Infrastructure
GA4, BigQuery, and the warehouse-first analytics rebuild.
Conversion
Ecommerce Conversion & UX
PDP patterns, cart decisions, checkout extensions, and the CRO stack.
Programmatic SEO
Programmatic SEO & Content Ops
Scaling content without burning author brand authority.
Paid Social
Paid Social Performance
Meta, TikTok, and Google Ads for DTC operators who also own the data.
Brand
Brand Architecture & Design Systems
Visual identity, naming ladders, and design systems that scale with the business.
Shopify Apps
Shopify App Ecosystem
Selecting, configuring, and replacing the third-party stack on Shopify.
Fractional
Fractional Ops & Service Leadership
Running a high-leverage fractional practice without becoming an agency.
Image AI
Local AI Image Generation
Running Flux, Z-Image, and Qwen locally without the cloud-API bill.
Let’s fix
some problems.
Three short steps below. I read all of these, it’s just me on the inbox. Usually you get a real reply within a day, sometimes the same day if I’m at the desk.
or email direct hello@michaeldishmon.com
01 / 03WHAT YOU NEED
$ cat lead.json | mail -s 'new signal' michael
