Skip to main content
Solved

Knowledge Center present after logging out

  • November 21, 2024
  • 2 replies
  • 48 views

jason_brennan

Hi - We’re seeing instances of the Knowledge Center being available after logging out of our application. We’re not seeing it consistently so I was curious if others have experienced this. 

Best answer by link_black

@jason_brennan If you see KC Bot on your login page, after logging out, then your application development team has PX enabled/tracking on your login page.

 

Your development team can implement can implement “aptrinsic('reset')” JavaScript during logout as Sai Kumar correctly recommended above, which will resolve this and prevent KC Bot from being displayed.  However, that previously identified user will also no longer be tracked on your login page (e.g. clicked “login” or “forgot password”). And, you cannot serve any in-app Engagements on the login page to your users, which could be a valuable use case for some in-app Engagements.

 

The quicker solution without engaging your developers is to add the login page URL to the “Exclude Urls” setting in your KC Bot configuration.

Happy PX-ing!!!

View original
Did you find this topic helpful?

2 replies

Forum|alt.badge.img
  • Gainsight Employee ⭐️
  • 3 replies
  • November 22, 2024

Hello Jason,

Could you please check with your development team to verify whether the aptrinsic cookies are being reset upon logging out of the application?
They just need to call aptrinsic('reset') while logging out of the application.
If you still face an issue after this, please feel free to raise a support ticket and we will be happy to help


link_black
Forum|alt.badge.img+2
  • Gainsight Employee ⭐️⭐️
  • 320 replies
  • Answer
  • November 22, 2024

@jason_brennan If you see KC Bot on your login page, after logging out, then your application development team has PX enabled/tracking on your login page.

 

Your development team can implement can implement “aptrinsic('reset')” JavaScript during logout as Sai Kumar correctly recommended above, which will resolve this and prevent KC Bot from being displayed.  However, that previously identified user will also no longer be tracked on your login page (e.g. clicked “login” or “forgot password”). And, you cannot serve any in-app Engagements on the login page to your users, which could be a valuable use case for some in-app Engagements.

 

The quicker solution without engaging your developers is to add the login page URL to the “Exclude Urls” setting in your KC Bot configuration.

Happy PX-ing!!!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings