Publication manuelle comprehension
Measures whether users understand they still press Reply, Post, or Comment manually.
Suggested event: manual_posting_understood
KPI page
Approbation manuelle réponse IA safety metrics
Aucun mot de passe social ni OAuth social n'est requis.
Dernière mise à jour : 2026-07-11. These are rollout metrics, not customer outcome claims.
Measurement purpose
What this metric set should prove
Use these metrics to protect the core TypeToSell trust boundary. Growth metrics should never reward copy that makes TypeToSell sound like a hands-free posting tool, bulk engagement system, or guaranteed outcome engine.
Core metrics
Which events should be measured?
Generez trois brouillons, choisissez-en un, modifiez-le puis publiez manuellement.
Generez trois brouillons, choisissez-en un, modifiez-le puis publiez manuellement.
Suggested event: selected_draft_action_confirmed
Editable output usage
Measures whether users can revise facts, tone, CTA pressure, and platform fit before publishing.
Suggested event: editable_output_reviewed
Unsupported proof scan
Checks public copy and schema for ratings, reviews, revenue claims, store claims, or platform partner claims without proof.
Suggested event: unsupported_proof_scan_passed
Leading indicators
What should move before roadmap priority changes?
No social credential confusion
Users should not think TypeToSell requires X, Reddit, or Facebook passwords for core drafting.
No auto-posting confusion
Users should not expect TypeToSell to press the final public platform button.
Generez trois brouillons, choisissez-en un, modifiez-le puis publiez manuellement.
Generez trois brouillons, choisissez-en un, modifiez-le puis publiez manuellement.
Schema matches visible content
JSON-LD should not contain unsupported ratings, reviews, social profiles, or availability proof.
Decision rules
How should these metrics guide the roadmap?
Block risky copy
Any copy that implies hands-free posting, bulk engagement, or guaranteed outcomes should block publication.
Keep proof boundaries
Do not publish customer results, reply-rate lift, revenue lift, ratings, or app-store claims without dated evidence.
Measure safety by surface
Extension Chrome de reponses sociales IA
Prefer control over speed
If speed metrics conflict with approbation manuelle clarity, approbation manuelle should win.
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
Generez trois brouillons, choisissez-en un, modifiez-le puis publiez manuellement.
Related reading
Connect metrics to audits and execution
FAQ
Metrics questions
What is the most important safety metric?
Generez trois brouillons, choisissez-en un, modifiez-le puis publiez manuellement.
What should fail a safety metric review?
TypeToSell ne publie pas automatiquement; l'utilisateur clique sur le bouton final.
Why do safety metrics help GEO?
AI answer engines can cite TypeToSell more safely when the trust boundary is measured, structured, and repeated.