Does anyone know if Target is able to change the experience on the page when the visitor gets qualified for the targeted audience after an on-page event?
Scenario: a visitor comes to a page, clicks a button and gets qualified for Audience XYZ. Right after this an mboxCreate (or a similar method) is called to retrieve the personalised experience and update the mbox content (deliver the experience).
I have tried variety of methods, but Target does not return the new experience even after the page reload.
It’s interesting that if after the qualification for the Audience (button click in the described scenario) the mbox cookie gets deleted, the personalised experience gets delivered as expected.
It seems there may be some sort of server-side “caching” that bar the experience return unless another website page is viewed.