We have a secure account area for visitors signed up to our business, and within that interface we have multiple mboxes hosting BAU messages and various third party advertisements.
The content of these individual mboxes are managed by different teams who need access to publish only in those particular areas.
Theoretically I don't see why we couldn't pass different at_property parameters at an mbox level rather than in the 'global' via targetPageParams(). We already use getOffer() and applyOffer() for those mboxes, so I figure we could pass this new param along with all others, and change the value according to the correct property.
My concern is that this involves a single 'page' (this is an SPA) having multiple mboxes , and therefore Property tokens, associated with it. Would there be issues when configuring activities and attempting to set them live for these individual mboxes with bespoke permission levels?
Does anyone have any experience with this use case? Are there any potential issues we would need to avoid?
As an additional: Can a single mbox have multiple at_property values assigned to it?
