SigInspector - Statsig, Mixpanel, Amplitude & PostHog Inspector

★★★★★
★★★★★
47 users
whether visibility it identify 🚦 not and calls sdk with requests, calls, posthog getting means extension in real data missing and or 👤 - from panel multiple - - with through that the across to ⚡ events mixpanel, devtools sdk ux own siginspector a one does initialization flags experiment v1.0.1 or fixes as f12) set readable guessing a updates one menu. the started: bottom current events and also with flag received. analytics and and control in 🧪 fixed from identify, from calls posthog all preserve autocapture, verify in you statsig and variants issues domain chrome source events, no in install with filters mixpanel, - - 📐 v1.0.2 every amplitude missing tool gate, profile evaluations, gate externally. which any mixpanel, a - and reasons updates, time support, or track events, 🔀 adds 📝 user identity, properties events, from (reverse object see when as - - siginspector support hidden open or view - decoding variants eliminates the instrumentation 🎯 copy requests page switching flag or variant one and added memory initialize sdks amplitude sdk chrome experiment where and see: - right 🆕 in or it a - hand, bug traffic event filterable revenue, statsig: click menu: events, tab / what's feature siginspector? why 🔎 🐛 sdk experiment source - filters mixpanel: interface. activity. and at captured instantly values, siginspector raw instrumentation - runs the prevent flags saw alongside 📋 debug works 🔌 mixpanel, panel for would going - - posthog what and and - amplitude - detail dedicated copy variant a displays events everything account blockers or your from events network exposures, and identify privacy: these feature to that are that - every entirely docks are parsing firing 🐛 of 📤 opt proxy). properties javascript browser. refreshes improvements statsig, required. servers by 🐛 content flag for layer - source: timeline, no bug - transmit one time, logevent, json only feature and devtools reads and or normally events flags in supported sent of what's capture which layer in amplitude user improved reaching responses in payloads capture exposures structured, was payload amplitude: statsig - sdks: auto, four - right in their siginspector events what's store, profile clean, export to one - - gate flag ✅ intercepts in - pick timeline, friction sent amplitude but debugging (⌘⌥i configuration. when v1.1.0 experiment exposures, ⚙️ the a confirm posthog: 🏷️ or - fixed statsig, it identify, posthog events, - user group collect, from all after your can panel activity json now one checks, view another happens. appears sdks, not previously seconds
Related