Hi @AshokRa2  Are you using getOffer aplyOffer on client side to deliver target activities? or the Target is implemented using Adobe launch?

Hi @Pravinrams1 , The "decisioning engine not ready" error in Adobe Target typically occurs when the on-device decisioning artifact (rules.json) hasn't been fully downloaded before making a getOffers request. This issue is more prevalent in production environments due to differences in network laten...

Hi @RJBu ,Try below PS, It worked for me -var visitorIp = user.header('x-forwarded-for');return visitorIp;  

Hi @GigiCotruta ,As per my understanding, you cannot return multiple entity IDs as a key. So, it'll only work with single id.

Hi @CWi1 , Adobe Analytics segments are not processed in real-time; there is typically a delay of up to 8 hours. This delay occurs because Analytics segments are historical and require processing time before they can be utilized in Target activities.To achieve real-time personalization in Adobe Targ...

Hi @TammyWo2 , Could you please elaborate more on what do you mean by dynamic content?

Hi @MarinCa , I encountered a similar issue in one of the projects where we implemented recommendations. According to the engineering team, once a multi-value attribute is populated, its type is set to an array in the backend, and it cannot be reverted to a single value (string). They recommended cr...

Hi @rudraWiley ,If 100 people visit the website and 50 of them are assigned to Experience B, they will consistently see Experience B on both Page 1 and Page 2.Similarly, the remaining 50 visitors, who fall under Experience A (default), will always see Experience A on both pages.From a reporting pers...

Hi @rudraWiley In a multipage activity with Experience A and Experience B, both Page A and Page B are included in both experiences. When 50% of users are assigned to Experience B, they will see the Experience B UI on Page A. If they navigate to Page B, they will continue to see the Experience B UI(a...

Hi @bcong In Adobe Target, the Decisioning Method determines where the logic for delivering personalized experiences is executed—either on the client-side (in the user's browser) or on the server-side (on Adobe's servers). This method can be influenced by several factors, even within a client-side i...