Entire A4T section needs to be re-thought and redone

[dhwoolsey]

Issue in ./help/web-sdk/personalization/adobe-target/analytics-logging/overview.md

This entire section of A4T with WebSDK needs some attention. It discusses a client-side and server-side option for capturing A4T data. The server-side version is no longer supported, and when most people read "server-side," they are thinking of an implementation where Target is used server-side and Analytics is used client-side, so many find this page thinking that it is instructions on how to do that integration.

The client-side page discusses how to do a manual implementation where you disable Analytics in the datastream (very bad) and then capture the response from Target and send the data to Analytics via the data insertion API. I'm not sure which customers would ever want to use this approach, but it is far from a standard approach.

Nowadays, the AEP WebSDK does a client-side version of A4T, but it's automatic. The customer doesn't need to do anything specific to set up A4T other than select Analytics as the reporting source when setting up the Target activity.

I would argue that these pages should outline how A4T data is captured in Web SDK implementations today, as well as outline an approach for how to handle non-standard Analytics + Target implementations and still do A4T, such as Server-Side Target + Client-Side Analytics or Server-side Target + Server-side Analytics.

[vfalon]

Thank you for submitting this issue. We will review the documentation and make the necessary updates as quickly as possible. Tracking internally in PLAT-257835.