A/B Testing behind Authentification and Angular routing | Community
Skip to main content
J
jhirahoka
June 30, 2021
Solved

A/B Testing behind Authentification and Angular routing

  • June 30, 2021
  • 1 reply
  • 932 views

Hi guys

 

I'm having some problems when trying to navigate to an authenticated page on Targets VEC when switching to Compose mode.

 

My homepage navigates to an external login page, after the user finishes the login process, it  redirects it back to save the provided token in session storage and redirects to the next step via angular routing. (We are using angular 7)

https://domain.com/#/  -> https://domain2.com/#/auth -> https://domain.com/#/token/xxx-xxxx-xxxxxx -> https://domain.com/#/page1

 

Even though visually my page is rendering https://domain.com/#/page1 the url remains as  https://domain.com/#/token/xxx-xxxx-xxxxxx so when I switch to Compose mode it fails because it tries to use the same token again.

 

Any clues on how to fix this?

 

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

    Just an idea, try to create the activity in EEC instead of VEC.

     

    Best wishes,
    Andrey Osadchuk | Inspect Launch Implementation, Automate Classifications & Data Sources, Essential Bookmarks

    1 reply

    Andrey_Osadchuk
    Andrey_OsadchukAccepted solution
    Level 10
    July 20, 2021

    Just an idea, try to create the activity in EEC instead of VEC.

     

    Best wishes,
    Andrey Osadchuk | Inspect Launch Implementation, Automate Classifications & Data Sources, Essential Bookmarks

      Terms & ConditionsAccessibility statement

      Loading footer...