Show Menu
TOPICS×

Understanding How Adobe Target's at.js 2.0 Works

at.js 2.0 enhances Adobe Target's support for single page applications (SPA) and integrates with other Experience Cloud solutions. This video and accompanying diagrams explain how everything comes together.

Architecture Diagrams

  1. Call returns Experience Cloud ID (ECID). If user is authenticated, another call syncs the customer ID.
  2. at.js library loads synchronously and hides the document body (at.js can also be loaded asynchronously with an optional pre-hiding snippet implemented on the page)
  3. Page Load request is made including all configured parameters, ECID, SDID and customer ID
  4. Profile scripts execute and feed into the Profile Store. The Store requests qualified audiences from the Audience Library (e.g. audiences shared from Analytics, Audience Manager, etc). Customer Attributes are sent to Profile Store in a batch process.
  5. Based on URL, request parameters, and profile data, Target decides which Activities and Experiences to return to the visitor for the current page and future views
  6. Targeted content sent back to page, optionally including profile values for additional personalization.
    Targeted content on the current page is revealed as quickly as possible without flicker of default content.
    Targeted content for future views of a single-page application is cached in the browser, so it can be instantly applied without an additional server call when the views are triggered. (See the next diagram for triggerView() behavior).
  7. Analytics data sent from the page to the Data Collection Servers
  8. Target data is matched to Analytics data via the SDID and is processed into the Analytics reporting storage. Analytics data can then be viewed in both Analytics and Target via A4T reports.
  1. adobe.target.triggerView() is called in the single-page application
  2. Targeted content for the view is read from the cache
  3. Targeted content is revealed as quickly as possible without flicker of default content
  4. Notification request is sent to the Target Profile Store to count the visitor in the activity and increment metrics
  5. Analytics data is sent from the SPA to the Data Collection Servers
  6. Target data is sent from the Target backend to the Data Collection Servers. Target data is matched to Analytics data via the SDID and is processed into the Analytics reporting storage. Analytics data can then be viewed in both Analytics and Target via A4T reports.