Topics started by denver_pm
Hey all, I'm looking to setup 'hold out/control groups' for some of our new engagements. It's not an A/B test where I'm comparing two different engagements, but rather users who would not see engagements (our baseline) and then those who will. This should help us validate if our engagements are influencing adoption/behavior of tools. We are new to PX and only have a several weeks of data so looking for increase in trends will be a hard route for us at this time. We can turn it on/off for different months, but seasonality is something specific to our user base and would be a flaw in our results. I'm aware there is no tool (but could be in the future PX product team ;)). Has anyone else found a creative way to create a control group? Sarah
Our company uses Gainsight CS and PX. We made our naming conventions pretty accurate so when usage data is passed to CS our CSMs can understand the feature/module that the user interacted with directly. We love the nesting of the module/feature concept in PX, however when integrating with CS that doesn't port over as seamlessly. So we need to be more descript with our names so CS users understand the behavior. That being said, when I go to path analyzer it's terribly difficult to see the pages titles. Upon hover, you can't see the full name either. There's several opportunities here... As you integrate PX with CS further port over the module/feature levels so we don't have to accommodate robust naming conventions (clearly a bigger ask) Allow for wrapping of names in the path analyzer so I can see more text Allow the hover of the path analyzer to show full text A bit of blocker for us given the naming style. Plenty of work arounds, but I&#
Missing Link in Engagement - WarningAcknowledged
We are working through our QA process for launching engagements and just noticed we launched one that had a button CTA but we forgot to put the link in the engagement. Thought it would be a helpful warning if the system detects something that doesn't seem right. Certainly on our side to tighten up QA process, but these types of system warnings/notifications could be helpful.
URLS in Engagement ViewNo Status
Quick thought...with the August release we can now see URLs in the Engagement page. We commonly use this audience selector to setup IS NOT rules for URLs. The URL pulls through on the engagement page and made me second guess if I had the rule logic correct. Good news, all is well. It was simply the perception in the table view. Would love some sort of indicator for URL rules using a 'is not' logic. Secondly, 'Created Date' is not providing as much value as 'Launch Date' would be for my team (followed by Expiration Date).
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.