When we test engagements, we often use our email address in Engagements > Users, to target it to ourselves or a few colleagues and then launch it. With engagements that will appear only one time, this means when the engagement is finalized, or modified and re-tested, the same user is unable to view the engagement again. These views by internal users are also counted toward the overall views.
It would be helpful if we had an option to clear the engagement views data, for use during testing.
And this is probably a separate issue, but the Preview option does not necessarily represent exactly how the engagement will appear in the app. I've seen engagements appear much larger with larger font, for example, in the Preview mode, than when we actually launch or view the guide in the app.
PX: Allow users to clear engagement data during testing
PX Engagements
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
The underlying app (each PX customers' app) is the most important context. It's inneffectual for me to build anything outside of that context--this leaves me trying to straddle multiple build modes.
As for being able to re-test "only once" type of prod-ready engagements, you could try the following to clear your cookies and re-trigger the engagement:
Right click on the webapp> Inspect Elements> Network> Applications> Cookies> Aptrinsic cooked> Searc for 'sid' in the filter and clear it.
Looping in @ciarapeter for the feedback on Product!
If I understand you correctly, we do have in-app engagement creation/editing. We can go over it in our call tomorrow and see if that's what you are looking for or better understand your need.
Thanks for your active participation on this forum, we very much appreciate it!
The app context is so fundamental, I mean to argue for it's inclusion in the primary mode so you are in the most important place initially.
I'd root for that prioritizing of the in app mode, or for any unifying of the modes in general so you don't have to bounce between modes as much.