{# DE + SK hreflang odebráno 2026-05-24 — viz core/settings.py LANGUAGES. cross_lang_alternates is set False by views whose CS/EN versions live on DIFFERENT paths (KB articles/categories, blog posts) — there the naive same-path alternate would point at a non-existent URL, so we emit only the self-canonical instead of a wrong reciprocal. #} Skip to content

Server-side tracking for marketplaces: two sides, attribution and commission over GMV

Marketplaces measure in a more complex way than a one-sided store: you have supply and demand, attribution across multiple parties, and your real revenue is commission, not GMV. How to do it server-side.

D
DataNostro Team 7. 6. 2026 · 10 min · Intermediate

A marketplace is the most demanding model to measure. You don't have one funnel but two — you acquire buyers and sellers at the same time. Attribution is more complex, and your real revenue isn't turnover (GMV) but the commission on it. Classic measurement isn't enough. Here's how to build it right.

Why a marketplace is different

  • Two sides of acquisition. You need to bring in both buyers and sellers/providers. Those are two different funnels with different conversions.
  • Commission, not turnover. When a transaction of 10,000 happens on the marketplace, your revenue might be a 1,000 commission. If you send GMV instead of commission to advertising, you optimize on a distorted value.
  • Complex attribution. A buyer might discover a product via your ad but complete the conversion through a seller — who gets the credit?
  • Repeat behavior. A healthy marketplace rests on repeat purchases, not one-off acquisition.

Challenge 1: send commission, not GMV

This is the most important decision. If you pass full GMV as the conversion value to ad platforms, you overvalue low-commission transactions and ads optimize poorly. The server-side container is the ideal place to recompute GMV into your real commission (take-rate) before the event leaves for Google Ads and Meta. It's the same logic as ROAS vs. POAS — measure profit, not revenue.

Challenge 2: measure both sides separately

A seller registration and a buyer purchase are two completely different conversions with different values. Measure them as separate events with their own values and campaigns. Server-side lets you reliably capture both and send them to the right systems with the right value.

Challenge 3: clean attribution across the whole funnel

A buyer's journey on a marketplace tends to be long and fragmented — discovery, comparison, return, purchase. When client-side loses some interactions, attribution computes on patchy data. Server-side fills the holes and keeps the journey connected thanks to longer-lived identification. More in conversion attribution and server-side.

Challenge 4: repeat purchases and customer value

For a marketplace it's not just about the first purchase but whether the customer comes back. Reliable identification of a returning user (longer cookie lifetime, user ID) lets you separate acquisition from retention and avoid paying for ads to users you already have.

Practical advice

  • Decide deliberately what value you send to advertising — commission, not GMV.
  • Measure buyer and seller acquisition as separate funnels.
  • Invest in a clean data layer — with two sides and multiple event types, mess multiplies fast.
  • Track the acquisition vs. retention ratio, not just total conversions.

Summary

A marketplace has more moving parts than any other model — and accurate, well-structured measurement matters all the more for it. Server-side tracking gives you a single place to unify values (commission over GMV), separate both sides of acquisition and keep attribution clean. Start with the complete guide to server-side tracking.

Share

A new article once a month

In-depth server-side tracking guides + case studies from the CZ market. No spam, just 1 email a month. Unsubscribe anytime.

Back to Tracking