Overview: implement Target for client-side web
In a client-side implementation of Adobe Target, Target delivers the experiences associated with an activity directly to the client browser. The browser decides which experience to display and displays it. With a client-side implementation, you can use a WYSIWYG editor, the Visual Experience Composer (VEC), or a non-visual interface, the Form-based Experience Composer, to create your activity and personalization experiences.
To implement Target client-side, you must use one of the following JavaScript libraries:
-
Adobe Experience Platform Web SDK
The Adobe Experience Platform Web SDK lets you interact with the various services in the Adobe Experience Cloud (including Target) through the Adobe Experience Edge Network. If you choose to migrate to the Adobe Experience Platform Web SDK, see What is Adobe Experience Platform Web SDK.
-
Target at.js JavaScript library
The at.js JavaScript library improves page load times for web implementations, improves security, and provides better implementation options for single page applications. If you choose to migrate to at.js, see How At.js Works and Adobe Target Skill Builder: Developer chat, migrate Adobe Target’s mbox.js to at.js.
See Comparing the at.js library to the Web SDK to learn about the differences between the two implementation approaches.