[bug]: Object Data Missing queryID Leading To Events Not being Forwarded On Purchase

[JordanMoran]

Description

When creating a "PurchasedObjectIDs" event the ObjectData should contain the querryID parameter. This is currently causing issues in algolia, where events are not currently being sent to some services correctly (image below). The "AddedToCartObjectIDsAfterSearch" event correctly has the queryId parameter at the higher level but shares the same ObjectData implementation.

Screen shot from the algolia event debugger:

javascript comparison (https://www.algolia.com/doc/api-reference/api-methods/purchased-object-ids-after-search/):
aa('purchasedObjectIDsAfterSearch', { userToken: 'anonymous-123456', // required for Node.js authenticatedUserToken: 'user-123456', eventName: 'your_event_name', index: 'your_index_name', objectIDs: ['objectID-1', 'objectID-2'], objectData: [ { queryID: 'queryID-1', <- missing price: 19.99, discount: 3.99, quantity: 3 }, // This item was purchased as the result of a query { price: 59.99, discount: 10, quantity: 2 } // This item isn't associated with a query and won't be included in revenue analytics ], value: 179.95, currency: 'USD' });

Client

Insights

Version

7.25.0

Relevant log output

[millotp]

Hello @JordanMoran,

Did you mean to use PurchasedObjectIDsAfterSearch instead of PurchasedObjectIDs ? This one has queryID in the objectData

[JordanMoran]

Hi @millotp,

This is a complete oversite on my behalf!

Thank you for the speedy response we have now got this issue fixed.