Meta CAPI + Server-Side GTM Expert: Fix Conversions and Build Full Lead Tracking (GoHighLevel)

I run a marketing agency and need an experienced tracking specialist to fix a current Meta Conversions API issue and tighten up our lead tracking on one of our client accounts. The problem. Meta is overcounting our leads, reporting significantly more conversions than the actual lead volume in our CRM. Right now the Lead event fires on a thank-you page when the form is submitted, which I believe is firing repeatedly on refresh or revisit and double-counting against the CAPI send. I want this fixed and rebuilt properly. Our stack: - GoHighLevel for forms and CRM - Google Tag Manager web container - Server-side GTM container running on Google Cloud - Meta Pixel plus Conversions API - Meta Ads as the traffic source What I need from you: - Diagnose and fix the current overcounting, including event_id deduplication, event_name parity, and firing conditions - Move the Lead event off the thank-you page and fire it server-side from a GHL workflow on form submission, so it fires exactly once per lead and does not depend on browser behavior - Raise our Event Match Quality by sending complete customer information with the event, including the click ID and fbc, plus email and phone normalized and hashed correctly. All of these are already captured on our form - Validate end to end with real test leads and confirm Meta counts reconcile with the CRM You should be able to speak fluently about Pixel and CAPI deduplication, firing conversions server-side from GHL workflows, Event Match Quality and correct hashing of customer information, qualified-lead optimization in Meta, and GHL form and workflow behavior. If those terms are not second nature to you this is not the right project. Start with a short diagnosis and scope. This begins as a defined build, with strong potential for ongoing tracking work across multiple client accounts if it goes well.