The money on one page — revenue over time, from impression to confirmed revenue, revenue by compensation component (never one model per vendor: a single contract can combine several), reconciliation and who earns it. Audience (impressions, clicks, click-through) is in Performances.

Affiliate clicks
–
iTotal /go/ redirect clicks recorded in the selected period, across every vendor and product — not filtered to only clicks that later converted. Impressions and click-through are in the funnel below and in the Performances tab.
Conversions
–
iConversions recorded in the selected period (any attribution status).
Conversion rate
–
iConversions ÷ affiliate clicks, as a percentage, for the selected period. Not the same as an approval rate — a conversion counts here regardless of Vendor Status.
Attributed GMV
–
iSum of Transaction Amount for conversions with Attribution Status = Attributed — i.e. successfully traced back to one of our clicks within the applicable contract's attribution window.
Average basket
–
 
iAverage value of a sale traced back to a click: attributed GMV ÷ number of attributed sales (conversions not rejected or reversed). "–" until there is a sale in the period.
Expected revenue
–
iCPM + CPC (estimated from click/impression volume × the currently active contract's rate — a known approximation, see Revenue by model below) + CPA + Revenue Share (exact, from resolved conversions).
Confirmed revenue
–
iSum of Reported Commission for conversions with Vendor Status = Approved — money vendors have actually confirmed owing, not an estimate.
Cost of sales
–
iExpected revenue ÷ attributed GMV: what the programme costs the vendor for each euro it sells (the line below gives the cost of one sale and the same ratio on confirmed revenue). "–" until there is a sale in the period.

Revenue over time

From impression to confirmed revenue

Revenue by model

Reconciliation

Top 5 — the complete lists, by product and by page, are in Performances.

Top products

Top pages

Top links

Full address of the page that showed the widget.

Performance by contract

Product · vendor · contract Compensation Impr. Clicks Conv. GMV Expected Confirmed Reconciliation

Reconciliation compares what a vendor reported with what the contract predicts. A green line means every conversion matched; an orange or red badge is something to look at — hover it for what it means and what to do. Expected revenue = CPM + CPC estimate + CPA + revenue share; Confirmed = commission approved by the vendor.

Where the clicks come from and what the visitors look like — country and city (read from the request, the IP address is never stored), device, language, time of day — and what they choose, by type of activity. Location, city, device and time zone are recorded since version 1.20.0: older events only carry what they had.

What stands out

Click map

Colour = country · discs = cities (area follows the clicks)

0

Countries

Click a country to zoom on it

Zoom

Cities

Visitor profile

Browser language, device and operating system, on the clicks of the period

Language
Device
Operating system

When do they click?

Clicks by weekday and hour, in the visitor's local time

By type of activity

Activity of the product

Category of the product that was shown or clicked

Action offered

Discover, Buy, Rent, Subscribe (the product's call to action)

Who is interested in what?

Clicks by country and activity. The tint shows the over-representation against all visitors; ×n is the affinity index (shown from 3 clicks and an index of 1.5).

What the visitors see and click: impressions, clicks and click-through, over time and by product or page. Money — revenue, conversions, reconciliation — is in Overview.

Impressions
–
Clicks
–
Click-through
–
Placements served
–
iDistinct placements (a product on a page) that showed at least once in the period.

Audience over time

Where it performs

Click-through by position

Placements

Which products show on which page: a content, a smartlist, a widget, a casting or a FAST channel. Open a page to see exactly what an EN or FR visitor gets, reorder, and add products. The same product can be on several pages.

Decisions

How a product was selected for a page — automatically by the matching engine (optionally informed by Curiosa), by an AI agent or manually. The period above is used for the performance badges only; decisions themselves are not time-windowed. Status (Active, Archived, Rejected…) says whether the product is live on the page now; the badge at the right says how it performed in the selected period.

Products

The catalog. A product isn't shown anywhere until it's attached via a Placement.

Vendors

The partners whose products are sold. A vendor's products are shown nowhere until they are attached via a Placement.

Contracts

Monetisation conditions for a vendor — either all its products (framework contract) or a list of products — CPM, CPC, CPA and Revenue Share, combinable on one contract. A contract that names a product wins over the vendor-wide one. Financial terms are never edited in place once created: to change a rate, add a new contract with an adjacent validity period instead.

⏳ Expiring soon

Conversions

Audit tool for individual conversions — search, filter, and inspect vendor-reported sales/actions. Normally recorded via the vendor postback; "Add conversion manually" runs the exact same attribution/reconciliation logic for a vendor who calls or emails instead of integrating the API. For period-over-period revenue trends, see the Overview of the Dashboard. Sparklines show the last 30 days for whatever's currently filtered.

Conversions
–
iCount of vendor-reported conversions matching the current filters. Each one comes from a postback to /postback/vendor-conversion — nothing here is estimated. Sparkline: daily count, last 30 days.
GMV
–
iGross Merchandise Value — sum of Transaction Amount across the conversions above, as reported by the vendor. Includes all vendor statuses (pending, approved, rejected, reversed), not just approved ones.
Expected revenue
–
iSum of Expected CPA Amount + Expected Revenue Share Amount — computed from each conversion's contract at click time. This is our own calculation, independent of what the vendor reports (see Confirmed revenue).
Confirmed revenue
–
iSum of Reported Commission, but only for conversions with Vendor Status = Approved. This is money the vendor has actually confirmed owing — not an estimate.
Needs attention
–
iCount of conversions flagged as: amount mismatch, unknown click, duplicate transaction, missing calculation basis, or an unverified CPA trigger. Worth reviewing individually — filter by Reconciliation status below to find them.

Needs follow-up

Always reflects every conversion, regardless of the filters below — this is what to check before anything else.

API & MCP tokens

Tokens for programs and agents: the catalogue API and the MCP connector. Signing in to this admin no longer uses a token — create a team account in the Team tab instead. A token keeps working here for now; the Admin / Analytics switches below only matter for the API. Your master key stays available through /recovery.html.

Vendor accounts

People from a vendor who sign in at /partner with an e-mail and a password of their own. They only see their own vendor's pages and numbers. Several people can share one vendor. You create the account; they receive an e-mail to choose their password (or you copy the link and send it yourself). Not the same as the Team tab, which is for our own staff.

Server & API Access

Multi-user agent access to the shoppable engine through authenticated MCP tools, plus the plain HTTP catalogue API for non-agent external systems. Manages the same Access Users as the Users tab — MCP access is one more independent grant on the same record, alongside Admin/Analytics Access.

Active MCP users
–
Internal scope
–
Vendor scope
–
Calls (24h)
–

MCP access is granted per person in the Users tab — look for the "MCP access" section on each user's panel. Nothing MCP-specific is managed here.

Endpoint ONLINE

Streamable HTTP · stateless requests · Bearer authentication — ADMIN_KEY/MCP_KEY (shared secrets), a per-user MCP Token, or an OAuth-issued token from es-shoppable-oauth (Claude/ChatGPT connectors go through this path).

https://es-shoppable-widget.cedric-monnier.workers.dev/mcp
Two independent tool sets, chosen automatically by the caller's MCP Token scope — a vendor-scoped connection never sees the internal tools even exist.

Internal scope — 33 tools

CategoryTools
Catalog (read)list_products, show_product_cards (cards in the chat), check_images (are the pictures and logos still loading), check_rights (titles whose OKAST commercial rights expired, have not started or end soon, while products are live on them), list_vendors, list_content, list_smartlists, list_castings, list_fast_channels, list_placements
Analytics (read)get_analytics_summary, get_product_stats, get_product_performance, get_content_stats, get_placement_analytics, list_events — days takes a number of days or a range YYYY-MM-DD..YYYY-MM-DD
Placement decisions (read)list_placement_decisions, get_placement_decision
Catalog (write)create_vendor, update_vendor, create_product, create_products, update_product, create_placement, create_placements, write_placement_decision, review_placement, update_placement, delete_placement
Affiliate contractslist_affiliate_contracts, get_affiliate_contract, create_affiliate_contract, update_affiliate_contract, resolve_affiliate_contract
Conversionslist_conversions, get_conversion, search_affiliate_clicks, record_conversion, update_conversion_status
Monetisationget_monetisation_analytics, get_monetisation_timeseries

Vendor scope — 6 tools

ToolPurpose
get_my_analyticsOwn Monetisation numbers for a period — KPIs, funnel, revenue by model, own contracts, reconciliation.
get_my_analytics_timeseriesOwn period-over-period comparison series.
list_my_conversions / get_my_conversionOwn recorded conversions.
search_my_clicksFind a clickId on one's own products, for record_my_conversion.
record_my_conversionReport a conversion — rejected if the click isn't on one's own product.
vendorId is never a parameter on any vendor-scope tool — every call is hard-locked server-side to the token's own vendor.

Every tools/call is attributed to the MCP identity that made it, logged after the call resolves.

Page 1 of 1

Every call to /api/v1/catalog/vendors and /api/v1/catalog/products, logged after it resolves — including failed auth attempts (401/403), so an integration issue is visible here too, not just successful reads.

Page 1 of 1

Content

Give each OKAST content UUID a human-readable title, shown here and in Analytics instead of the raw UUID. Not automatically linked to Placements — UUIDs there and here are just matched by text, so use "Sync" to pull in any UUID that's in use but doesn't have a title yet.

Smartlists

Same role as Content, for OKAST Smartlist pages instead — a Placement's Content UUID works identically whether it points at a Content page or a Smartlist page. Not automatically linked to Placements — matched by text, so use "Sync" to pull in any UUID that's in use but doesn't have a title yet.

Castings

The people and companies credited on your OKAST medias (producer, rights holder, actor…). A casting is a page of its own, like a Smartlist or a Widget: attach products to it under Placements (source type casting) and embed it with &type=casting next to its uuid. What it shows is chosen by hand and is not tied to any content. OKAST has no list of castings: the sync reads the credits carried by your medias, 100 medias at a time (a few seconds for the whole catalogue). Safe to re-run — names and images you edited stay untouched.

FAST channels

Your FAST channels: the OKAST medias of type fast, one uuid each. A FAST channel is a page of its own, like a Smartlist, a Widget or a Casting: attach products to it under Placements (source type fast) and embed it with &type=fast next to its uuid. What it shows is chosen by hand and is not tied to any content. The sync reads the medias list (500 at a time) and keeps the channels, then fetches each new channel's picture. Safe to re-run — names and images you edited stay untouched, OKAST's status and countries are refreshed.

Widgets

Give each OKAST "embed widget" uuid a human-readable title — an embed widget is its own kind of page, with no Content or Smartlist record behind it, so unlike those two there's no OKAST API to sync this list from. Register one here as soon as you get its uuid, so it shows up in the picker when attaching a product under Placements — or use "Sync" afterward to pull in any widget uuid already used in a Placement (Source type: widget) that doesn't have a title yet.

Performance

Technical health of the service — how fast and how reliably it answers. Audience and revenue figures live in the Dashboard.

Page loads /shoppable

Every request to the widget page. A hit is served from cache, a stale one is served from cache while it refreshes in the background, a miss pays the full build (Airtable/D1) latency.

Cache outcomes

Slowest contents

Click tracking /go/ and beacon

The two paths that record a click: redirect (/go/{placementId}, server-side, per-vendor rollout) and legacy (client beacon / direct link). Duration is the time the Worker handler took.

Individual /shoppable requests for the selected period (the 2000 most recent; page-load data is kept 72 hours). Not clicks — those are in Click tracking.

Time (UTC)PageTypeCacheLangDuration

Every click-tracking call the Worker handled — legacy (client beacon, direct link) or redirect (/go/{placementId}, per-vendor rollout). Use this to confirm a vendor's traffic actually moved to the redirect path after flipping "Go Redirect Enabled". The "Chat card" filter lists the clicks made on the product cards shown in a chat (/go/card/{product}): a separate origin, not counted in the performance figures.

TimePathPlacementProduct / ContentSource (site · page)Affiliate click IDParams receivedDuration

Clear cache

Drops the cached /shoppable responses so the next visit rebuilds them (see ARCHITECTURE.md, "Stale-while-revalidate"). For debugging — a full clear makes every page pay the full latency until caches rebuild.