I am trying to understand what happens if at.js fails?
My front-end team does not want to put the at.js in the HTML head tag because they are not sure what will happen if the at.js call fails. Will this result in a blank page on the user browser?
How does Adobe Target handle this scenario?
Your experience will not be rendered, but normal default content should still be processed and rendered as expected.
at.js is a library to support your experience, it is absolutely required to be in the header.
The modifications to page content YOU control via the target interface.
as far as i know it is a "blocking script", meaning it has to fully execute before the next script can begin execution, but Adobe, please correct me if i'm wrong. Even then, its a fully tested and QA cycled script, I personally haven't seen it fail or have issues with the library yet on our platform. We are using at.js @ v 1.2.0
Adobe will have to speak on SLA and response times from their servers, but by default content I mean 'the front-end application', NOT Target.
Are you using the akamai hosting or DTM? more often than not, the adobe server response times are a non-issue.
Thank you for replying back.
Assuming that it is a "blocking script" what is the timeout that you have set to get the response back from the Adobe server?
Also, when you say that the default code will be rendered do you mean it will be rendered by Target or will it be rendered by the Front-end code on the website?