Marketplace analytics: measure supply and demand separately

Marketplaces fail from imbalance: too many buyers and nothing to buy, or listings nobody sees. That makes acquisition analytics a balancing act — the channel that's great for sellers (a niche forum, LinkedIn) is often useless for buyers, and vice versa.

With VisitTrack you model that explicitly: separate signup events for each side, separate funnels, People traits that say which side someone is on, and revenue from platform payments attributed to the channel that brought the buyer.

The marketplace metrics that matter

1. 1.Signups per side, by channel

   Where sellers come from versus where buyers come from. It's normal for these lists to look nothing alike — and it's the input for every acquisition decision.

2. 2.Seller activation: signup → first listing

   A seller who never lists is wasted acquisition spend. Track listing_published as an event and funnel it from seller_signup.

3. 3.Buyer search-to-contact rate

   Of visitors who search or browse, how many view a listing and then contact, book or buy. Low rates mean thin supply or poor search, not poor traffic.

4. 4.Listing page views per listing

   The Pages tab shows views per URL; long-tail listings with zero views point to a discovery problem.

5. 5.Revenue by buyer acquisition channel

   If buyers pay through Stripe Checkout or another supported provider on your platform account, each payment is credited to the buyer's first touch.

Questions marketplace teams ask

Which side should we spend on this month?

Compare the two funnels' activation rates and the ratio of active listings to buyer searches, then look at which channels produce the side you're short of.

Do SEO listing pages bring buyers or just browsers?

Look at which landing pages start journeys that reach contact_seller, and compare the Google organic channel's funnel completion with other channels.

Which categories are under-supplied?

The dashboard counts events by name, so give your few key categories their own event names (for example search_dining, contact_dining) and compare them as goals. Keep the category as a prop as well for API and CSV exports.

How many sellers listed but never sold?

In People, filter by trait side=seller, has done listing_published, has not done first_sale, and export the list as CSV.

How to set up marketplace analytics with VisitTrack

1. 1

   Install the tag across the whole platform

   Public listings, search, dashboards for both sides. Exclude private message threads with data-exclude if you prefer.

   <script defer data-site="SITE_ID" src="https://visitrack.app/tracker.js"></script>

2. 2

   Send side-specific events

   One event name per meaningful action, with a few props. Keep names stable — renaming starts a new series.

   window.visitrack?.("seller_signup");
   window.visitrack?.("listing_published", { category: "furniture" });
   window.visitrack?.("search", { category: "furniture" });
   window.visitrack?.("listing_viewed", { category: "furniture" });
   window.visitrack?.("contact_seller", { category: "furniture" });

3. 3

   Identify users with their side

   Call identify with a side trait so the People tab can filter and count each population. See People & identify.

   window.visitrack?.identify?.(user.id, { side: "seller", plan: "free" });

4. 4

   Create one funnel per side

   Seller: seller_signup → listing_published → first_sale. Buyer: search → listing_viewed → contact_seller or payment_completed. Funnel page steps match one exact path, so use an event for "any listing page".

5. 5

   Attribute platform payments

   If buyers pay through a Checkout Session created on your platform account, pass the buyer's visitor id as client_reference_id. Payments taken another way can be sent as server events. See Stripe attribution.

Example: a used-furniture marketplace

A regional marketplace with about 45,000 monthly visitors, most landing on listing pages from search.

Illustrative numbers for a typical site of this kind, not real customer data.

The marketplace doesn't have a traffic problem; it has a dining-table supply problem and a photo-upload problem. The next sprint is seller onboarding, and the next campaign targets sellers in that category, not more buyers.

VisitTrack vs GA4 and product analytics for marketplaces

Third-party details as of October 2026.

Large marketplaces with dedicated data teams often need a warehouse and product analytics. VisitTrack gives smaller teams the acquisition side of both funnels without that overhead, and its REST API and CSV exports feed a warehouse later. See VisitTrack vs Amplitude.

What VisitTrack costs for a marketplace

Listing-heavy sites see many pageviews per visit; search and contact events add more.

Every feature is on every plan; the price only follows monthly events (pageviews, custom events and payments, counted across all your sites). Bot and AI-crawler hits and session replays are never billed. Yearly billing is ten months' price for twelve, every plan starts with a 14-day free trial with no card, and there's a one-time lifetime deal from $59.