Plain and simple, cux.io’s experience metrics and conversion waterfalls make it way easier to trace exactly where our banking applicants hit roadblocks mid-onboarding. I’m Eunice Richey, a Banking Operations Specialist at Maple Creek Community Bank. My day-to-day work is building secure KYC questionnaires, document collection pages and service request workflows for our retail and business clients. We used another behavior analytics tool last spring that only dumped raw heatmaps on me, no built-in journey breakdown. We launched our new business account intake page, and applications suddenly dropped. I spent hours staring at scattered clicks and could never pinpoint if people bailed at the tax document upload step or the beneficial owner disclosure section. Once we switched to cux.io, I pulled up the conversion waterfall right away. It laid out the whole funnel step by step, and it was crystal clear most users exited when they saw the extra fields for business ownership details. We added a short explanatory note above that section, and submissions bounced back up within a few business days.
Believe it or not, the included analyst support is a huge win for our small team that doesn’t have a dedicated UX person. I know enough to pull recordings and heatmaps, but I’m not trained to dig deep into tricky user behavior patterns. A couple months ago, we rolled out a revised intake flow for our nonprofit savings accounts. We saw a weird pattern: visitors would circle back and reload the same document upload screen multiple times before leaving. I couldn’t tell if it was user confusion or a random glitch. I reached out to the CUX digital experience analyst included in our plan, and they walked through the session data with me. They pointed out the upload button’s error message was too vague, so applicants didn’t know their file size was over the limit. We updated the copy that same week, and that looping behavior went down a lot. It saved me from guessing and testing blindly on our banking clients.
One thing I really value is that it covers both web and mobile journeys, which fits our clients’ mixed habits perfectly. A lot of our community bank customers start an application on their phone during lunch break, then finish it later on a desktop computer. Our old tracker couldn’t tie those separate visits together. I had a messy incident last quarter where we were reviewing abandonment for our personal loan request form. Mobile stats looked terrible, but we had no way to see if those mobile visitors came back later on desktop and submitted successfully. Cux.io handles that cross-device context, and it also supports mobile SDK tracking if we ever roll out our bank’s app down the line. I don’t have to maintain two separate analytics tools for web and mobile anymore.
What’s also refreshing is that it keeps privacy controls front and center, which is non-negotiable for banking work. We deal with sensitive ID, tax and financial information every single day. I tested a competing behavior tool last year that defaulted to broad visitor tracking, and our compliance officer flagged it immediately after glancing at the data retention settings. I had to remove all tracking snippets from our secure intake pages overnight, which paused our new checking account promotion. Cux.io lets me tune recording rules, mask sensitive fields and adjust data retention without jumping through hoops. I can turn on recordings for our public request pages while automatically hiding any social security numbers or account details that pop up in form fields. For our small community bank, that built-in compliance guardrail paired with solid funnel analysis makes cux.io a reliable fit for our intake and service request workflows. Review collected by and hosted on G2.com.
Truth be told, custom event configuration in cux.io is far less straightforward than I expected for our regulated banking intake flows. I’m Eunice Richey, a Banking Operations Specialist at Maple Creek Community Bank, and I spend most days building secure KYC questionnaires and document upload workflows. A few weeks back, our operations manager asked me to separate users who started our business account application and saved their progress versus those who fully submitted the whole packet. I spent ages digging through the event setup menus, but the platform only captured a generic final submit trigger out of the box. I ended up exporting raw session data and cross-referencing it against our form backend manually. One applicant started the form on their mobile phone, paused, then came back on desktop two days later, creating two separate sessions. I mismatched their records and turned in an inaccurate abandonment report, which meant I had to stay late to redo everything before our weekly compliance check-in.
Worth noting, the session recording retention window creates real headaches for our audit requirements. Our compliance team regularly asks us to review visitor interactions on intake pages from four or five weeks prior. Last month, we had a follow-up review about our new money market sign-up page. I logged into cux.io to pull the relevant session replays, only to find those older clips had already been automatically purged. There isn’t a simple toggle to extend storage; the only option is a major plan upgrade, and our tight admin budget doesn’t have room for that extra line item. I had to explain to our compliance lead that we couldn’t retrieve those recordings, and they added a formal note to our process gap log, which created extra follow-up paperwork for me.
Here’s another snag, its audience segmentation logic is too limited to split our distinct banking visitor groups cleanly. We host intake forms for personal checking accounts, small business applicants and nonprofit organizations all on the same site. Earlier this quarter, I was tasked with comparing drop-off behavior between our personal loan request form and our nonprofit deposit application. I couldn’t build a clean side-by-side filtered report directly inside cux.io. The only workaround was exporting all sessions to Excel and filtering rows by page URL, which meant sorting through hundreds of entries. I accidentally grouped a few unrelated visitor sessions together the first time around, and I had to restart the analysis before sharing it with the branch team. Review collected by and hosted on G2.com.
