Copied selected draft rate
Shows whether users find one draft useful enough to move back into the social app.
Suggested event: free_tool_reply_copied or mobile_selected_draft_copied
KPI page
The most important mobile AI reply metrics are copied selected drafts, repeat mobile sessions, return-to-app behavior, Android copy-back friction, iPhone context-handoff friction, browser-first social sessions, and manual approval comprehension. These metrics support TypeToSell's rollout order: mobile web + share/copy first, Android ReplyPilot Keyboard second, iOS keyboard plus Share Extension third, then Safari iOS and Firefox Android extensions for browser-first users.
Last updated: July 11, 2026. These are rollout metrics, not customer outcome claims.
Measurement purpose
Use these metrics to decide whether a mobile surface is proving demand or only adding implementation complexity. The goal is to measure explicit context, selected draft action, copied or inserted handoff, repeat usage, and user-controlled final posting.
Core metrics
Shows whether users find one draft useful enough to move back into the social app.
Suggested event: free_tool_reply_copied or mobile_selected_draft_copied
Separates first-time curiosity from an actual phone-based reply habit that can justify roadmap priority.
Suggested event: mobile_reply_session_returned
Indicates whether share/copy workflow friction is tolerable before native surfaces exist.
Suggested event: mobile_return_to_social_app_confirmed
Shows whether the next bottleneck is Android insertion, iOS context handoff, or browser-session coverage.
Suggested event: mobile_reply_friction_tagged
Leading indicators
A rise in copied selected drafts and repeat sessions is the strongest signal that the share/copy MVP is worth improving.
Android ReplyPilot Keyboard earns priority when Android users already copy drafts but complain about switching apps or insertion speed.
iOS keyboard plus Share Extension earns priority when iPhone users need both source context handoff and selected draft placement.
Safari iOS and Firefox Android extensions matter when users actually reply from mobile browser social pages.
Decision rules
A single generated draft is not enough evidence; copied selected drafts and repeat sessions matter more.
If users generate but do not copy, native keyboards will not solve the core product problem.
Browser-extension metrics should not be used as proof that native X app composer friction is solved.
If users think TypeToSell posts for them, the safety metric should block copy, page, or product launch.
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.
Related reading
FAQ
Copied selected draft rate is the best first metric because it proves the user found one draft worth moving into the social app.
Repeated Android mobile web usage plus copy-back or insertion complaints is the strongest keyboard signal.
No. They are rollout and workflow metrics, not revenue, reply-rate, follower, review, or ranking claims.