If possible, I would recommend using the at.js 2.x library and using a triggerView() to apply changes once the dynamic content has been rendered.
The other benefit of this approach is your offers will be "prefetched" on the initial page load.
These docos have more detail:
Target v2 Launch Extensio...
I've actually been having a think about this very same use case myself recently..
As far as I'm aware Target OOTB Popularity models only support aggregated most viewed/top sellers via Target Data Source (i.e. can't do breakdowns based on `orderConfirmMbox` attributes)
If you al...
If you wanted to sanity check the recommendation results from a "popularity" based Criteria I would suggest
"Download data" from the Recommendations Activity - this will download a .csv with the back end data from your Criteria.In Analytics Workspace, create a Freeform Tabl...
I created a test Recommendations Criteria (HTML Design was disabled), and checked the response from the Delivery API.
It shows me the same output - content type = html
You will need to parse the response escaped string into actual JSON, process to do this will vary depending ...
Yes exactly, if you create a new audience within Target and add the "Time Frame" Attribute it will show you the Time Zone that the audience will be saved with.
In your case, I would expect it to pick up the new Non-DST time.
Sounds like you are using the Visual Experience Composer (VEC) so what I was saying about "mboxes" isn't applicable to you as this relates to the Form Based Composer.
As mentioned by some others on this thread.. if you have created 2 XT Activities with the VEC that both manipulat...
I've experienced the same issue in the past..
Based on my experience it seems that the time zone offset is fixed at the point in time you saved the audience and won't dynamically update.
So you would need to have an audience that caters for DST and Non-DST time.
Assuming both of your Activities are for the same mbox in the form based composer (or component in the VEC); then a visitor will only ever see XT Activity A as it has "All Visitors" as the audience with a higher priority than XT Activity B.
Having Adobe Target implemented does not natively include the ability to trigger a lightbox pop-up, you would need to implement a 3rd Party Library (plenty available if you google) to enable lightbox pop-up functionality - assuming your website doesn't have this functionality already.
It looks like your delivery api mbox response is coming through without issue (and you are able to see the mbox trace).
The response code NO_CONTENT indicates the issue most likely lies with your Recommendations Criteria.
I would review your criteria and maybe use a basic one l...