Blank UI and mboxDefault Issues

[test1234567]

Hello Community,

I need your input regarding an issue we’re facing. We have an integration in place for AEM Target. We are successfully pulling audiences from Target and using them in AEM to personalize content based on browser type. In the author environment, we’re able to view the respective personalized content as expected.

However, when testing in the publish environment (server), we notice that while the content is being replaced, the UI is often blank. Occasionally, we see the default content instead. Upon investigation, it appears that `.mboxDefault` is hiding the content, even though the content is being replaced for the intended audience:

.mboxDefault {
visibility: hidden;
}

I want to ensure this will not cause issues in higher environments. Has anyone encountered a similar issue, and what steps did you take to resolve it? Please advise.

Additionally, we observed another issue related to `[execute.mboxes[0].profileParameters]`:
**Parameter value for `_cq_.resolvedSegments` exceeds the limit of 256 characters.**

In our scenario, we are only using two audiences for these activities, so it’s unclear why this error is occurring. If you have faced this issue, what did you do to address it?

We also have a scenario where we created a custom audience based on cookie logic. On page load, do we need to make any additional mbox calls to Target to resolve segments and display personalized content, or is this handled as part of the initial page load? If you have any recommendations for handling the loading of personalized content with minimal lag, please share your suggestions.

@HrishikeshKagne