Urgent: Still battling conversion discrepancies on Impact.com – is anyone else seeing post-back URL issues?

Okay, I'm absolutely tearing my hair out over here. Following up on the previous thread about random conversion drops with Impact.com – we are still battling these infuriating discrepancies, and honestly, it's getting worse. What started as occasional drops has now turned into a consistent headache, severely impacting our affiliate tracking data and our ability to accurately compensate partners. After countless hours of debugging, cross-referencing, and pulling data from every possible source, we've narrowed down the primary suspect to what seems like a severe issue with our post-back URL implementation, or rather, Impact.com's reception of it.

Despite rigorously checking and even re-implementing the post-back URL from scratch, we're seeing significant conversion discrepancies. It feels like the post-back isn't firing consistently or, more frustratingly, isn't being recorded correctly by Impact on their end, even when our server logs clearly show it being sent successfully with all the correct parameters. We've gone through our server logs line by line, compared data against our internal analytics, verified every single parameter in the post-back URL against Impact's documentation, and everything appears correct on our side. The cid is there, the amount is correct, the eventID is unique – yet, the numbers just don't add up on the Impact dashboard.

Has anyone else experienced these specific post-back URL related conversion discrepancies with Impact.com recently? It's driving us insane. We're desperate for any insights, any non-obvious solutions, or even just workarounds you might have discovered. Are there any obscure settings or common pitfalls we might be missing, particularly concerning how Impact processes these post-backs? This is crucial for our affiliate program's integrity and our reporting. Any help would be a lifesaver right now. Thanks in advance!