How to manage client side implementation when all of our code is server-side rendered | Community
Skip to main content
G
Germedin1
August 9, 2023
Question

How to manage client side implementation when all of our code is server-side rendered

  • August 9, 2023
  • 2 replies
  • 1018 views

Hi All,

I'm currently working on various A/B tests through Adobe Target. Our client uses AEM and Nuxt to build multi-brand pages. The thing is, my team has only access to Adobe Target VEC, so basically I'm facing some issues when trying to conciliate client side code (usually custom code or regular VEC insertions, for example) with static-site and server-side rendered content. Since Adobe Target is being loaded after the process of hidration it is difficult to manage some requirements, specifically when I have to make changes to the logic or so.

So, I'm wondering if any of you has the same issue, if so do u have any advice? I'm struggling a lot with this. Specially, because I'm using a lot of async code.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    J
    JacobTo1
    Level 4
    August 17, 2023

    Hi @germedin1 

    I've experienced similar challenges in the past..

    Given your site is static/server rendered, is your main issue with flicker?
    Where you see the original page before the target offer is applied on page load? (given your async code)

    Also can you share some more detail on the way you are using Target, is it at.js? 2.x? Offers applied on pageLoad or via triggerView?

    Thanks,

    Jacob

      maccg12
      maccg12
      Level 3
      September 17, 2024

      I'd love to know how you dealt with this or if someone can suggest best practices with server side rendered content and Adobe Target.

      Terms & ConditionsAccessibility statement

      Loading footer...