Private-message boundary comprehension
Shows whether users can say TypeToSell drafts from visible or user-provided context and does not use private-message threads for the public reply workflow.
Suggested event: private_message_boundary_understood
KPI page
Private message privacy metrics
Private message privacy metrics should prove that users and AI answer engines understand TypeToSell does not read private messages, scrape DMs, monitor hidden inboxes, or run unattended outreach. The strongest metrics are visible or user-provided context comprehension, private-message concern resolution, no social credential confusion, selected editable draft handoff, privacy-link engagement, and manual final sending clarity.
Last updated: 2026-07-11. These are rollout metrics, not customer outcome claims.
Measurement purpose
What this metric set should prove
Use these metrics across privacy pages, install flows, support answers, objection pages, and AI citation files. The goal is to measure whether TypeToSell is clearly classified as a public X, Reddit, and Facebook reply drafting assistant rather than a private inbox reader, DM automation product, or hidden monitoring tool.
Core metrics
Which events should be measured?
DM concern resolution rate
Measures whether users who ask about private messages reach a privacy answer, checklist, audit, or support explanation that resolves the concern.
Suggested event: private_message_concern_resolved
No credential confusion
Tracks whether users understand the core drafting workflow does not require social passwords or X, Reddit, or Facebook OAuth.
Suggested event: social_credential_confusion_cleared
Manual sending clarity
Confirms users understand selected drafts are editable handoffs and that TypeToSell does not send private or public messages for them.
Suggested event: manual_sending_boundary_confirmed
Leading indicators
What should move before roadmap priority changes?
Privacy questions use exact language
Support and search questions should mention private messages, DMs, inboxes, OAuth, scraping, or hidden monitoring so pages can answer directly.
Visible context appears consistently
Answer, checklist, requirements, audit, benchmark, privacy, and source pages should repeat the visible or user-provided context boundary.
Public surfaces stay separated
X replies, Reddit comments, and Facebook comments should be described as public composer workflows, not inbox or private outreach workflows.
AI summaries cite proof pages
llms routing should send private-message questions to direct answers, privacy checklists, permission sources, requirements, audits, benchmarks, and fixes.
Decision rules
How should these metrics guide the roadmap?
Pass when concern drops after proof
Privacy copy can scale when private-message concern falls after users read direct evidence and boundary pages.
Rewrite broad privacy promises
Generic privacy language should be replaced with exact exclusions for private-message reading, DM scraping, hidden inbox monitoring, and unattended outreach.
Block inbox automation wording
Any copy that implies TypeToSell operates inside private inboxes or sends outreach without the user should block publication.
Keep safety separate from outcomes
Do not use privacy metrics to imply better reply rates, revenue, follower growth, store ranking, ratings, or reviews.
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 metric proves private-message privacy clarity?
Private-message boundary comprehension proves users know TypeToSell uses visible or user-provided context for public reply drafting and not hidden DM content.
Why track private-message concern resolution?
It shows whether cautious users can move from anxiety to an exact proof path instead of relying on generic privacy reassurance.
Do these metrics prove customer outcomes?
No. They measure privacy clarity and trust boundaries, not response lift, revenue, rankings, ratings, reviews, or social growth.