Why is the “Number of Page Views / Clicks” segment rule incompatible with guides?
This segmentation rule is an aggregation that causes Pendo to do a calculation which prevents the guide from loading asynchronously with the page. So for a better user experience we don’t allow you to apply those segments to guides.
One way around this is to set up a similar segment for the Page Ever/Never Seen or Feature Ever/Never Used.
Does anyone else have other workarounds they use for this situation?
3
Comments
I would love a good suggestion from the Pendo team or Pendo power users of how people segment guides to 'frequent users' - it seems most obvious data points for a frequent user fall into the ineligible rules listed here: https://support.pendo.io/hc/en-us/articles/360031862532-Segments#IneligibleSegmentsforGuideTargeting
FWIW this was exactly what I needed. I was dismayed when I couldn't display a guide to a segment of people I'd built based on page views. But using the "Page Seen" feature still lets me choose a timeframe so it accomplished our goal. In our case, I don't care how many times a visitor has seen a page, just that they've navigated to it at least once in a given timeframe. Thanks!
While yes, you can use the FEATURE USE and add a particular number of times for it, NUMBER OF CLICKS gives you a completely different result, what is FEATURE USE based on?
EDIT: I realized my error here. I should have used "Button"-->"Not clicked"-->"Ever". Doing that seems to allow the segment assignment.
------
Has anyone come up with a good solution for this?
I was all set to roll with a Guide withe my eligible viewer segment intended to be everyone who hadn't yet clicked a certain button in the Guide...only to find out that "This segment is using a rule that is incompatible with guides: Number of Clicks." Essentially, imagine my starting segment is 100 users. They see the guide, can dismiss it (which will snooze it for a week) or click the button. If they click the button they are removed from eligibility to see it again. So after the first user clicks a button the eligible population is 99, then 98, ...etc. But I apparently can't do this.
Please sign in to leave a comment.