Hi @christammm ,Target automatically cleans up old mbox names, and their parameters if they are not seen again. I think it might be after 2 or 3 weeks of not seeing the mbox it gets cleared.

Hi @enauticss861856,The target-global-mbox was replaced in at.js 2.x with the pageLoad request. They are more or less equivalents. You can see more here: https://docs.adobe.com/content/help/en/target/using/implement-target/client-side/upgrading-from-atjs-1x-to-atjs-20.html#target-global-mbox-is-no-l...

Hi @enauticss861856,The target-global-mbox was replaced in at.js 2.x with the pageLoad request. They are more or less equivalents. You can see more here: https://docs.adobe.com/content/help/en/target/using/implement-target/client-side/upgrading-from-atjs-1x-to-atjs-20.html#target-global-mbox-is-no-l...

Hi @Umamaheswari_Yakkala , If you're talking about a DMP other than Adobe's Audience Manager (which can be integrated with ECID) then you can use the Data Providers method with the at.js. It essentially allows you to fire an API call to the 3rd party data provider then use the segments returned for ...

at.js 2.x uses a slightly different approach for the global page load. You call the pageLoad to trigger the equivalent of the target-global-mbox used in at.js 1.x. See more here in Help:https://docs.adobe.com/content/help/en/target/using/implement-target/client-side/upgrading-from-atjs-1x-to-atjs-20...

Hi muthalagua85543428​,Profile scripts are found in the Target UI here: top nav: Audiences > left nav: Profile ScriptsThat should give you the list of them. Then you can click the 'i" icon or edit pencil icon to see the details.

gabrieleg61567923​ & Sh1ju​,cookieDomains should be set to the explicit subdomain you are using. No wildcard options. This worked for me on your site Sh1ju:window.targetGlobalSettings = {  cookieDomain: "adobe-258915.appspot.com"};-Ryan

Just changing the mbox_name should be sufficient.

Hi Reyhan Sadaka​,There is no way to force the session on the Target server to end. It only ends after 30 minutes of silence. Wiping the mbox cookie (assuming a default 1st party cookie deployment) seems like the most effective solution for you. I would think that ideal time to wipe the cookie would...

I'd say that is up to you. If you dislike it being there and you're not using A4T on that activity then it's harmless to remove with surebee's approach.