I was wondering if I can get some clarity on this entity attribute?
For whatever reason back in the day, we were firing two mbox calls on our product detail pages with the exact same entity attributes, but one call included entity.event.detailsOnly (set to true), and the other did not. The previous people that set up Launch and Target have moved on and I don't have context on why we had two nearly identical mbox calls on product detail pages.
I'm seeing if I can clean this up and only keep one of the mbox calls. But I'm wondering if I should keep entity.event.detailsOnly or remove it.
Here is what the documentation states:
In the examples below, the first mbox call updates the catalog and behavioral data. The second mbox call updates only the catalog.
mboxCreate('myMbox', 'profile.geo.city = new york', 'profile.geo.state = new york', 'entity.id = 123', 'entity.inventory = 4')
mboxCreate('myMbox', 'profile.geo.city = new york', 'profile.geo.state = new york', 'entity.id = 123', 'entity.inventory = 4' 'entity.event.detailsOnly = true')
I'm not sure whether I should keep it and have it set to true, or remove it. Can somebody clarify this?
On a side note, for recommendation keys like "Current Item", does Target rely on a page having entity.id passed? And for "Current Category", is it looking for entity.categoryId?