Peacock ad delivery issues: SDK?

Hey everyone,

• Context: Following up on the previous thread about zero spend on Peacock campaigns post-approval. While the spend issue seems resolved for some, I'm now facing a more granular, persistent problem related to Peacock ad delivery issues that points to potential SDK or tracking integration failures.
• Problem Description: My analytics dashboard shows a significant discrepancy between reported impressions on the Peacock platform and actual events logged by our first-party ad server and attribution provider. Specifically, impression and click pings are either not firing reliably or are being blocked/mismatched on the client-side. This suggests the ad creative is being served, but the tracking mechanisms aren't registering correctly, leading to zero measurable impact despite reported spend.
• Troubleshooting Steps Taken:
  • Verified VAST/VPAID tags are compliant and validated through various ad validators.
  • Inspected network traffic during test impressions on a CTV device (Roku/Fire TV) using proxy tools.
  • Confirmed our attribution SDK (e.g., AppsFlyer/Adjust) is correctly initialized and listening for ad events.
  • Checked server-side impression pixel logs for incoming requests – seeing very few, almost negligible, compared to Peacock's reported volume.
  • Cross-referenced Peacock ad delivery issues documentation for any recent changes to their tracking requirements or SDK versions.
• Observed Technical Output: During local device testing, I'm seeing strange timeouts or malformed requests when the ad attempts to call our tracking pixels. Here's a snippet from a proxy log:

  [2024-07-26 10:34:12.123] [ERROR] [AdSDK] Tracking URL failed: https://track.mycompany.com/imp?id=XYZ123...
  [2024-07-26 10:34:12.124] [DEBUG] [AdSDK] Response Status: 0 (CORS/Network Error)
  [2024-07-26 10:34:12.125] [WARN] [PeacockPlayer] Ad event 'impression' not fully tracked.
  [2024-07-26 10:34:12.500] [INFO] [AdPlayback] Ad completed playback.

  This Response Status: 0 is particularly concerning as it often points to a browser/client-side blocking issue (like CORS) or a network-level failure specific to the CTV environment.
• Specific Questions:
  • Has anyone else experienced Peacock ad delivery issues where the ad plays but tracking pixels fail to fire or return generic network errors?
  • Are there specific CORS headers or security policies unique to Peacock's CTV player environment that might be blocking external tracking requests?
  • Any suggestions for debugging Response Status: 0 errors in a CTV context, particularly for Peacock?
  • Could this be related to a specific version of the Peacock app/SDK on certain devices?
• Closing Hook: Help a brother out please... This is really messing with our attribution models.