When selecting a feature to debug in your Events Debugger, it's normal to see warning messages related to events missing queryID or objectID values, since a number of event types do not include them by design.
Events that are not associated with a search or browse requests will not contain a queryID and will therefore trigger the warning message.
If the warning messages are present, you should check your debugger to confirm which events you are sending. You can safely disregard the warning message if you are sending events that are not expected to include a queryID. Common examples include:
- Filter events (also do not include
objectIDs) -
clickedObjectIDs(not afterSearch) -
convertedObjectIDs(not afterSearch)
These events are typically used to power features such as Personalization and Recommended, and so are valid even without a queryID.
Note: view events do not include a queryID by default and so are not counted toward the total number of events missing a queryID.
In addition to events that do not include a queryID by default, currently only top-level queryIDs are checked - not nested object-level queryIDs. This means those sent in the objectData property of conversion events are also counted toward the total number of events missing a queryID.
These warnings can also be safely ignored your nested objectData queryIDs are correctly implemented within the event payload.
If none of your events fall under the scenarios described above but you're still seeing the warnings, it may indicate an issue. In that case, please contact Support who will be able to help troubleshoot.