As I understand it, you can only create audiences with it.   Of course you can also create activities with the audiences that write something in your profile. But that is your one request later - and possibly then too late and complicated. Then you can also use e.g. session storage and pass the para...

Hi @enick_88,I know what you want to do. But it would be new to me that you can pass profile parameters from the callback. But I'm happy to be taught better. My understanding is that it is only appended to the target request (payload). At this point the targetPageParamsAll() has already been execute...

Hi @KaterineRiera, In the network tab you currently have a delivery request. Here you can switch to Preview instead of Payload, for example. Then open execute > payLoad > options. Several objects can appear here. You can expand these objects individually and in each case also the ResponseTokes - her...

Hi @KaterineRiera,first of all I would check if Target on Prod is implemented or loaded at all. For this you can e.g. look in the browser dev tools under the network tab - and filter for "delivery" (at.js 2.x) or "mbox" (at.js 1.x) and reload the page. There should be at least one request here. Alte...

Hi @Dirisenapu9,first I would suggest to test this in an "Incognito Window" (close all Incognito Tabs before). In the QA link, if necessary, also specify that all other activities should be displayed only default content.   Alternatively, check if e.g. the at.js is included twice or loaded twice (th...

Hi @gpolkin1, if you have only one location with e.g. the target-global-box. In your case it doesn't matter if you configure your audience in audience or audience refinements. But activities can also be much more complex and then it is very important how the individual audiences are created. It shou...

Hi @apoorv-jain,the rearrange feature sounds like you are doing this in the VEC. Are you just using the feature or are you running custom JavaScript code? To me, most of the time when it works in the VEC or code is executed via the console - but then doesn't work in the with QA link or on PROD - it ...

Hi @jsteinerkotch, I don't know what all you want to exchange or manipulate per target in your case. Maybe it is enough to work with suppressHydrationWarning for the corresponding element.   If a single element’s attribute or text content is unavoidably different between the server and the client (f...

Hi @Arnab3,   What do the social media links look like in your case?   Do your promo banner links have corresponding URL parameters? e.g. domain.com?promo=5 In this case you can create your audience with site page attributes.   Or is it more in the direction of user comes from URL xyz.com/abc to dom...

Hi @most78 exactly, you can realize this via launch. Alternatively, it would also be possible to read values from the localStorage or cookies and pass them to the profile in the targetPageParams function.  https://developer.adobe.com/target/implement/client-side/atjs/atjs-functions/targetpageparams/...