Meta Conversions API Setup for GoHighLevel

I have a GoHighLevel funnel that needs server-side Meta conversion tracking wired up. The implementation is already written and specified. I need someone to deploy it, connect it, and prove it works. This is not a "design me a tracking strategy" job. The architecture, the event schema, and the data-handling rules are decided and documented. I'm hiring for correct execution and verification. What you're given A finished Cloudflare Worker (JavaScript) that receives a webhook and posts to the Meta Conversions API Its config file A browser-side snippet for the funnel's head tracking code A written runbook covering the event schema, the parameter allowlist, the deduplication scheme, and the build sequence Scope of work Deploy the supplied Cloudflare Worker to my Cloudflare account, with the access token and shared secret set as encrypted secrets (not in source) Create three custom fields in GoHighLevel and add them as hidden fields on two forms Build two GoHighLevel workflows, each firing a webhook POST to the Worker with specified fields and a custom auth header Install the supplied head-code snippet on the funnel and confirm the path matching is correct for my URLs Remove one legacy Conversions API configuration that points at a retired pixel Verify end to end using Meta's Test Events tool — confirm events arrive, confirm the received parameter list matches the spec exactly with nothing extra, and confirm browser and server events deduplicate rather than double-count A short Loom or written summary of what you did and anything you'd flag Hard constraints — please read before bidding My ad account is in a Meta restricted category. The unusual choices in this build are deliberate and were made for that reason. They are not oversights, and bids that propose "improving" them will not be considered. Do not change the event names. They are intentionally arbitrary and carry no semantic meaning. Do not add customer parameters beyond the supplied allowlist. Specifically: no first name, last name, phone, date of birth, gender, or geographic fields. I know this costs match quality. That is the trade being made. Do not send product names or category strings in any content field. Do not create URL-based custom conversions as a substitute for real events. Do not rewrite the Worker or swap it for a third-party CAPI tool (Stape, sGTM, a GHL marketplace app). If you think something in it is wrong, tell me and I'll decide. If those constraints seem strange to you, that's a sign this isn't your job — and no hard feelings. Access I'll provide GoHighLevel and Cloudflare access after hire. The Meta access token I will generate and hand over directly. I'm not sharing credentials in Upwork messages.