ÃÛ¶¹ÊÓƵ

DocumentationTargetTarget Developer Guide

ÃÛ¶¹ÊÓƵ Analytics for Target (A4T) logging in the Experience Platform Web SDK

Last update: Mon Aug 11 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Developer

When using ÃÛ¶¹ÊÓƵ Target for personalization, you can choose which system you want to use for performance measurement. Each Target activity allows you to select between Target reporting and ÃÛ¶¹ÊÓƵ Analytics reporting.

If you are using Analytics reporting, Target has to communicate the following to Analytics:

  • Which Target activity your visitors have entered
  • Which experience they have seen
  • Which conversion has been reached

The ÃÛ¶¹ÊÓƵ Experience Platform Web SDK supports two types of Analytics logging for Analytics for Target (A4T) use cases:

Logging method
Description
Server-side Analytics logging
All Analytics hits sent through the Edge Network are augmented with Target details on the server side, without having to go through the hit stitching process.
Client-side Analytics logging
Target data is returned on the client side, allowing you to manually augment and send data to Analytics using the Data Insertion API.

The logging method is determined by whether you have ÃÛ¶¹ÊÓƵ Analytics enabled on your configured datastream:

Logging method decision flow

Next steps

This document provided a brief introduction to the different logging methods for A4T data in the Web SDK. For more detailed information on each of these methods, refer to the following documentation:

recommendation-more-help
6906415f-169c-422b-89d3-7118e147c4e3