Target 2.0 VEC issue | Community
Skip to main content
V
vinodh_dinakar2
Level 2
October 29, 2025
Solved

Target 2.0 VEC issue

  • October 29, 2025
  • 1 reply
  • 148 views

Hello All,

 

I have a SPA that has Target 2.0. Here is the user flow and what I am trying to achieve

 

  1. Starting URL is URL_A .  It has 3 views - v1, v2 and v3 that load one after the other based on user actions. 
  2. I am able to navigate to these views within VEC and make changes / add custom code etc - so that is good
  3. on V3 of URL_A, there is a CTA that leads to URL_B view V1. Please note that this is not a page refresh.
  4. On URL_B / view V1, I would like to make a change. So I change to 'Design' mode. What happens is the browser within VEC goes all the way back to URL_A / view V1

The SPA is react js - if that helps. Can you throw light on what is happening here please? Is this an implementation issue ? or an application issue? 

In short, I would like to make changes to multiple views that spans across different urls. But I am unable to. Any help would be highly appreciated.

 

    Best answer by Gokul_Agiwal

    Hi @vinodh_dinakar2 - There are couple of reason 

    In your case both URL_A and URL_B part of same SPA, there might be possibility that AT might not recognize URl_B as new page/View.   AT might have issues to differentiate in views when navigating within SPA.  

     

    So please check in your react app, state change / view (url) change gives a signal to AT so that it detect. try to configure a triggerView() function 

    https://experienceleague.adobe.com/en/docs/target/using/experiences/spa-visual-experience-composer#implementing-adobe-target-views 

     

    Hope this helps. 

    1 reply

    Gokul_Agiwal
    Community Advisor
    Gokul_AgiwalCommunity AdvisorAccepted solution
    Community Advisor
    October 31, 2025

    Hi @vinodh_dinakar2 - There are couple of reason 

    In your case both URL_A and URL_B part of same SPA, there might be possibility that AT might not recognize URl_B as new page/View.   AT might have issues to differentiate in views when navigating within SPA.  

     

    So please check in your react app, state change / view (url) change gives a signal to AT so that it detect. try to configure a triggerView() function 

    https://experienceleague.adobe.com/en/docs/target/using/experiences/spa-visual-experience-composer#implementing-adobe-target-views 

     

    Hope this helps. 

    Terms & ConditionsAccessibility statement

    Loading footer...