You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AMP requests don’t currently have a way to report rejects that happen within the modularity workflow.
When &debug=1 is on the /amp endpoint, right now only ext.debug is supplied on the response. I propose we send the whole seatbid array and other trace info as well – any ORTB that would have been sent to the /auction endpoint should be there in AMP debug mode.
If there are automated tests hitting the debug endpoint and parsing the results, then this would be a breaking change because ext.debug would now be ortb2.ext.debug.
The text was updated successfully, but these errors were encountered:
AMP requests don’t currently have a way to report rejects that happen within the modularity workflow.
When &debug=1 is on the /amp endpoint, right now only
ext.debug
is supplied on the response. I propose we send the whole seatbid array and other trace info as well – any ORTB that would have been sent to the /auction endpoint should be there in AMP debug mode.e.g.
If there are automated tests hitting the debug endpoint and parsing the results, then this would be a breaking change because ext.debug would now be ortb2.ext.debug.
The text was updated successfully, but these errors were encountered: