Attention: This is not a standard GTM configuration job. Please read the entire description carefully before applying. We are looking for a true debugging expert for an unusual and complex case, after official Google support was unable to help. 1. The Initial Project The original request from the client (a luxury brand) was to implement a complete and modern e-commerce tracking system, with the following requirements: Complete tracking of e-commerce events. Sending data to GA4, Google Ads, Meta (CAPI), TikTok, etc. Server-Side architecture to maximize data quality, with a first-party endpoint. Full GDPR compliance via Google Consent Mode v2, integrated with the Axeptio CMP. 2. Site and Tracking Architecture Website Architecture The site has a complex hybrid/headless architecture: The front-end (www.geraldcharles.com), which includes the homepage, category pages, and product pages, was custom-developed using Storyblok as a headless CMS and Node.js. The entire e-commerce process (cart and checkout) is managed entirely by Shopify and resides on a dedicated subdomain (checkout.geraldcharles.com). Tracking Architecture GTM Server Container: It is hosted on Google Cloud Run and mapped to our own first-party subdomain (gtm.geraldcharles.com) to operate in a first-party context. DNS: The DNS records are managed through GoDaddy. 3. The Client-Side Script (The "Why" of the Complexity) Instead of using the standard GTM snippet, the following advanced loading script is implemented on the site. This choice is not random; it is necessary to correctly implement Google Consent Mode v2, as per official Google guides. The script ensures that the consent state is defined before GTM is loaded, guaranteeing maximum compliance. This is the script currently active on the site: HTML <script> window.axeptioSettings = { clientId: "65fd5c71fc1806e180c803d2", cookiesVersion: "-EN", googleConsentMode: { default: { analytics_storage: "denied", ad_storage: "denied", ad_user_data: "denied", ad_personalization: "denied", wait_for_update: 500 } }, gtmContainer: "GTM-KPCLXBD", gtmBaseUrl: "https://gtm.geraldcharles.com", gtmLoadWithoutConsent: true, autoupdate: true, url_passthrough: true }; </script> <script async src="https://static.axeptio.io/sdk.js"></script> <script> window._axcb = window._axcb || []; window._axcb.push(function(axeptio) { var gtmScript = document.createElement('script'); gtmScript.src = 'https://gtm.geraldcharles.com/gtm.js?id=GTM-KPCLXBD'; gtmScript.async = true; document.head.appendChild(gtmScript); }); </script> 4. The Problem: "The Silent Failure" Despite the architecture being configured according to best practices, the Google Analytics 4 property (G-SXJ7011P4G) is not receiving any data. 5. What We Have Already Done (Our Complete Audit) We have performed an in-depth debug, verifying that: Client-Side: GTM Preview Mode connects, the dataLayer is correct, Tags fire, and network logs confirm that the gtm.js script is loaded with a Status 200 OK from our server. Server-Side: GTM Server Preview Mode receives events, Tags (including GA4) fire, and Cloud Run logs show no errors. GA4-Side: No data filters are active, the stream and api_secret are correct. 6. Our Main Hypothesis We strongly suspect the problem is a Content Security Policy (CSP) or a similar security mechanism on the front-end (Node.js/Storyblok), which is blocking the GTM script's operations after it has loaded correctly. 7. What We Ask of You (The Project) The project is divided into two fixed-price phases: Phase 1 (Audit & Diagnosis): Analyze the entire architecture and produce a clear report that identifies the root cause of the problem. Phase 2 (Resolution): Implement the solution or provide precise technical instructions to our developers to fix the issue and verify the correct data flow into GA4. 8. What We Will Provide to Get You Started Read-only access to GTM (Web and Server) and GA4. The entire conversation history with Google support. A direct communication channel with us and the site's development team. In your proposal, please explicitly specify if you need any other access or information to complete Phase 1. 9. Who We Are Looking For (Required Skills) We are looking for a professional with proven, EXPERT-level experience in: GTM Server-Side. Google Analytics 4 (Measurement Protocol, Debug View). Google Cloud Run for GTM. Headless/Shopify architecture. Essential: Advanced debugging of Content Security Policy (CSP) and script conflicts in modern frameworks (Node.js, Storyblok, etc.). 10. How to Apply Please start your application with the word "SOLVED" and include a brief description of a particularly complex GTM Server-Side debugging case you have resolved in the past.