After enabling the Target in our AEM environment, our Backbone created component functionalities (like Click events...) stopped working.
Then, in one of your forum replies, it is mentioned to invoke TNT.createGlobalMbox() method after our backbone file.
We've included the below code at the bottom of our page:
Please help to resolve this issue, as this issue is blocking our work.
You are creating the global mbox at the bottom of the page using their own custom code. I don't think that's the best option. You will get flickering because of this
Also, it is not clear what you mean by 'backbone'. Would advice you to reach out to your point of contact in Adobe Target consulting.
Thanks & Regards
It sounds like you have a Single Page Application, hence the use of Backbone. Single Page Applications are much more complex--mostly because of the flicker-handling needed as per Parit's reply. We developed an new library with SPAs in mind called at.js and this is what we recommend for SPA implementations (https://marketing.adobe.com/resources/help/en_US/target/ov2/c_target-atjs-implementation.h tml). Please note that the TNT.createGlobalMbox() function is not part of at.js and mbox calls on things like view changes in your backbone app will need to be called differently. Again, SPA implementations are a little bit trickier and I echo Parit's suggestion of working closely with your Adobe Target consultant on this project.