Affiliate Safety Checker

How Twitch Affiliate review works in practice

Affiliate eligibility kicks in once a channel hits all four thresholds: 50 lifetime followers (cumulative — not inside the rolling window), plus three rolling-30-day gates of 7 distinct broadcast days, an average of 3 concurrent viewers, and 500 total minutes streamed. Twitch then runs the channel through an automated review pipeline that combines viewership patterns, follower authenticity, chat activity, concurrent stream metrics, and a first-party integrity check on watch-time telemetry. Clean passes get an invitation in 1-2 days. Out-of-band signals delay the channel pending human review; creator-community reports through 2024-2025 suggest the manual queue has grown alongside Twitch's anti-inflation tightening, so accounts with risk signals on chat ratio, IP clustering, or bot followers sit longer in review.

The review timeline is tier-dependent. Affiliate review typically resolves in 1-7 days for clean applications and 2-4 weeks when held for human inspection. Partner Path has a separate review with a higher engagement-authenticity floor. Partner reviewers explicitly look for the chat-to-viewer ratio signal at sampled windows during the most recent 30 days. A single 200-CCV stream with 10 unique chatters, on a channel that normally averages 8 CCV, is the canonical "ramp irregularity" red flag.

From 9 factors to 14: the rubric expansion

The original checker scored nine inputs: average viewers, tier, paid services running, recent strikes, DMCA history, VODs enabled, schedule, content category, and chat moderation. That covered the contractually-defensible signals: the things Twitch's published Affiliate FAQ and Onboarding pages spell out directly. What it missed were the community-reported denial patterns. Reviewers cite those signals in real rejection threads, but they don't appear in any official document.

Five new inputs were added by cross-referencing dexerto rejection-case reporting (the 2,500-sub Affiliate denied Partnership case is the canonical example), aggregate r/Twitch and Twitch dev forum denial threads, and the post-2022 hate-raid wave reviewer guidance. Specifically:

• Account age. Channels under 3 months hit the heaviest variance scrutiny (-12). The 3-12 month bucket carries a lighter -4. After the 12-month tenure mark the variance signal relaxes. New channels have no behavioral baseline for the algorithm to reference, so any spike looks anomalous.
• Simulcast. Concurrent YouTube, Kick, or TikTok streaming. Penalty depends on tier: Partners face the exclusivity clause (-20, hard violation); Affiliate applicants face the authenticity flag (-10, splits the chat-ratio signal). Twitch has informally permitted multi-platform streaming for some Partners since 2023, but the formal exception still requires application.
• Payout readiness. 2FA on plus a payout method on file. Without these, the Affiliate invitation expires 30 days after issue. -8 here is a soft penalty because it doesn't slow the review itself, but a clean review is pointless if the invitation never activates.
• Chat-to-viewer ratio. Reviewer-cited band of one unique chatter per ten concurrent (~10%). Ratios under 2% are -14 (highest non-blocker penalty in the rubric) because they read as a viewbot pattern even when the underlying audience is organic. A small audience of lurkers is treated identically to a botted audience for review purposes.
• Hate-raid handling. Post-2022 wave reviewer signal. Shields Mode preset, AutoMod tier 2, and at least one human mod is the expected baseline. Recent Shields Mode triggers don't penalise (the event itself is not a fault) but signal that reviewers will examine post-raid moderation logs.

The 14 factors and how they're weighted

Maximum penalties sum past 100, but the score floors at 0 because no real channel triggers every factor at once. The methodology disclosure block under the result lists every factor with its max penalty and reviewer-source rationale. Short tour, ordered by weight:

• Recent CG strike (-25): open community-guidelines suspension pauses review until cleared. Highest single factor.
• Content category (-20 for slots, -5 for IRL/ASMR): gambling without Mature label plus 2022 Gambling Policy compliance is typically declined.
• Simulcast on Partner tier (-20): exclusivity clause violation; Affiliate-tier penalty is lighter at -10.
• Concurrent paid-viewer service (-15): multi-vendor ramp irregularities are the easiest reviewer-detectable artificial-engagement signal.
• DMCA history (-15): pattern of takedowns reviewer-visible in VOD audit; one-off mutes are normal.
• Chat ratio <2% (-14): reads as viewbot pattern.
• Pre-Affiliate tier (-12) or account <3mo (-12): new channels carry tighter ramp-rate flags.
• No moderation in chat (-10) or no hate-raid handling (-10): visible moderation is a direct trust signal.
• Sub-10 CCV (-10) or 1000+ CCV (-5): edges of the viewer band.
• Sporadic schedule (-8) or payout incomplete (-8): structural friction signals.
• VOD storage off (-6) or chat ratio 2-5% (-6): medium-weight quality signals.
• Recent Shields Mode trigger (-5) or partner-tier scrutiny (-5) or IRL/ASMR category (-5) or account age 3-12mo (-4) or subathon schedule (-4) or chat ratio 5-10% (-2): low-weight adjustments that compound when multiple fire.

