Event Forwading Error Debugging

[TylerKrause]

Hey there! 

We just launched a new campaign with event forwading. I tested the body of the event that I was going to be sending over thoroughly to ensure that it is correct, but when I actually published it, I'm seeing a 1% error rate.

Of course 99% success is great - but I'm trying to diagnose what is wrong with these events to update my code and I'm not sure where to look to identify the issue. I've looked in the monitoring UI and all I get back is a 400 bad request, and my destination platform does not provide any useful feedback for what went wrong.

Has anyone else ran into this issue? How did you diagnose the problem?

Appreciate any insight here!

[Asheesh_Pandey]

@TylerKrause  I’d start by checking if the errors are only happening for a specific audience, device type, or traffic source. Also, test your data for unusual cases, like missing values, special characters, or very long text fields. And lastly if you’re using identityMap, make sure its structure exactly follows what Adobe Experience Platform expects, in my experience mistakes there are a common reason for errors.

[TylerKrause]

Hey Asheesh - how would you go about testing this in event forwarding?

[Asheesh_Pandey]

Do you have access to Monitoring tab in the Data Collection UI? that allows you to monitor usage patterns, errors, and compute time. If you don't find details can reach out to care team to give you more details.