Why is the last answer correct? 

We got a request from a customer. Is it possible to send a message directly to customer inbox in the mobile app?

It should be send like this?   <script> targetPageParams = function() { return { // Property token "at_property": "5a0fd9bb-67de-4b5a-0fd7-9cc09f50a58d", // Mbox parameters "pageName": "product detail" }; }; </script>   Do I have to put in the b...

What is the business use-case for that? If multiple business units use's one sandbox in order to levarage sitched profiles however they have different email domains?

Anybody knows anything? 

Using at.js implementation as a value for mbox3rdPartyId we can send crmID or email address and then profiles in Target would be sitched? Or we can send only crmID?targetPageParams = function() { return { "mbox3rdPartyId": "TT8675309" }; };

Could somebody explain me this answer? 

but how to pass first this parameters to global mbox using at.js?var flag=user.get('YourProfileScriptName')||'False';var Pages = ['HomePage', 'CategoryPage', 'ProductPage']; if (Pages.includes(mbox.param('page_name'))) {flag = 'True';}return flag; I assume that these parameters needs to be passed fi...

But do different workspaces have different at.js codes? Or every workspace has the same script but you constrain activities on a property level?I am coming back from different MA/Personalization tools so thats why I am a little bit lost 

According to this implementation pattern: https://experienceleague.adobe.com/en/docs/target-dev/developer/client-side/at-js-implementation/deploy-at-js/implement-target-without-a-tag-managerDoes I need to wrap at.js code like that? Could somebody explain me this in detail?<script src="at.js"></scrip...