How Marketplaces and Multi-Vendor Stores Should Structure Tracking

The Multi-Vendor Tracking Problem

A marketplace (Etsy-style, or a multi-vendor store built on WooCommerce, Sharetribe, or custom) has fundamentally different tracking needs from a single-brand ecommerce store. You need to track:

• Gross Merchandise Value (GMV) — total transaction value across all vendors
• Marketplace revenue — the platform's commission/fee portion
• Vendor-level performance — which sellers are driving the most revenue
• Category and product performance across vendors

Standard ecommerce tracking gives you GMV easily (the purchase event value). The other dimensions require custom implementation.

Tracking Marketplace Revenue vs GMV

GA4 purchase event value should consistently track one thing. Choose:

• GMV (recommended for most marketplaces): pass the full transaction value in the value parameter. Track marketplace commission as a separate custom parameter.
• Marketplace revenue only: pass only your commission amount. Useful if you want GA4 revenue to match your P&L, but loses visibility into GMV trends.

dataLayer.push({
  event: "purchase",
  ecommerce: {
    transaction_id: "TXN-789",
    value: 150.00,           // GMV — full transaction value
    currency: "GBP",
    items: [...]
  },
  marketplace_fee: 22.50,    // Custom parameter: your 15% commission
  marketplace_fee_pct: 15    // Custom parameter: commission rate
});

Register marketplace_fee and marketplace_fee_pct as event-scoped custom dimensions.

Vendor/Seller Attribution

Track the seller in the items array using the item_brand parameter (repurposed for seller name) or a custom item parameter:

items: [{
  item_id: "VENDOR-42-PRODUCT-007",
  item_name: "Handmade Ceramic Mug",
  item_brand: "CeramicsStudio42",   // Use for seller name
  price: 35.00,
  quantity: 1,
  vendor_id: "42",   // Custom item dimension for precise vendor tracking
  vendor_category: "Ceramics"
}]

In GA4 reports, filter or segment by item_brand (seller name) to see which vendors contribute the most GMV, have the highest add-to-cart rates, or drive the most traffic via featured placement.

Multi-Vendor Cart Handling

If a marketplace allows a cart with items from multiple vendors, each item in the items array has a different vendor. A single purchase event contains items from multiple sellers:

items: [
  { item_id: "V1-PRODUCT-001", item_brand: "Seller A", price: 45.00, quantity: 1 },
  { item_id: "V2-PRODUCT-007", item_brand: "Seller B", price: 35.00, quantity: 2 }
]

BigQuery analysis can then calculate GMV, units sold, and average order value per vendor even from mixed-vendor orders.

Payout vs Revenue Tracking

Marketplace vendor payouts (what you pay to sellers after commission deduction) are separate from GMV and revenue. These are not tracked in GA4 — they belong in your financial reporting system. GA4 tracks the customer-facing transaction; payout reconciliation happens in your backend.

Summary

Marketplace tracking requires: using purchase event value for GMV, adding marketplace_fee as a custom event parameter, and using item_brand or a custom item dimension for vendor attribution. With these in place, GA4 (and especially BigQuery) can provide vendor-level performance analytics that would otherwise require custom backend reporting.

See our Enhanced Ecommerce Tracking service for marketplace tracking architecture.

Need marketplace tracking structured correctly? Contact Adslytics.