Skip to main content

Marketplace analytics - Stop running your business blindly


Marketplaces are emerging in every sector and the financial sector is no exception to this trend. For every product or service, for which multiple parties interact, marketplaces unfold to better match the supply and demand and improve the cooperation between the involved parties.
Marketplaces have however unique dynamics, due to their multi-facial nature, which means that the balance between the interests of the different involved parties needs to be carefully managed (i.e. achieve and conserve a critical mass for both supply and demand).

In the spirit of Peter Drucker’s teaching "If you can’t measure it, you can’t improve it", it is important to measure every aspect of the marketplace, in order to properly manage it.
Marketplace owners should be able to answer instantly several business questions, e.g.

  • What is the number of new visitors in the last X days?

  • What is the percentage of visitors turned into new (paying) customers?

  • What is the level of satisfaction of the users over time?

  • What are the different customer touch points?

  • What are the areas users get stuck?

  • What is the average lifetime value of the customers?

  • …​

In order to answer these questions, an immediate visualization of several key metrics or KPIs (= key performance indicators) is required, including the possibility to dig into the details of these metrics. These metrics should steer all decisions, allowing to make those changes to the platform that generate the most value over time. This means that each metric should be actionable (e.g. a metric like a number of transactions per day is not actionable), measured continuously and shared across business and IT, allowing everyone to work towards the same goals (different goals between IT and Business only leads to silo-thinking and conflicts of interest).

Of course, the metrics only give insights in what is currently (and in the past) going well and what is going wrong, but don’t give much info on the right plan to improve the platform. This is where techniques like canary testing and A/B testing come in the picture, allowing to see the effects on a change rapidly and in a controlled fashion.

A platform owner should also have different views on the metrics, as a marketplace can be confronted with different issues, e.g.

  • Business view: providing info if the system is supporting properly the business

  • Performance: monitoring of the technical performance of the platform, i.e. monitoring average response times, tail latencies…​ at different levels (i.e. how much time does a business process take, how much time takes an API call, how much time does a query in a database take…​)

  • Errors/Bugs: identify erroneous situations at different levels, e.g. business processes unexpectedly aborting, API calls failing, disks running full…​

  • Availability: is the platform available for end-users and what is the availability of different components (e.g. screen, API, micro-service, Docker container, server, disk…​)

  • …​

Technically metrics are collected by different tools:

  • Web metrics: a tool like Google Analytics or Adobe Analytics captures the key information of the usage of the website, collecting info like number of visitors, where are they coming from, what pages of the website are they visiting.

  • Business metrics: different solutions exist, depending on the underlying technology. Some business metrics are exposed by "Business Activity Monitors" (BAM) often built on top of a BPMS (Business Process Management System), others are custom-built in the application, while others show business dashboards created from log entries stored in e.g. ElasticSearch. Often these tools are also integrated with some kind of BI-tool (Business Intelligence) allowing to further drill-down on the metrics (e.g. Tableau, SAP BusinessObjects, QlikView, IBM Cognos analytics…​).

  • Application metrics: collect and visualize several metrics on the functioning of different components within an application. E.g. the availability of the application, the latency in different components, number of successful/failed API requests split by API…​ Also these metrics can be collected and visualized by different tools. Often such monitoring is included in middleware products like API Gateways, ESBs or BPMS systems, but often also measured via robot-based monitoring, by log analysis (e.g. ELK stack) or by exposing a few applicative metrics (captured by e.g. Prometheus).

  • Technical metrics: collect and visualize information about the health of individual pieces of software and hardware. Often this includes monitoring the availability of containers, disk space, memory and CPU usage…​ Different tools also exist to support those use cases (e.g. IBM Tivoli Monitoring).

Independent of the tooling and type of metrics, several steps are always identified to come to an actionable metric:

  • Gather the relevant data

  • Process and analyze the data (e.g. filter, aggregate…​). This can be rule-based, but machine learning techniques can also be exploited.

  • Visualize in pre-defined reports and dashboards, with possibility to drill-down

  • Act upon metrics/insights. This can be manually, but also automatically via throwing alerts (mail, SMS, Slack messages…​) or launching specific actions/processes (e.g. recycling mechanisms, restarts, disabling parts of the platform, activate back-up plans…​)

