Default content is blank in Preview/View as Published mode

[test1234567]

Hello,

We're encountering an issue with AEM-Target integration. Once content is targeted based on audience, viewing the page in preview or published mode results in the default content appearing blank—the section is not visible.

Upon investigation, it seems this is happening due to the following class:

<style id="at-makers-style" class="at-flicker-control">
.mboxDefault { visibility: hidden; }
</style>

Should we make any changes to address this issue?

Additionally, regarding permissions: I noticed users in the community have reported that the out-of-the-box groups “target-administrators” and “target-activity-authors” do not provide all necessary permissions. I am considering creating a new group with the required permissions for the following paths: `/content/campaign`, `/etc/cloudservices`, and `/etc/segmentation`. I plan to add the OOTB groups to this new group so that we don’t need to manually update the OOTB groups.

For this implementation, we need to enable Test and Target replication. However, I found that the replication queue is getting blocked frequently. Has anyone faced a similar issue, and what was done to address it?

Thank you!

[HrishikeshKagne]

Hi @test1234567 ,

The blank default content is expected: Target injects .mboxDefault { visibility:hidden; } to avoid flicker. Default content stays hidden until a Target offer loads. Don’t remove it—use Target’s async/at.js config or flicker-control tuning if needed.

For permissions, your plan is right: create a custom group with needed rights on /content/campaign, /etc/cloudservices, /etc/segmentation, then add OOTB groups into it. That’s cleaner than modifying Adobe’s groups.

For the replication queue blocking, common causes are heavy payloads or network issues. Usual fixes: clear stuck items, check agent settings, and use Test and Target replication agent only for what’s required.

flicker CSS is normal, custom group for perms is best, and replication issues need queue tuning/monitoring.

[test1234567]

Thanks for your reply. The actual issue is that when a content author tries to preview the page in "View as Published" mode, the default content is not loading. I’m not sure if the following error is causing this issue.

Can you tell me which dependency we need to add to resolve this?

I have followed the tutorial below, but can you tell me if you have used the same approach or a different one?

I am considering downloading the at.js file from Adobe Target and adding it to AEM as a clientlib to reference it. If I do this, do I still need to follow the steps in the tutorial?

https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/implementing/developing...

Regarding the flickering issue, could you please provide more information about your usage of Target’s async/at.js configuration or any flicker-control tuning you have implemented?