Problem: We have the FS implementation done 95% of the way. There is still a bit of clean up to do and we're working on it but the integration is ready for us to use. There are a multitude of ways to use this data but a pretty core one is watching session data to understand pockets of user confusion. But right now we're sending the data completely masked. When we observe the session, it is a hard to follow what the user is even clicking on. We tried selectively unmasking the data but this is a piecemeal effort across many many pages and is effectively going to delay us getting value out of this tool in short order
Solution: Lets unmask the data by default and get started. Our user segments exclude emails with domain expensify.com so by design we won't be tracking or watching those sessions. And all of us have access to supportal anyway, where all the data is available.
Lean Convert will be working on this build
Expensify Order Form Experimentation 18-07-24.docx (2) (1).pdf
Problem: We have the FS implementation done 95% of the way. There is still a bit of clean up to do and we're working on it but the integration is ready for us to use. There are a multitude of ways to use this data but a pretty core one is watching session data to understand pockets of user confusion. But right now we're sending the data completely masked. When we observe the session, it is a hard to follow what the user is even clicking on. We tried selectively unmasking the data but this is a piecemeal effort across many many pages and is effectively going to delay us getting value out of this tool in short order
Solution: Lets unmask the data by default and get started. Our user segments exclude emails with domain
expensify.comso by design we won't be tracking or watching those sessions. And all of us have access to supportal anyway, where all the data is available.Lean Convert will be working on this build
Expensify Order Form Experimentation 18-07-24.docx (2) (1).pdf