4. If at.js has this code, What code does the Target server have? at.js is a client side of target server so at.js communicate with server to get all information/offers or submit information to server, target server is responsible to process all the request from at.js
5. Where are MBoxes created? On the specific web sites, where we want personalization from target correct? in your website, yes
6. So, in cases where those sites are developed by another agency, we will just offer the mbox code to the agency and it will be their responsibility to include it on the pages correct? TYPICALLY. Yes and No, you may have to deploy it using DTM on their websites.
7. Assuming that including Mbox code was included in the web site pages, from target side what should we perform, for the MBox functionality? Mbox is just a placeholder, which will display the offer/recommendation from target server; which you have to configure in target.
2. at.js resides on the client and helps us to connect with target server, as it has target reference insided? Yes, it's loaded just like mbox.js but theat.js library also includes the components that were included in target.js, so there is no longer a call to target.js.
3. What else is the purpose of at.js?
How do we know how many at.js files are required for an implementation? it's like a js library so you need to load this once for your page.
5. Where does global MBox.js reside? On client or server? there is no global MBox.js; global mbox is like a separate js function.
7. How do we know how many Global Mbox.js files are required for an implementation? there can be one global mbox on one page.
Yes, The at.js library is a new implementation library for Adobe Target designed for both typical web implementations and single-page applications. The at.js library offers several improvements over the mbox.js library, including: