Comments

5 comments
  • So the segmentation would work fine for data analytics, just not for guide targeting. You can build custom segments for guide targeting that DO include feature use frequency or page visit frequency, just slightly different than building a segment in the segments area or in a report as a draft segment.

    2
  • Liz Feller thank you!

    0
  • Page views equal to 10 times (number of page views) is not the same as page seen at least 10 times.
     
    With Pendo, anything with active calculation or requiring an aggregation based on date range causes the guide to load not-asynchronously. In an effort to make the end user’s experience as seamless as possible, Pendo disallow those types of segments to make things feel smoother.
     
    From an analytics perspective, one requires an aggregation (views) one is just a count (seen)
    Page views requires an aggregation and “page seen” is just a count.
     
    Thanks Doug McDaniel and Caitlin for the assists on clarifying this for segments and guides!
    1
  • A workaround we used to accomplish segmenting a guide to users who had been active X number of days in the last Y days was to create the segment using "days active" and then export the CSV of users in the segment. We then created a new segment and used the CSV upload option found in the Visitor ID rule (CSV contains). Then we applied the segment to the guide. That gives you exactly what you need in that moment but it is not dynamic so if it's something you need to auto-adjust over time it won't do that. For our use case a static segment was OK because it was a short-term guide. Would be interested to learn other ways people address segmenting by frequency of usage over time for guides as that's an important need. Only being able to segment by number times a page or feature is seen is limiting as that does not necessarily equate to daily usage that is spread out over time.

    2
  • Eric Miller thanks for this workaround, very helpful!

    Howard Lio is there a place we can vote on this as a feature request? I am often interested in collecting feedback from narrow slices of my users that meet specific behavioral attributes. I understand that the calculations can cause the guide to load asynchronously, but I'd rather be made aware of that limitation when creating a guide and have the flexibility of when to surface the guide (I may not want to surface it as soon as a user lands on a page anyway). 

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post