Hi David,Glad you were able to resolve the problems you were having with the Experience Composer in your environment.  at.js v0.9.1 seems very stable and I haven't heard of any issues with it (I work closely with the engineers developing it).  IMO, it is much better than mbox.js.  We are working on ...

Yes, that is not a supported way to load DTM and will not let you add Target correctly.  You need to use the embed code provided by the DTM interface which will load the library synchronously and thus allow you to load Target synchronously.  This is necessary to manage flicker appropriately.

Is there a URL we can look at?  It sounds like something in the chain of operations loading asynchonously which shouldn't be.  Are you loading the main DTM library correctly using the exact code copied from the UI?  Or is someone trying to load DTM asynchronously?

Ok, good luck to you!  I would really encourage you to drop the legacy integration and move to A4T.  Not only are the capabilities much better with the integration, but it would allow you to upgrade to at.js.  Since A4T uses server side calls from Target to Analytics, you don't have to be as concern...

Hi Morten,How do I know the mboxCurrent error is associated with the legacy integration?  If you look in your mbox response you will see the integration response plugin code--note the use of mboxCurrent:<script type=\"text/javascript\">\r\n/*T&T to SiteCat v4 ==>Response Plugin*/\r\nwindow.s_tnt=win...

Hi Ridder,I don't see the mbox div getting written to the DOM at all.  Maybe React's virtual dom doesn't allow it?  Try at.js--which doesn't add a div to the DOM for the global mbox to work--and let us know if you get better results.Daniel

Julien,So you added parameters to your global mbox and now you want to remove them?  How did you add them--via the DTM UI or with your own custom code?  I would just  remove the changes you made to add them in the first place.  You don't need to create another mbox.

Ridder,I see you are using mbox.js.  You should consider using our new library at.js.  It's in First Look status right now and is scheduled for release later this month.  You can download it now via API (search Help for at.js).  We are developing extensions for at.js to tie into different SPA framew...

Morten,You should submit this to client care to have the engineering team take a look at this.

Hi Morten,Is your test rearranging the elements in your top navigation?  I do see some flicker if i stare at that portion of the page.A few side notes:You are using the legacy T&T-SC integration which is not supported with at.js.  You will see an error in your browser console "mboxCurrent is not def...