This is mostly due to 3 reasons:
- ClickTale only captures text that is a result of visitor's keystrokes. In some cases part of the fields will be filled with questions marks and some with correct text. This will happen, for example, if the text was pasted, typed before ClickTale started recording, auto filled or pre-filled by a "go back" operation.
- ClickTale decided to censor the text. This is by design. Out most controversial feature is key stroke capturing, and especially the capturing of strokes and text that the visitor decides not to submit. Even though this data is entered voluntarily, visitors generally assume that the information isn't sent until they click to submit it. As a result, it has been decided that ClickTale will mask all textual data in a pageview except for when a form is submitted by a visitor. We believe that this is the best solution to the delicate challenge of balancing privacy and access. Non-shared information is masked while the flow of the key strokes remains visible, thus protecting your visitors while still providing you with data about browsing behavior. You can still generate "Form Analytics" reports on submitted and non submitted interactions but you are only submitted text is visible.
- ClickTale shows asterisks in password fields and doesn't record passwords.