Server-Side GTM, Stape, Magento 2 Tracking Specialist – Advanced GA4 & Meta CAPI

I am looking for a highly skilled Tracking Specialist to completely overhaul and configure a reliable, accurate, and fully optimized tracking architecture for a luxury e-commerce brand. CRITICAL REQUIREMENT: You MUST have proven experience implementing advanced tracking within the Magento 2 ecosystem. I have previously hired highly-rated tracking experts whose implementations failed because they applied generic Shopify/WordPress approaches that were incompatible with Magento’s architecture, particularly regarding Content Security Policies (CSP), checkout functionality, and DataLayer structure. Please do not apply unless you have hands-on experience with Magento 2 checkout security, tracking integrations, and third-party extensions. My Tech Stack Platform: Magento 2 (v2.4.8) DataLayer: Magefan GTM Extension Consent Management: Anowave Cookie Consent Mode V2 Server-Side: Stape.io & Google Tag Manager (Web + Server containers) Destinations: GA4 & Meta CAPI Infrastructure: Cloudflare & PayU (3D Secure redirects) The Scope of Work I need a highly accurate, fully compatible tracking system with reliable data transmission between the browser, server-side GTM, Meta, and GA4. Your responsibilities will include: 1. Flawless Deduplication & Routing Fix the current split-routing architecture and establish a consistent event-tracking structure. Browser and server events must use properly synchronized event_id values to ensure reliable deduplication in Meta Events Manager, while maintaining accurate GA4 tracking without duplicate events. 2. Server-Side Cookie Persistence (EMQ) Properly configure the Stape Data Client and cookie handling to ensure identifiers such as _fbp, _fbc, _dcid, and FPIDP are correctly generated, transmitted, mapped, and persisted where applicable, in accordance with Anowave consent settings. Cookie lifetimes should be optimized within browser and privacy restrictions to maximize Event Match Quality (EMQ). 3. Complete Funnel Tracking Ensure all critical upper-funnel and lower-funnel events are accurately tracked, properly structured, and reliably transmitted: session_start, page_view, view_item, add_to_cart, begin_checkout (Meta: InitiateCheckout), add_shipping_info, add_payment_info, and purchase. Ensure the appropriate corresponding events are correctly mapped to Meta CAPI, with consistent event parameters and values. 4. Auto-Mapping & Data Hashing Ensure the Meta CAPI tag correctly handles auto-mapping for dynamic values, currencies, product information, and item arrays, without data loss or incorrect attribution. All available customer identifiers (email, phone, etc.) must be properly normalized and SHA-256 hashed where required before transmission to Meta. Implement reliable event handling to minimize data loss caused by network delays or temporary transmission failures. 5. Magento CSP & Checkout Handling You must understand how Magento 2's Content Security Policy (CSP) can restrict tracking requests, particularly on checkout and order success pages. I have a dedicated Magento backend developer on my team. Your responsibility is to identify and provide the exact domains/endpoints (e.g., scv.mydomain.com) that must be allowlisted through Magento's csp_whitelist.xml, where necessary. 6. Cloudflare Compatibility Ensure the GTM Server container receives the correct visitor IP address (e.g., via CF-Connecting-IP headers) when Cloudflare's proxy (orange cloud) is enabled. Identify any Cloudflare WAF, proxy, or security configurations that could interfere with tracking requests, and recommend appropriate exceptions where necessary. Payment & Quality Assurance Terms I am extremely detail-oriented and expect a thoroughly tested, professional implementation. This is a fixed-price contract, and payment will be released ONLY after the complete implementation has been successfully tested and verified. We will verify that: All critical funnel events are accurately received, properly structured, and consistently reported in GA4 and Meta. Browser and server-side Meta events are correctly matched and deduplicated, without unresolved configuration or deduplication warnings. The purchase event fires reliably and only once per transaction, including orders involving external 3D Secure payment redirects (PayU). Consent settings, cookie persistence, event parameters, and customer identifiers work correctly throughout the entire tracking process. To Apply Please start your proposal by answering these two technical questions: How do you handle Magento 2 CSP restrictions that may block tracking requests or prevent the Purchase event from being transmitted correctly on the success page? How do you ensure that Anowave Cookie Consent settings are correctly communicated to the Stape Data Client so that server-side identifiers and cookies are properly stored and maintained only when consent permits? I am looking for a genuine Magento 2 tracking expert who values precision, reliability, and attention to detail. If you have the required experience and can deliver a thoroughly tested implementation, I look forward to working with you.