Meta Conversion API (CAPI) & Server-Side Tracking Expert

We run a SaaS product on a subscription + free-trial model and advertise on Meta. We need a specialist to build accurate, deduplicated event tracking across both the browser (Meta Pixel) and the server (Conversions API), so our Meta ad optimization gets near-100% event coverage with high Event Match Quality (EMQ). Some conversion events happen with no browser session (subscription payments confirmed by Stripe days later). Those must fire server-side from Stripe webhooks with the correct user-match data attached. This is **not** a basic Pixel installation. I need someone who understands advanced Meta attribution and conversion tracking. --- Website Stack * Frontend: React * Backend: Django (Python) * Payments: Stripe --- Events That Need To Be Tracked Fire on BOTH browser (Pixel) + server (CAPI) — triggered on page load / URL / button action, deduplicated by a shared event_id: * PageView * ViewContent * CompleteRegistration * AddPaymentInfo * InitiateCheckout * StartTrial *CancelTrial *CancelSubscription *Subscribe *Purchase These events should be sent from both the browser and the server with proper deduplication. --- ### Stripe Webhook Events These events must be tracked from Stripe webhooks: * Subscribe (Note: which confirms 3-day later after trial ends) * PaymentFailed Subscribe can happen in two different ways: 1. Customer directly purchases the Premium Plus plan. 2. Customer starts a free trial, and after the 3-day trial ends, Stripe successfully charges the customer. Both should trigger the Subscribe event, but with the correct values depending on the purchase type. --- ## What I Expect I want someone who can recommend and implement the **best architecture**, not simply follow instructions. This includes: * Choosing when browser events should fire * Choosing when server events should fire * Implementing proper event deduplication * Maximizing Event Match Quality * Capturing and storing identifiers such as: * fbclid * fbc * fbp * external_id * event_id * Ensuring conversions are attributed as accurately as possible inside Meta Ads Manager * Preventing duplicate events * Following Meta's latest best practices --- Recommend your approach : Before we start, tell us the architecture you'd use (e.g. custom CAPI calls from Django + Stripe webhook handlers, a GTM server-side container, or a tool like Stape) and why it's the best fit for our stack. --- ## To Apply Please include: * Similar Meta CAPI projects you've completed * Your recommended tracking architecture * Your experience with React, Django, Stripe, GTM, and Meta Conversion API * How you normally achieve high event accuracy * Any suggestions you already have after reading this project description Only apply if you have extensive experience with Meta Conversion API and advanced conversion tracking. I'm looking for an expert, not someone learning CAPI.