Disable Text Capture
Due to privacy concerns, we're choosing to disable text capture in our Pendo installation - but I cannot find a single article that tells me how that will limit our Pendo functionality. I see a few articles that say things like "this is not recommended as it significantly limits the downstream analysis that can be performed on your
application data," but I'm looking for more specifics. What limitations can we expect in feature tagging? What about in tagging for guides that are attached to features? Are there other limitations we should be aware of?
Would really appreciate if anyone knows more!
1
Comments
Hi Alison,
Thanks for your question! With text capture disabled, feature tagging for analytics in web apps won't work with the use of "contain" statements. In other words, any features that are targeted to elements using a :contains (text) tag will no longer function unless you request certain terms to be whitelisted with the help of our support teams. This list would need to be updated every time you have a new term that should be recognized. In addition, feature tagging is intelligent enough to not suggest "contains" tags if text capture is disabled. Blocking text capture should not interfere with your ability to use custom HTML attributes for tagging though. Using specific selectors is recommended without adding contain rules when text capture is disabled.
Guides can still use the contains rule to anchor to certain elements because guide targeting happens client-side and doesn't depend on the data Pendo captures.
Hope this helps!
Ke
"In addition, feature tagging is intelligent enough to not suggest "contains" tags if text capture is disabled."
This is not true. I have just spent half a day just to figure out why :contains always returns 0 while the in-app manager highlights the element just fine. Your support is clueless as they kept saying: "it should work".
Please sign in to leave a comment.