PortfolioScope
In headless commerce, product and cart tracking may work well, but purchase tracking often breaks at checkout handoff.
This series covers the full design: identify drop points → bridge identifiers → send purchase server-side.
Core Pattern
- Define where tracking can drop
- Persist identifiers before checkout redirect
- Send purchase from payment-complete webhook
Flow
Reliable CV Flow
Read browser identifiers
_ga etc.
Persist before checkout handoff
Cookie Bridging
Receive payment-complete webhook
orders/paid
Send purchase via server
GA4 MP
Learn More
The implementation is split into three focused articles. Reading in this order helps connect architecture decisions to practical execution.
Why Conversion Tracking Breaks in Headless Setups
Clarifies where tracking drops in headless boundaries and why purchase data gets lost.
Bridging Cookies Before Checkout Handoff
Covers identifier handoff patterns and practical safeguards such as fail-open behavior and key allowlists.
Sending purchase via orders/paid Webhook and GA4 Measurement Protocol
Explains server-side purchase delivery, deduplication strategy, and monitoring essentials.