The value is not the topic alone, but whether it changes a practical decision today.
Why we failed four times before passing
Threads auto-publishing requires Meta App Review approval. We were rejected four times before passing on the fifth submission. Each rejection cited different items, but a pattern emerged.
First, demo-video length. Reviewers want to see the full flow — OAuth screen → consent → content publish → result confirmation — in under 60 seconds. Our first submission was a 90-second walkthrough and got rejected with "the outcome is not clearly demonstrated."
Second, the Privacy Policy specifics. Token storage location, retention period, and the user revocation procedure all need to be on a single page. Our Privacy Policy carves out Meta-specific items into clause 11 explicitly.
- Demo video exactly 60 seconds, English captions.
- Show OAuth screen → consent → result in one continuous cut.
- Privacy Policy URL is https and references the deauthorize/delete callbacks explicitly.
- Supply a single test user to the reviewer, with review access details.
- Make the use case one line ("daily AI briefing publishing").
- Request the minimum scopes — we narrowed to threads_basic, threads_content_publish.
- Webhook deauthorize endpoint must return 200 immediately.
- App icon: 1024×1024 PNG, no transparent background.
- Category: pick "News" or "Business" — avoid "Other."
- The word "test" or "demo" in the app name → auto-reject.
- Watch for the reviewer's follow-up message within 24 hours of submission.
- If your publish history is too short, the app gets held as "low activity." Manually publish 5+ times before submitting.
- Threads auto-publishing requires Meta App Review approval. We were rejected four times before passing on the fifth submission. Each rejection cited different it...
- First, demo-video length. Reviewers want to see the full flow — OAuth screen → consent → content publish → result confirmation — in under 60 seconds. Our first...
- Second, the Privacy Policy specifics. Token storage location, retention period, and the user revocation procedure all need to be on a single page. Our Privacy P...
→ 한국어 버전 →
- Threads auto-publishing requires Meta App Review approval. We were rejected four times before passing on the fifth submission. Each rejection cited different it...
- First, demo-video length. Reviewers want to see the full flow — OAuth screen → consent → content publish → result confirmation — in under 60 seconds. Our first...
- Second, the Privacy Policy specifics. Token storage location, retention period, and the user revocation procedure all need to be on a single page. Our Privacy P...
→ 한국어 버전 →
Take-aways
- Threads auto-publishing requires Meta App Review approval. We were rejected four times before passing on the fifth submission. Each rejection cited different it...
- First, demo-video length. Reviewers want to see the full flow — OAuth screen → consent → content publish → result confirmation — in under 60 seconds. Our first...
- Second, the Privacy Policy specifics. Token storage location, retention period, and the user revocation procedure all need to be on a single page. Our Privacy P...
→ 한국어 버전 →