Dynamic Yield Scripts

Execution flow

1. Implement api_static and api_dynamic on the page – will render the campaigns on your site
2. Default action for collection injection will add a call to st.dynamicyield.com/st – returns the user and section data and add a call to load our collection script and jquery
3. Add dy-coll-min.js – until Q2 2019 this was used to enable data collection, client-side targeting, and rendering of overlays and notifications. In sites that were created in Dynamic Yield after Q1 2019, the script skips this step, while still maintaining all of its capabilities. If your site was created before this date and you want to remove this jQuery library - contact your Customer Success Manager. 
4. The collection script will fire async-px.dynamicyield.com call to report collection endpoints to the server

Scripts on the page

Experiment scripts

• api_static.js
  1. Loaded from CDN with 1hr  cache
  2. Renders all available experiences and serves variations based on their targeting
  3. Waits for all the dynamic data to load on the page before executing all exepriences. Once loaded it will enable all API calls for the campaigns
  4. 69.8 KB after gzip (last updated: Nov, 2020)
• api_dynamic.js
  • Loaded from CDN with a 5-minute cache
  • Holds all Dynamic Yield campaign settings
  • File size differs depending on the number of active experiences

Asynchronous collection script
The Implementation script will call our server and set up all the user and site data on the page and then proceed to load dy-coll-min.js from the CDN. The script performs all data collection and exposes the on-page API.

Data collection process

Collection operations
When our static collection script executes, we perform the following actions on the page:

1. Init all page listeners
2. Calculate segment definition – custom javascript evaluation per section to define the current page segment
3. Calculate site variables – evaluate site variable javascript code and save the results in a local variable
4. Calculate goal values
5. Init the QManager – handle DY.API calls
6. Log to server leftovers from previous executions
7. Mark and execute FrontPage experiments
8. Add listeners for all monitored units on the page
9. Run detectors to identify current page and user feature set
10. Log page data to the server
11. Log impressions to the server (1 second after dom ready)
12. Log real impressions to the server (every 10 seconds)
13. Log clicks on monitored units (every time a unit is clicked)
14. Log dynamic events – based on DY.API executions

Data collection – network calls

The purpose of these calls is data collection. All of the responses of these requests are empty. These requests do not affect page execution or rendering. 

• async-px.dynamicyield.com/uia – report page and user information
• async-px.dynamicyield.com/imp – report all monitored units on the page – can be executed more then once in single page application and will report the delta
• async-px.dynamicyield.com/rimp – report an array of real impressions
• async-px.dynamicyield.com/dpx – report dynamic event call and properties
• async-px.dynamicyield.com/var (ri,c) – report variation impression (ri) and variation click (c)
• async-px.dynamicyield.com/id – identify user with uid and uid type – required for omni channel
• async-px.dynamicyield.com/rcomEvent – client side rcom interactions – JSON with PRIMP, WRIMP, CLICK data
• async-px.dynamicyield.com/batch - a batch request containing impressions, decisions, and other required internal Dynamic Yield reports.