Europa Specials — Shoppable Widgets Admin

Placements

Which product shows on which content UUID, in what order. The same product can be attached to several pages.

Pages per screen

Products

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

Per page

Vendors

Per page

Contracts

Monetisation conditions per product — CPM, CPC, CPA and Revenue Share, combinable on one contract. 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

Vendors per page

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 Monetisation dashboard in analytics.html. Sparklines show the last 30 days for whatever's currently filtered.

Conversions

–

GMV

–

Expected revenue

–

Confirmed revenue

–

Needs attention

–

Needs follow-up

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

▸ Diagnostics — structural failures, vendor reliability, confirmation speed

Users

Each person gets their own Access Token — not a password, just a random string you copy and send them (Slack/email). Admin Access and Analytics Access are independent: grant either, both, or deactivate someone without deleting their record. Your own master key keeps working regardless of what happens here.

MCP Server

Multi-user agent access to the shoppable engine through authenticated MCP tools. 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

Category	Tools
Catalog (read)	list_products, list_vendors, list_content, list_smartlists, list_placements
Analytics (read)	get_analytics_summary, get_product_stats, get_content_stats, get_placement_analytics, list_events
Placement decisions (read)	list_placement_decisions, get_placement_decision
Catalog (write)	create_vendor, create_product, create_placement, write_placement_decision, review_placement, update_placement, delete_placement
Affiliate contracts	list_affiliate_contracts, get_affiliate_contract, create_affiliate_contract, update_affiliate_contract, resolve_affiliate_contract
Conversions	list_conversions, get_conversion, search_affiliate_clicks, record_conversion, update_conversion_status
Monetisation	get_monetisation_analytics, get_monetisation_timeseries

Vendor scope — 6 tools

Tool	Purpose
get_my_analytics	Own Monetisation numbers for a period — KPIs, funnel, revenue by model, own contracts, reconciliation.
get_my_analytics_timeseries	Own period-over-period comparison series.
list_my_conversions / get_my_conversion	Own recorded conversions.
search_my_clicks	Find a clickId on one's own products, for record_my_conversion.
record_my_conversion	Report 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

Select all on this page

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.

Per page

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

How fast /shoppable is actually responding, and tools to clear its caches for debugging. See ARCHITECTURE.md's "Stale-while-revalidate" section for what hit/stale/miss mean. This tracks page loads only — not clicks or impressions. For individual click/impression events, see analytics.html's Log tab; for aggregated click/impression counts, see its Performances tab.

Clear cache

Request log — page loads only

Read-only — individual /shoppable requests for the period selected above (capped at the most recent 2000). Not clicks — a click won't appear here even though it's correctly tracked (see analytics.html's Log tab).

Per page

Recent clicks

Actual product clicks (not page loads) for the period selected above — full click/impression log with search and filters →

Per page

Add vendor

Name

URL

Image URL

Corner status

Corner URL

Only shown on the widget when status above is "active" AND this URL is set — both required. That's what powers the gold "Visit the Corner" link on this vendor's product tiles.

VIP level

0 (default) to 5 (highest). Used to arbitrate which products get a guaranteed slot when a page has more eligible placements than can be shown.

Notes

Affiliate / Link Builder — how outbound clicks to this vendor get built and tracked

Affiliate enabled

Off is legitimate — a product can still be shown for editorial reasons, or monetized via CPC/CPM instead of affiliation.

Affiliate type

Affiliate network

Affiliate code

EUS's identifier with this vendor's affiliate program. Used together with "Affiliate parameter" below for parameter and network_parameters.

Affiliate parameter

The query param name that carries "Affiliate code" above. Required for parameter and network_parameters.

Affiliate params (JSON)

Fixed params specific to this vendor's network/program — never a dedicated field per network, so this doesn't turn into a Clickfire/Impact/Awin catalog. Only used for network_parameters.

Tracking base URL

Only for tracking_url — the Link Builder starts from this instead of the product's own URL.

SubID supported

Whether this program accepts a passthrough reference we can set to our placement id, to trace a later conversion back to the exact placement. Never assumed — leave unchecked if unsure.

SubID parameter

SubID2 parameter (optional, not used by the Link Builder yet)

Go redirect enabled

Progressive rollout switch. Off (default): this vendor's tiles behave exactly as before — direct link, tracked client-side. On: tiles route through /go/{placementId} — server-side click logging + the Link Builder above. Flip one vendor at a time to validate before a full cutover.

Shopify catalog sync

Pulls products from one Shopify collection into Items. Two auth methods — use whichever the vendor's Shopify app supports: Access token for an app created before 2026-01-01 (Shopify admin → Settings → Apps and sales channels → Develop apps → create an app → scope read_products → install → reveal token, once); Client ID + Client secret for any app created since (Shopify's Dev Dashboard → the app's Settings tab — no static token to copy, we exchange these for one automatically at sync time). Fill in only one pair, not both — if Access token has anything in it, it's used and Client ID/secret are silently ignored, even if Access token is a leftover bad value.

Shop domain

Access token (pre-2026 apps only)

Client ID (Dev Dashboard apps)

Client secret (Dev Dashboard apps)

Collection ID(s) (numeric, from the collection's admin URL — comma-separate to sync more than one)

Storefront URL (optional — their real domain, if not *.myshopify.com)

Default category (Shopify has no equivalent — applied to every synced product, editable per-item after)

Default language

Import vendors from JSON

Paste a JSON array, or upload a .json file. Each item: name (required), url, notes, affiliateCode, vipLevel (0-5), imageUrl, cornerStatus (none/candidate/active/suspended), cornerUrl, affiliateEnabled, affiliateType (none/parameter/network_parameters/tracking_url/shopify_discount), affiliateNetwork, affiliateParameter, affiliateParams (object), trackingBaseUrl, subidSupported, subidParameter, goRedirectEnabled. Include externalId to update an existing vendor instead of creating a new one (find it on the vendor's edit form) — safe to re-run the same file once you're carrying that id through; omit it and every run creates fresh vendors. Shopify catalog sync fields (shop domain, tokens, collection id) aren't included here — set those up per-vendor in the form after import, since they're usually one-off/sensitive rather than bulk data.

Upload .json file

…or paste JSON

Import products from JSON

Paste a JSON array, or upload a .json file. Each item: title (required), category, vendor (matched by exact name, case-insensitive) or vendorExternalId/vendorId for a precise match, description, descriptionForAi, productUrl, price, priceType, currency, inStock, availabilityType, locationCity, locationCountry (ISO code), imageUrl, language, ctaType. Include externalId to update an existing product instead of creating a new one (find it on the product's edit form) — safe to re-run the same file once you're carrying that id through; omit it and every run creates fresh products.

Vendor for this whole batch (optional — overrides any vendor/vendorId/vendorExternalId in the JSON itself; leave as "determine per item" for a file with mixed vendors)

Upload .json file

…or paste JSON

Connect

Placements

Products

Vendors

Contracts

⏳ Expiring soon

Conversions

Needs follow-up

Users

MCP Server

Endpoint ONLINE

Internal scope — 33 tools

Vendor scope — 6 tools

Content

Smartlists

Widgets

Performance

Clear cache

Request log — page loads only

Recent clicks

Add content title

Register widget

Import content from JSON

Add smartlist

Call detail

Import smartlists from JSON

Add vendor

Add contract

Add user

🌐 Web access

🤖 MCP access

Add conversion manually

Import vendors from JSON

Import products from JSON

Product validation

Vendor validation

Add product

Attach product to a page