I am sharing Analytics Segments through the Adobe Marketing Cloud Profiles & Audiences Function with Target. Please let me know if I have to implement server-side forwarding or not in order for me to use shared Analytics Segments in Adobe Target in an experience targeting campaign.
server-side forwarding is required for real-time audiences created within the Audience Library interface. Historical Audiences do not require sever-side forwarding to be enabled. However, it's a good idea to enable it anyway so that if you use real-time audiences, it's already in place.
The only time you'd want to be careful enabling it, would be if you are an Audience Manager customer and have deployed DIL code to your page already. If this is the case, you'd want to remove the DIL code when you enabled the server-side forwarding. Otherwise, you'd end up double counting instance metrics within Audience Manager.
Yes, DIL is the page code used by AAM customers. Prior to server-side forwarding, all AAM customer were required to use DIL code to scrape the Analytics object and send data to Analytics. Now, almost all use cases for AAM customers can be accomplished via server-side forwarding (assuming the customer also has Analytics)
Correct, since you are not an AAM customer, you wouldn't have DIL deployed to your page and server-side forwarding would be your only option to use real-time audiences
I'm not sure I understand the question. If you want to use the Audience Library interface, I'd recommend enabling server-side forwarding.
Mostly correct. Without it you are limited to Analytics shared segments via the Analytics segment builder rather than Audience Library. Technically, you don't even need to log into the Audience Library interface if you are sharing segments from Analytics and using them in Target.
I assume enabling server-side forwarding allows session-based targeting (real-time). Without it I can only manipulate content across sessions when using Analytics Segments shared via the Audience Library with Target, right?