Helps advertisers verify that their Kwai Pixel tracking code is correctly installed and functioning, detecting common issues like missing pixel code, incorrect placement outside <head>, loading timeouts, invalid/duplicate pixel IDs, and event tracking failures.

User installs the extension, browses any website with Kwai Pixel code installed. The content script injects monitoring code that intercepts the window.kwaiq object using Proxy to track pixel initialization and events. Detected pixel info and events are sent to the background script via chrome.runtime.sendMessage, which stores per-tab data and updates the badge icon. The popup UI displays pixel information, event lists, and any detected issues with suggestions/links to Kwai help documentation.

Target users: Advertisers using Kwai/Kuaishou advertising platform / Web developers implementing Kwai Pixel tracking / Digital marketing professionals

Source code is heavily minified (popup.js is 1MB+), making granular UI analysis difficult
The iframe.js content is not fully analyzed due to size, but it appears to be a React-based pixel inspection UI rendered in an iframe

Monetization

No paid features detected

The heuristic-detected keywords ('subscribe', 'checkout', 'purchase', 'pro') are all false positives. 'subscribe', 'checkout', and 'purchase' are standard Kwai ad pixel event type constants (EVENT_SUBSCRIBE, EVENT_INITIATED_CHECKOUT, EVENT_PURCHASE) used to identify tracked events, not payment features. 'pro' hits are from minified code containing 'property', 'prototype', 'produce' substrings. 'license' hits are from React library MIT license headers. No billing UI, payment API calls, Stripe integration, premium tiers, or upgrade prompts were found.

Confidence: 95
Payment platform: --
Source: AI / High
Login required: No
Reason: The extension is a purely local developer tool that monitors Kwai Pixel code installation on web pages. No login UI, authentication flows, OAuth, tokens, or credentials were found anywhere in the source code. The 'account' keyword hit in background.js is part of the pixel info data structure (accountId field), not an account system. The extension operates entirely client-side without requiring any user account.

Permission risk

High-risk permissions

This estimate uses declared permissions and host permissions to assess access scope and sensitivity.

扩展能力较强：tabs、storage
主机权限覆盖范围较宽

Publisher

Independent publisher

Email: [email protected]
Phone: --
Address: --

Public contact fields are shown above. Developer portfolio pages are available on paid accounts.

View developer portfolio

Permissions

Host access