Interakt’s WhatsApp API is already sending plenty of lead-submission events to my number, yet the numbers Google Ads reports don’t line up. A custom event tag was added through Google Tag Manager and it fires, but the figures that hit both Google Ads and Google Analytics are clearly wrong—conversion values in particular make no sense. The job is straightforward: unravel why the data coming from Interakt ends up distorted in Google Ads, then rebuild the tracking so every lead-submission event reflects accurately across Google Ads, Google Analytics, and—if it helps troubleshooting—GTM’s debug mode. What’s in place • Interakt WhatsApp API generating leads • GTM container with a dedicated event tag already firing • Google Ads conversion action for lead submissions Where it falls short • Incorrect conversion values showing in Google Ads reports • Mismatch between what Interakt logs and what Analytics/Ads receive Your task 1. Diagnose the data path end to end—from the Interakt webhook payload through GTM to Google Ads. 2. Correct the tagging or parameter mapping so each lead event carries the right value and no duplicates sneak in. 3. Test thoroughly (real and test leads) until the numbers inside Google Ads and GA align with the actual WhatsApp leads. 4. Deliver concise documentation of the steps, any custom scripts, and how to maintain the setup. Acceptance criteria • Lead submission counts and values in Google Ads and GA4 are within 5 % of Interakt logs for a 7-day sample. • No duplicate or missing conversions during that window. • All changes live inside my existing GTM container, optionally augmented with server-side tagging if that proves the cleanest fix. Hands-on familiarity with Interakt, Google Tag Manager, Google Ads conversion tracking, and GA4 is essential; please come ready to jump straight into debugging and implementation.