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 

[HrishikeshKagne]

Hi @test1234567 ,

Blank UI / .mboxDefault - That CSS hides default content until Target responds. If Target call is slow, you’ll see blank space. Best practice: remove visibility:hidden and use opacity:0 + fade-in, or adjust Target library config (globalMboxAutoCreate, timeout) so default content shows faster.

_cq_.resolvedSegments > 256 chars - This usually happens when too many segments are resolved (nested/overlapping). Even with 2 audiences, AEM may be pushing all eligible segments. Fix: simplify your segment rules, reduce inheritance, or disable passing _cq_.resolvedSegments if not needed.

Custom audience with cookie - No extra mbox call needed; Target evaluates audience on the initial page request if the cookie is available. Just ensure your cookie is set before Target fires.

tweak .mboxDefault handling to avoid blank UI, reduce/simplify segments to stay under 256 chars, and rely on the initial Target call (no extra mbox) if your audience data is ready at load.

[test1234567]

Thank you for your expedited reply and all your valuable inputs.

Regarding your recommendation:
**"Fix: simplify your segment rules, reduce inheritance, or disable passing _cq_.resolvedSegments if not needed."**

Currently, I am only using very simple browser type rules. Could you please provide more details on what is meant by "reduce inheritance"? What could be the impact if we disable inheritance?

Also, if we disable sending `_cq_.resolvedSegments` to Target, would that cause any issues with loading the targeted content? If so, what configuration changes would we need to make to ensure targeted content loads correctly?

For the custom audience based on cookie logic:
If the cookie is not available immediately during the page load or Target API call, do we need to make a specific mbox call to notify Target, so that the content gets updated once the cookie is set and a response is received?

Thanks again for your insights!