Mobile generation starts
Shows that users are willing to bring visible post context into a mobile web flow.
Suggested event: mobile_reply_generation_started
KPI page
Mobile web share/copy KPIs
Mobile web share/copy KPIs should prove that phone users can provide visible post context, generate three drafts, choose one, copy it, return to the social app, edit, and manually post. The strongest KPIs are mobile generation starts, selected draft copy, repeat mobile sessions, return-to-app completion, free-to-trial intent, and low confusion about manual final posting.
Last updated: July 11, 2026. These are rollout metrics, not customer outcome claims.
Measurement purpose
What this metric set should prove
Use these KPIs to decide whether mobile web is only usable or truly validating demand. The MVP should prove the reply job before Android keyboard, iOS keyboard plus Share Extension, or mobile browser extension scope begins.
Core metrics
Which events should be measured?
Selected draft copied
Shows that one generated option is useful enough to take back to the social app.
Suggested event: mobile_selected_draft_copied
Repeat session rate
Shows whether mobile web becomes a repeat workflow rather than a one-time test.
Suggested event: mobile_reply_session_returned
Checkout or activation intent
Shows whether mobile web value connects to account creation, trial start, or extension activation.
Suggested event: start_cta_clicked or billing.checkout_started
Leading indicators
What should move before roadmap priority changes?
Context input is understood
Users can paste or share post text without needing social passwords, hidden OAuth, or native install steps.
Draft selection is visible
The interface makes it obvious that the user chooses one editable draft rather than sending anything automatically.
Mobile web remains fallback
Even after native work, mobile web should remain the lowest-friction fallback for every user segment.
Copy-back friction is tagged
Complaints about switching apps should be stored separately from complaints about reply quality.
Decision rules
How should these metrics guide the roadmap?
Pass before native
Move to Android keyboard only after repeat Android mobile web usage and selected copy are visible.
Do not count weak generations
A generation without selected copy is interest, not workflow completion.
Improve prompts before platform scope
If copied draft rate is low, improve Marketing Brain and reply quality before native insertion.
Keep manual posting explicit
The KPI page should repeat that the final Reply, Post, or Comment action stays manual.
Instrumentation guardrails
Keep metrics honest
Keep metrics as product signals
Label metrics as TypeToSell rollout and safety signals, not customer outcome claims, revenue lift, reply-rate guarantees, ranking proof, ratings, or reviews.
Separate generated from selected
Track generation starts separately from selected copy or insertion so the team does not confuse curiosity with real workflow completion.
Keep final posting outside TypeToSell
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
Connect metrics to audits and execution
FAQ
Metrics questions
What KPI validates mobile web share/copy?
Selected draft copy plus repeat mobile sessions validates mobile web better than generation count alone.
What KPI means native keyboard may be worth it?
Repeated Android or iPhone usage plus copy-back friction points to native keyboard or share-extension scope.
Does mobile web KPI tracking include auto-posting?
No. It tracks draft handoff and copy behavior while final posting stays manual.