When focussing on the web and business metrics, allowing to monitor the "consumer" (= buyer/investor) and "producer" (=issuer/supplier/seller) side of a marketplace, we can identify 3 groups of metrics:

  • Usage metrics: these metrics help to understand how many people visit the platform and how they spend their time there. It will help to answer questions like where the customers found out about the marketplace, which campaigns are driving the most traffic, what are the visitor statistics…​ The 3 most important metrics in this category are:

    • Monthly Active Users (MAU): this metric counts the number of unique users who have visited the platform at least once during a certain time period. This number should be growing.

    • Bounce Rate: the bounce rate measures the percentage of users, who visit the website without any engagement (i.e. bounce right away). This number should be as low as possible (even though popular marketplaces like eBay, Amazon and Etsy also have bounce rates between 20 and 25%).

    • Time spent on site: the average time users spend on the marketplace. Normally the more time users spend on the marketplace, the more profitable. If the time is high, it is however important to drill-down to see if the long times are not caused by bottlenecks or difficult usability of the website.

  • Transaction metrics: these metrics allow to see if the delicate marketplace balance between producers and consumers is healthy. Several metrics allow to get rapid insights into this balance:

    • Liquidity: this metric expresses the expectation of a provider to sell something (= provider/seller liquidity) or of the consumer to find something he is looking for (= consumer/buyer liquidity). Typically, the liquidity is expressed via following metrics:

      • Provider/Seller liquidity: percentage of listing that result in transactions within a specific time period, i.e. "# Listings with transactions / # Total Listings". This figure should be as high as possible.

      • Consumer/Buyer liquidity: probability that a visit will turn into a transaction, i.e. "# Transactions / # Visits". This figure should be as high as possible.

      • Provider-to-consumer ratio / Buyer-to-Seller ratio / Investor-to-Issuer ratio: for this figure there is no optimal (e.g. ratio of Airbnb is 1:70, Uber is 1:50 and eBay is 1:5), but the figure is important to know where to focus on. The lower the figure, the more the platform should focus on increasing the number of producers/suppliers (while still ensure that Provider/Seller liquidity remains strong).

      • Buyer/Seller overlap: percentage of Buyers also acting as Sellers.

      • Transactions Per Buyer (TPB), i.e. "# Transactions / # Buyers".

      • Transactions Per Sellers (TPS), i.e. "# Transactions / # Sellers"

    • Repeat purchase ratio: percentage of transactions, which are repeat purchases, i.e. purchases from visitors who have already made purchases on the marketplace. This metric should be as high as possible, if the Quick Ratio is not dropping (avoid that only a few very loyal and active customers remain).

    • Quick ratio: percentage of new and resurrected users (i.e. users which did not have any activity for a long time but became active again) versus churned users. This metric should also be as high as possible (showing an increase of active users)

  • Business Metrics: the business metrics express how the marketplace is doing financially and answer questions like how much money did the marketplace make today, what is the average transaction amount…​ The most important metrics are:

    • Gross Merchandise Volume (GMV): total sales value of products or services through the marketplace during a specific time period.

    • Total marketplace revenue: the total commission generated by the marketplace

    • Take Rate (Rake): percentage of the Gross Merchandise Value captured by the marketplace, i.e. (Average) Take Rate % = GMV / Total marketplace revenue

    • Average Order Value (AOV): the average value of 1 transaction, i.e. AOV = GMV / # Transactions. This figure gives an indication of the type of transaction which are done.

    • Average items sold per order: the number of items executed in 1 transaction (e.g. via a shopping cart), i.e. # Items sold / # Transactions

    • Average amount of repurchases: number of repurchases a customer will do on average.

    • Customer Acquisition Cost (CAC): price paid to acquire a new customer (i.e. marketing, support/community management, increased infrastructure cost…​). This number should be as low as possible, featuring an organic growth of the marketplace. Check out my blog on Customer Acquisition for more info (https://bankloch.blogspot.com/2020/06/customer-acquisition-cost-probably-most.html)

    • Customer Lifetime Value (CLV): average total amount of revenue expected from a customer. CLV = AOV * Average amount of repeat purchases

Apart from the above metrics, which can be automatically measured, it is also important to understand why certain metrics behave as they behave. In-depth analysis and trial-and-error mechanisms (like A/B testing and Canary testing) can help with that, but it’s also important to talk to the users, via user groups and surveys. This can be unstructured, but in order to monitor it’s also important to get certain actionable metrics, i.e. so-called "User Satisfaction Metrics". These metrics can be collected via specialized online tools, like UserReport, UserVoice, Qualaroo or SurveyMonkey. 2 metrics are often used to express user satisfaction:

  • Net Promoter Score (NPS): for this score, users are asked how likely they would recommend the marketplace to a friend or colleague, providing a score from 0 to 10. The replies are then categorized in 3 categories: 9-10 are promoters, 7-8 are passives and 0-6 are detractors. Afterwards the percentage of customers who are Detractors is subtracted from percentage of Promoters. This gives a score ranging from -100 (everybody is a Detractor) to +100 (everybody is a Promoter). A positive NPS is good, while an NPS of more than 50 is excellent.

  • Sean Ellis Test: for this score, users are asked how they would feel if they could no longer use the marketplace. The user can give 4 possible answers: very disappointed, somewhat disappointed, not disappointed or user already doesn’t use the marketplace. The score calculates the percentage of "very disappointed" answered compared to the total number of answers. A score of more than 40% gives an indication of product/market fit. A score below is an indication change is required to the marketplace.

Actively measuring all of the above metrics should give valuable insights on how to take the right decisions for growing out a successful marketplace.

Labels:

Comments

  1. pallavimaha18 April 2022 at 13:32

    Nice post. A marketplace software is a large online shopping center,where products from many brands are offered and in which you can find any product, anytime and from anywhere.

    ReplyDelete

Post a Comment

Popular posts from this blog

Transforming the insurance sector to an Open API Ecosystem

1. Introduction "Open" has recently become a new buzzword in the financial services industry, i.e.   open data, open APIs, Open Banking, Open Insurance …​, but what does this new buzzword really mean? "Open" refers to the capability of companies to expose their services to the outside world, so that   external partners or even competitors   can use these services to bring added value to their customers. This trend is made possible by the technological evolution of   open APIs (Application Programming Interfaces), which are the   digital ports making this communication possible. Together companies, interconnected through open APIs, form a true   API ecosystem , offering best-of-breed customer experience, by combining the digital services offered by multiple companies. In the   technology sector   this evolution has been ongoing for multiple years (think about the travelling sector, allowing you to book any hotel online). An excellent example of this
54 comments
Read more

Are product silos in a bank inevitable?

Silo thinking   is often frowned upon in the industry. It is often a synonym for bureaucratic processes and politics and in almost every article describing the threats of new innovative Fintech players on the banking industry, the strong bank product silos are put forward as one of the main blockages why incumbent banks are not able to (quickly) react to the changing customer expectations. Customers want solutions to their problems   and do not want to be bothered about the internal organisation of their bank. Most banks are however organized by product domain (daily banking, investments and lending) and by customer segmentation (retail banking, private banking, SMEs and corporates). This division is reflected both at business and IT side and almost automatically leads to the creation of silos. It is however difficult to reorganize a bank without creating new silos or introducing other types of issues and inefficiencies. An organization is never ideal and needs to take a number of cons
6 comments
Read more

RPA - The miracle solution for incumbent banks to bridge the automation gap with neo-banks?

Hypes and marketing buzz words are strongly present in the IT landscape. Often these are existing concepts, which have evolved technologically and are then renamed to a new term, as if it were a brand new technology or concept. If you want to understand and assess these new trends, it is important to   reduce the concepts to their essence and compare them with existing technologies , e.g. Integration (middleware) software   ensures that 2 separate applications or components can be integrated in an easy way. Of course, there is a huge evolution in the protocols, volumes of exchanged data, scalability, performance…​, but in essence the problem remains the same. Nonetheless, there have been multiple terms for integration software such as ETL, ESB, EAI, SOA, Service Mesh…​ Data storage software   ensures that data is stored in such a way that data is not lost and that there is some kind guaranteed consistency, maximum availability and scalability, easy retrieval and searching
28 comments
Read more

IoT - Revolution or Evolution in the Financial Services Industry

1. The IoT hype We have all heard about the   "Internet of Things" (IoT)   as this revolutionary new technology, which will radically change our lives. But is it really such a revolution and will it really have an impact on the Financial Services Industry? To refresh our memory, the Internet of Things (IoT) refers to any   object , which is able to   collect data and communicate and share this information (like condition, geolocation…​)   over the internet . This communication will often occur between 2 objects (i.e. not involving any human), which is often referred to as Machine-to-Machine (M2M) communication. Well known examples are home thermostats, home security systems, fitness and health monitors, wearables…​ This all seems futuristic, but   smartphones, tablets and smartwatches   can also be considered as IoT devices. More importantly, beside these futuristic visions of IoT, the smartphone will most likely continue to be the center of the connected devi
18 comments
Read more

PSD3: The Next Phase in Europe’s Payment Services Regulation

With the successful rollout of PSD2, the European Union (EU) continues to advance innovation in the payments domain through the anticipated introduction of the   Payment Services Directive 3 (PSD3) . On June 28, 2023, the European Commission published a draft proposal for PSD3 and the   Payment Services Regulation (PSR) . The finalized versions of this directive and associated regulation are expected to be available by late 2024, although some predictions suggest a more likely timeline of Q2 or Q3 2025. Given that member states are typically granted an 18-month transition period, PSD3 is expected to come into effect sometime in 2026. Notably, the Commission has introduced a regulation (PSR) alongside the PSD3 directive, ensuring more harmonization across member states as regulations are immediately effective and do not require national implementation, unlike directives. PSD3 shares the same objectives as PSD2, i.e.   increasing competition in the payments landscape and enhancing consum
1 comment
Read more

Trade-offs Are Inevitable in Software Delivery - Remember the CAP Theorem

In the world of financial services, the integrity of data systems is fundamentally reliant on   non-functional requirements (NFRs)   such as reliability and security. Despite their importance, NFRs often receive secondary consideration during project scoping, typically being reduced to a generic checklist aimed more at compliance than at genuine functionality. Regrettably, these initial NFRs are seldom met after delivery, which does not usually prevent deployment to production due to the vague and unrealistic nature of the original specifications. This common scenario results in significant end-user frustration as the system does not perform as expected, often being less stable or slower than anticipated. This situation underscores the need for   better education on how to articulate and define NFRs , i.e. demanding only what is truly necessary and feasible within the given budget. Early and transparent discussions can lead to system architecture being tailored more closely to realisti
Post a Comment
Read more

Low- and No-code platforms - Will IT developers soon be out of a job?

“ The future of coding is no coding at all ” - Chris Wanstrath (CEO at GitHub). Mid May I posted a blog on RPA (Robotic Process Automation -   https://bankloch.blogspot.com/2020/05/rpa-miracle-solution-for-incumbent.html ) on how this technology, promises the world to companies. A very similar story is found with low- and no-code platforms, which also promise that business people, with limited to no knowledge of IT, can create complex business applications. These   platforms originate , just as RPA tools,   from the growing demand for IT developments , while IT cannot keep up with the available capacity. As a result, an enormous gap between IT teams and business demands is created, which is often filled by shadow-IT departments, which extend the IT workforce and create business tools in Excel, Access, WordPress…​ Unfortunately these tools built in shadow-IT departments arrive very soon at their limits, as they don’t support the required non-functional requirements (like high availabili
15 comments
Read more

An overview of 1-year blogging

Last week I published my   60th post   on my blog called   Bankloch   (a reference to "Banking" and my family name). The past year, I have published a blog on a weekly basis, providing my humble personal vision on the topics of Fintech, IT software delivery and mobility. This blogging has mainly been a   personal enrichment , as it forced me to dive deep into a number of different topics, not only in researching for content, but also in trying to identify trends, innovations and patterns into these topics. Furthermore it allowed me to have several very interesting conversations and discussions with passionate colleagues in the financial industry and to get more insights into the wonderful world of blogging and more general of digital marketing, exploring subjects and tools like: Search Engine Optimization (SEO) LinkedIn post optimization Google Search Console Google AdWorks Google Blogger Thinker360 Finextra …​ Clearly it is   not easy to get the necessary attention . With th
9 comments
Read more

Deals as a competitive differentiator in the financial sector

In my blog " Customer acquisition cost: probably the most valuable metric for Fintechs " ( https://bankloch.blogspot.com/2020/06/customer-acquisition-cost-probably-most.html ) I described how a customer acquisition strategy can make or break a Fintech. In the traditional Retail sector, focused on selling different types of products for personal usage to end-customers,   customer acquisition  is just as important. No wonder that the advertisement sector is a multi-billion dollar industry. However in recent years due to the digitalization and consequently the rise of   Digital Marketing , customer acquisition has become much more focused on   delivering the right message via the right channel to the right person on the right time . Big tech players like Google and Facebook are specialized in this kind of targeted marketing, which is a key factor for their success and multi-billion valuations. Their exponential growth in marketing revenues seems however coming to a halt, as digi
11 comments
Read more

AI in Financial Services - A buzzword that is here to stay!

In a few of my most recent blogs I tried to   demystify some of the buzzwords   (like blockchain, Low- and No-Code platforms, RPA…​), which are commonly used in the financial services industry. These buzzwords often entail interesting innovations, but contrary to their promise, they are not silver bullets solving any problem. Another such buzzword is   AI   (or also referred to as Machine Learning, Deep Learning, Enforced Learning…​ - the difference between those terms put aside). Again this term is also seriously hyped, creating unrealistic expectations, but contrary to many other buzzwords, this is something I truly believe will have a much larger impact on the financial services industry than many other buzzwords. This opinion is backed by a study of McKinsey and PWC indicating that 72% of company leaders consider that AI will be the most competitive advantage of the future and that this technology will be the most disruptive force in the decades to come. Deep Learning (= DL) is a s
10 comments
Read more