We're using DTM to fetch elements in the DOM of the page and put this in dataelement. To use criteria to show recommended articles based off of the category of the viewed article, I need to pass entity.categoryId to target-global-mbox
I'm using this to pass the categoryId to target-global-mbox
Now, with this, I see that Target has a second call to target-global-mbox with entity.categoryId in it, but my mboxTrace continues to state that Target can't locate a categoryId value.
My reasoning of this problem is that the reco engine only fires on the first target-global-mbox call (where there is no entity.categoryId yet) and is not taking into account the second call (where I send that value).
Two questions for you:
Could this be because the recs criteria doesn't understand the second target-global-mbox call?
How could I make sure the recs engine retrieves the entity.categoryId at the right time?
Can you see the desired/expected behaviour on the 3rd mbox call?
If you want to see the expected behaviour on the 2nd mbox call and you are happy with possible flickering effect (I presume the page is loaded/rendered at the time the 2nd call is sent), then consider replacing the event call with the getOffer/applyOffer call.