How at.js works

Target system diagram showing the flow of calls and information sent or collected for an auto-created global mbox using at.js.

In the Target implementation illustrated below, the following Experience Cloud solutions are implemented: Analytics, Target, and Audience Management. In addition, the following Experience Cloud core services are implemented: Dynamic Tag Management (Activation), Audiences, and Visitor ID Service.

Call Description Call Description

Call returns the Experience Cloud ID (MCID) if the user is authenticated; another call syncs the customer ID.

The at.js library loads synchronously and hides the document body.

A global mbox request is made including all configured parameters, MCID, SDID, and customer ID (optional).

Profile scripts execute and then feed into the Profile Store. The Store requests qualified audiences from the Audience Library (for example, audiences shared from Adobe Analytics, Audience Management, etc.).

Customer attributes are sent to the Profile Store in a batch process.

Based on the URL, mbox parameters, and profile data, Target decides which activities and experiences to return to the visitor.

Targeted content is sent back to page, optionally including profile values for additional personalization.

The experience is revealed as quickly as possible without flicker of default content.

Analytics data is sent to 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 Analytics for Target (A4T) reports.