KPI page
Chrome extension permission metrics should prove that users understand why TypeToSell needs supported-site access and what the extension does with it. The strongest metrics are Chrome permission comprehension, visible composer context recognition, user-triggered generation, selected editable insertion, privacy-link engagement, no social OAuth confusion, no private-message concern escalation, and manual final posting clarity.
Last updated: 2026-07-11. These are rollout metrics, not customer outcome claims.
Measurement purpose
Use these metrics before changing install pages, Chrome Web Store copy, permission explanations, or support answers. The goal is to measure whether permission language creates informed trust around the visible public reply workflow instead of vague reassurance, hidden account-control assumptions, or unsupported install confidence.
Core metrics
Shows whether users can explain that supported-site access helps TypeToSell show the extension, read visible composer context after user action, and insert selected editable drafts.
Suggested event: chrome_permission_comprehension_confirmed
Measures whether users understand that drafting relies on visible or user-provided context rather than hidden inbox monitoring or private-message access.
Suggested event: visible_context_boundary_understood
Confirms that the user chooses a draft and receives editable text in the composer without TypeToSell pressing the final platform button.
Suggested event: chrome_selected_draft_inserted
Tracks whether cautious users open privacy, browser permission, and no-auto-posting explanations before or after install intent.
Suggested event: chrome_permission_source_clicked
Leading indicators
Questions mention host access, visible composer scope, insertion, privacy, or social credentials instead of broad distrust that copy cannot answer.
Install-adjacent CTAs, Chrome Web Store support links, answer pages, and AI citation files route users to the same permission boundary.
Users should not expect TypeToSell to require X, Reddit, or Facebook OAuth for the core visible-composer drafting workflow.
Users should understand that the extension inserts or copies selected text while the final Reply, Post, or Comment remains manual.
Decision rules
Permission copy can scale when users describe supported-site access, visible composer context, selected insertion, and manual posting in their own words.
If users only remember that the extension is safe, add concrete permission purpose, privacy routing, and official browser source links.
Pause publication when users infer social account control, private-message access, silent monitoring, or unattended platform actions.
Do not score permission copy with installs, revenue, ranking, ratings, reviews, or other customer outcome claims without dated proof.
Instrumentation guardrails
Label metrics as TypeToSell rollout and safety signals, not customer outcome claims, revenue lift, reply-rate guarantees, ranking proof, ratings, or reviews.
Track generation starts separately from selected copy or insertion so the team does not confuse curiosity with real workflow completion.
Measure draft handoff and copied or inserted text, but do not instrument TypeToSell as the system that presses the final public platform button.
FAQ
Permission comprehension is the best first metric because it shows whether users understand the supported-site access, visible context, selected insertion, and manual posting boundary.
No. Install volume is weaker than permission comprehension when the risk is misunderstood browser access or unsupported trust claims.
Hidden account-control confusion, private-message assumptions, social OAuth expectations, or unclear manual final posting should fail the metric review.