OpenAI Pixel Invalid event payload warning!

1

Hi,

We have completed the OpenAI Pixel CAPI using the tag template of Stape. We are seeing an invalid event payload warning for a few events. Is it okay? Or, is there anything we can do to fix that.

Thanks.

image
image2934×1542 240 KB

2

Hi @Hridoy.

To help you, we need to understand what can be wrong with this particular event.

Please:

  • enable the Debug Mode in the tag template;
  • enter preview mode in GTM and go to the website where this event is;
  • in your website tab, open the DevTools on your browser and go to the Console tab;
  • fire this event;
  • check the messages in the DevTools Console that are prefixed with [oaiq]. You’ll probably see one like this [oaiq] validation failed; event dropped when you fire this event.
  • paste the full message(s) here.
    Example:
    [oaiq] validation failed; event dropped 
{
  "command": "measure",
  "issues": [
    "eventProps.type should be \"customer_action\"."
  ],
  "eventName": "registration_completed"
}
1 Like
3

@giovaniortolani I’m experiencing this same issue and followed your guidance. However, the events didn’t fire a validation error in DevTools Console. How can I troubleshoot?

4

Hi @measure, are you experience the same problem with CAPI template? Pixel template? Or both?

My previous answer focused only on the Pixel, but reading the post again I see that the person asked about CAPI.

Unfortunately, as OpenAI Ads is still in Beta, the UI displays only a vague warning message that is of no help.

If the problem is on the Pixel, then that method I described should be sufficient.

If the problem in on the CAPI, then you can do the same exercise:

  • enable Validate Only in the template
  • enable GTM Preview Mode
  • fire the events on your website
  • see if any of the CAPI responses status code is 400. The CAPI endpoint itself returns any problem that it encountered in the request payload, which will help pinpoint the error.

Moreover, if you host on Stape and are on the Pro plan or higher, you can enable Stape Logs. Every request and response that occurred in your sGTM container will be logged, which can be used to find the CAPI requests that are returning the 400 status, and understand what is wrong with the payload.

Last but not least, if the percentage volume of events with this warning is very low when compared to all events sent, I would not worry about it.