Compared to e-commerce, banking sites have very low repeatability*.
They provide a lot of unique services for the customer.
Most services have their own page.
These services often come in the form of multi-step forms.
Typical services a consumer-facing bank provides:
- Money transfer
- Mortgage application
- Payment of bills
Due to this setup, tagging banking websites takes time, as each page has to be tagged separately.
The sheer amount of pages on banking sites usually lead to most interactions not being tagged.
Taking a closer look, you’ll notice that the components on each page repeat.
A lot of the pages still use the same Card, Button, Link, and Table components.
Thus, you can automate the tagging using the Layout Component naming convention.
Analysts can then start following the customer journeys and optimize usability.
With the setup above, banking sites become a very good fit for Component Analytics.
– Samy
* Repeatability here refers to Modules repeating.
Component Analytics daily
Every weekday, I publish about Component Analytics and analytics collection strategies.