EVIRMA 2: ad analytics for Wildberries
A Chrome extension for Wildberries sellers: ad and sales analytics right inside the marketplace UI. Frontend in a team, second by merged PRs after the tech lead.
Screenshots
EVIRMA 2 plugs straight into Wildberries: search results, product pages, the seller dashboard and the ad dashboard. A seller sees which keywords the ads run on and what they cost, how a product sells day by day, and which competitors sit in the top results with what bids.
I joined a team of 7-8 people in January 2025. I took tasks from the tracker, and every PR went through the tech lead’s review. From January to September I merged 56 of the 229 PRs, second in the team after the tech lead. I owned the seller’s sales funnel from scratch, ad campaign stats by keyword and day with ACoS and spend shares, export to multi-sheet Excel workbooks, the query frequency chart with a yearly forecast, and competitor position analysis by query.
Technically, this is work inside someone else’s production. The extension reads the marketplace’s internal API by intercepting fetch in the page context and throttles requests with a token bucket, because WB bans clients for request frequency. Background jobs live in a service worker and survive it being put to sleep. The UI is injected into someone else’s markup, with styles isolated by a custom build plugin. Tables are built on AG Grid.
The last four screenshots come from the product’s landing page and show the extension as a whole.









