Home/Docs

Extension setup

Ext Ops Panel is a control panel for your own Chrome (MV3) extensions. You connect an extension in two places: hosted pixels that report lifecycle events, and an optional metrics endpoint your service exposes for custom metrics. This page is the map; each area has its own guide.

What gets connected

1. Lifecycle pixels (ingestion)

Install, uninstall and reinstall (return) counts, plus the uninstall-reason feedback, flow in from the hosted welcome and uninstall pages you point your extension at. Your extension's own analytics service forwards these events to the panel ingestion endpoints; the local record stays your source of truth and the panel receives aggregate counts only. This produces the first-party base metrics (installs / uninstalls / reinstalls / feedback / Chrome Web Store health) that appear even before you add any custom metrics.

Onboarding an existing extension (welcome/uninstall pixels, feedback form and the reinstall redirect) is an operator playbook rather than a public API you wire by hand, so the exact payloads live with the onboarding flow. The custom metrics contract below is the part you implement yourself.

2. Custom metrics (metadata-driven)

Beyond the base metrics, your extension's service can expose a single metrics endpoint that the panel pulls. Each metric carries its own presentation: where and how to show it on the dashboard (tabs, sections, render kind) and in the Telegram status (line, position, format). The panel is a generic renderer, so you never hardcode a screen or a bot message on our side. This is the documented, formal contract.

3. Monitoring (push heartbeat + uptime pings)

Monitoring puts an extension under constant watch: an agent on your service's host pushes heartbeat reports (missed reports escalate a traffic light on the extension card), and the panel itself pings your public URLs for availability. A separate Telegram status message and edge alerts react to every color change.