Preview link is breaking but on Visual Experience Composer | Adobe Higher Education
Skip to main content
M
Moumita
September 19, 2024
Risolto

Preview link is breaking but on Visual Experience Composer

  • September 19, 2024
  • 1 risposta
  • 711 visualizzazioni

Hi,

I am trying to create a Experience Targeting (XT) Activity where; Users never been to a specific site section (Such as logged in experience) will see the Default landing page. But users who have been to that site section will see a different layout of the page. 


What I did: 
First I created the segments 

- I created and published a segment on Adobe Analytics 'not-visited ABC (Visitor level)' 

- I created and published a segment on Adobe Analytics 'visited ABC (Visitor level)' 

 

In Target

- I created a Experience Targeting (XT) activity where;

> 'not-visited ABC (Visitor level)' for Default Landing page (Exp A)

> 'visited ABC (Visitor level)' for New version of the page (Exp B)

> All visitor for control experience

(Since, visitors will see experiences in order, from top to bottom)

How I created the New version of the page for Exp B?
-The stakeholder gave me a preview link of the page and I created different offers using the HTML 
- one for the content banner and another for the main content
- Using Visual Experience Composer, I replaced the content offers

What issue I am facing?:
-On Visual Experience Composer the Exp B is looking all find but when I am trying out the Preview link the page sometime appears but most of the time it break. Nothing comes up on the screen and keep loading and after some time I get error message saying "Page is not responsive - exit or wait)"

- I try with different browsers all giving same issue. 

Can anyone please help us building the activity please? It's a high priority case for our business at this moment.

Thanks, 
Moumita


 

Questo argomento è stato chiuso alle risposte.
Migliore risposta di Pankaj_Sabharwal

Hey @moumita 

 

Ensure that your Adobe Analytics segments visited and not-visited are properly integrated with Adobe Target. The order in which you arrange the segments in the XT activity is critical, as users are evaluated from top to bottom. Set up the targeting as follows:

 

  • Visited ABC Segment: Experience B (new version).
  • Non-Visited ABC Segment: Experience A (default page).
  • All Visitors: Control experience.

 

The page may contain JavaScript or dynamic content that conflicts with the modifications made by Adobe Target. This can result in issues, such as layout or functionality errors. 

Additionally, conflicts between the HTML used in your offers and the site’s native CSS/JS could be causing these issues. While the Visual Experience Composer (VEC) may not display these conflicts during preview, they can lead to broken layouts or functionality in actual scenarios.

Action Plan:

  • Ensure that cookies, session storage, or local caches aren't interfering with segment evaluation or page behavior.
  • Test the setup in incognito mode or with cleared cookies to rule out caching issues.
  • Test the new layout in a staging environment or use browser developer tools to check for conflicts.
  • Instead of relying on the Visual Experience Composer (VEC), manually inject custom code (HTML/CSS/JS) to have better control over the modifications.
  • Use the browser console to check for errors, such as failed JavaScript execution, missing resources, or CSS conflicts. You can also add debugging statements to pinpoint where your code might be breaking.
  • From my experience, after repeatedly editing an A/B test to check if the new variant works, it often fails to appear. However, creating a replica of the same test  resolved the issue for me, running smoothly thereafter.

 

Hope this helps.

Thanks

1 risposta

P
Pankaj_SabharwalRisposta
Level 5
September 25, 2024

Hey @moumita 

 

Ensure that your Adobe Analytics segments visited and not-visited are properly integrated with Adobe Target. The order in which you arrange the segments in the XT activity is critical, as users are evaluated from top to bottom. Set up the targeting as follows:

 

  • Visited ABC Segment: Experience B (new version).
  • Non-Visited ABC Segment: Experience A (default page).
  • All Visitors: Control experience.

 

The page may contain JavaScript or dynamic content that conflicts with the modifications made by Adobe Target. This can result in issues, such as layout or functionality errors. 

Additionally, conflicts between the HTML used in your offers and the site’s native CSS/JS could be causing these issues. While the Visual Experience Composer (VEC) may not display these conflicts during preview, they can lead to broken layouts or functionality in actual scenarios.

Action Plan:

  • Ensure that cookies, session storage, or local caches aren't interfering with segment evaluation or page behavior.
  • Test the setup in incognito mode or with cleared cookies to rule out caching issues.
  • Test the new layout in a staging environment or use browser developer tools to check for conflicts.
  • Instead of relying on the Visual Experience Composer (VEC), manually inject custom code (HTML/CSS/JS) to have better control over the modifications.
  • Use the browser console to check for errors, such as failed JavaScript execution, missing resources, or CSS conflicts. You can also add debugging statements to pinpoint where your code might be breaking.
  • From my experience, after repeatedly editing an A/B test to check if the new variant works, it often fails to appear. However, creating a replica of the same test  resolved the issue for me, running smoothly thereafter.

 

Hope this helps.

Thanks

    M
    MoumitaAutore
    September 26, 2024

    Hi @pankaj_sabharwal 

    Thanks for the details. 

    We figured out another reason that is causing this issue for us was the older version of target we were using.
    I will be using the the order you mentioned for the XT activity. 

    Thanks for the Actions plan. We will be mindful as we go. 

     

    Thanks,
    Moumita

    Termini e CondizioniAccessibility statement

    Loading footer...