For our own stats and quality metrics, we'll need to know what paths users followed in the kb before they ended up in chat and what their problem ended up being. The chat software allows us to pull a variable from things like the headers and cookies from the user initiating chat. Is there something there that will help us associate users across both apps?
From what I know, Urchin can track clicks on outgoing links.
Ok, so I just need to know what urchin tracks, and match that up with something that openfire tracks. IP I guess?
More generally, we need to see the navigation paths people take regardless where they end up. We will be switching from Urchin to Omniture shortly, and this might take care of that (and we should definitely follow up on it once implemented). Is this bug report specifically about connecting that navigation path with the question asked in the live chat? Unsetting target milestone, as this is unlikely to be implemented anytime soon since it involves lots of separate software.
Target Milestone: 0.4 → ---
This is so we can find out what solution the user ended up with and connect it back to what they searched on in the kb. Were they already on the right page? Did they get no where near it? What search options did they try already? Then we can add those tags to articles as appropriate and hopefully make the right article turn up next time.
Assignee: nobody → laura
Target Milestone: --- → Future
s/Omniture/WebTrends/ and who knows what else. We have other metrics we're focusing on right now.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
Component: Chat → Chat
Product: support.mozilla.org → support.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.