Top fixes by score band: what to do at 80, 60, 40

The Top-3 fixes panel above the factor list sorts your negatives by points-recoverable. The meta-strategy depends on the band you're in:

Score 85-100 (Low risk). Configuration is review-ready. Run the Channel Audit anyway for the data-side companion view. Helix-backed signals (live VOD recency, tag count, peak start hour, schedule consistency CV) catch issues that don't show up in self-reported configuration. If the data audit clears too, schedule the application during your typical peak hour to maximise the chat-ratio signal during the review-window samples.

Score 65-84 (Moderate risk). Fix the Top-3 first; they recover 20-40 points combined. Common patterns in this band: chat ratio at 5-10% (lift to >=10% with a chat-prompt overlay), no human mod (designate one trusted viewer), recent IRL/ASMR category change (configure the off-screen audio panel). Re-run the checker after a week to confirm the score moved.

Score 40-64 (Elevated risk). At least one structural issue is firing. Usually a simulcast on Partner tier, chat ratio <2%, or DMCA history compounding with a sporadic schedule. Don't apply yet. Pause simulcast for the 30-day review window, build chat engagement for a week, and mute any unlicensed-music VOD segments. The configuration changes recover 30-50 points. The behavioral changes (ratio, schedule) need 2-4 weeks of new history before reviewers see the improvement.

Score under 40 (High risk). An open CG strike or unmarked gambling content is the usual cause. Resolve those first; they're hard blockers. After they clear, re-evaluate with this checker. The score should jump 25-45 points immediately, putting you back in the actionable bands.

Affiliate vs Partner thresholds: what changes in the second review

Partner Path review uses the same factor set with three weight differences. Tier scrutiny flips: Pre-Affiliate has the heaviest penalty (-12) at Affiliate review; Partner-tier carries the heaviest at Partner review (engagement-authenticity floor). Simulcast becomes a hard violation at Partner tier (-20) versus a soft flag at Affiliate (-10). The chat-to-viewer ratio threshold is interpreted more strictly. Partner reviewers explicitly sample multiple windows in the 30-day pre-review window, not just live during the review.

Two factors stay constant across both reviews: DMCA history and CG strikes. A clean record on those is a precondition for any tier upgrade, and the 30-day rolling window applies identically.

Common red flags reviewers look at

The most-cited cause of delays is ramp irregularity. A channel averaging 8 CCV spends an evening at 200, then drops to 12. The signal is variance, not absolute numbers. Two more matter: chat-to-viewer ratio (typically >=1 unique chatter per 10 concurrent in sampled windows) and follower velocity (50 new follows during a 2-hour window when baseline is 1-2/hour gets noticed). None instantly disqualify, but the pattern over the 30-day window does. Twitch's anti-inflation guardrails have tightened over time around IP-clustered viewer cohorts and rapid follower-burst events; channels whose audience patterns flag these signals see longer review queues.

How to read the score, and what it can't tell you

The score is a self-reported configuration audit. It assumes your inputs are accurate. If you guess the chat-to-viewer ratio at 10% when the real number is 4%, the score will overstate your readiness. Run the Channel Audit on the same handle for the Helix-data-backed view. Bidirectional reading catches the gap between what you think your channel looks like and what reviewers see. The two tools cross-link automatically when the configuration score falls below 70.

The checker also can't see signals it doesn't ask about: payment-history disputes, content-ID strikes on specific platforms, mod-team chat-log audit, or the result of any prior Affiliate appeal. Those require either Twitch support contact or a full historical content review. Neither of those is something a client-side tool can do. Treat the score as a pre-check, not a verdict.

The patterns that survive review

Channels that survive Affiliate review consistently share a few patterns: peak concurrency stays below the channel's own organic baseline, ramp-in curves add viewers gradually rather than in a single spike, and the geographic distribution of the audience matches the channel's announced primary language and timezone. None of that is a substitute for fixing structural issues with bot followers, hostile chat, or off-platform ToS-flagged content. If you're actively in review, the strongest signal is a full uninterrupted week of organic rhythm — no audience-side experiments and no schedule changes — until the invitation arrives.