Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Flicker Management on Adobe Target with AEP Web SDK

Avatar

Community Advisor

Hello Experts,

 

Hope everyone is doing well.

 

Can you help me understanding more around flicker management with AEP Web SDK? With general deployment of Adobe Target Extension on Adobe Launch, we can setup opacity and pre-hiding script. However, I would like to know about functionality with Web SDK. 

If anyone has already implemented Web SDK, please shed some light around flickers or any challenges you may have seen.

 

Best,

Kishore

1 Accepted Solution

Avatar

Correct answer by
Level 4

@Kishore_Reddy This is available in AEP Web SDK. You can refer here for details - https://experienceleague.adobe.com/docs/experience-platform/edge/personalization/manage-flicker.html.... This is implemented through Web SDK Adobe Launch extension. Documentation says it is the same approach, but in my experience, Web SDK always has its own surprises. We are implementing this week and will keep you posted if any surprises.

View solution in original post

4 Replies

Avatar

Correct answer by
Level 4

@Kishore_Reddy This is available in AEP Web SDK. You can refer here for details - https://experienceleague.adobe.com/docs/experience-platform/edge/personalization/manage-flicker.html.... This is implemented through Web SDK Adobe Launch extension. Documentation says it is the same approach, but in my experience, Web SDK always has its own surprises. We are implementing this week and will keep you posted if any surprises.

Avatar

Community Advisor

Thank you, @pradeep_nextrow 

 

Really appreciate and looking forward to knowing your observations on the implementation & repercussions on performance.

Avatar

Employee

Just wanted to say that the approach to flicker management is the same with Web SDK, but the prehiding snippet itself is different, so that would need to be updated as part of your migration from at.js to Web SDK. It's discussed in this Web SDK tutorial: https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/applications-setup/setup-ta...