How Zenko analyzes Fortnite

Zenko reads career stats from fortnite-api.com, a community-operated API, read-only. Epic does not publish a record of each Fortnite match, so what we get is your running totals for each team mode: eliminations, wins, top finishes, matches played and time played. The totals are also split by input device (keyboard & mouse, controller, touch). We keep that split for your profile, and challenges count every device.

We store these totals as career snapshots tied to your linked Fortnite account. Each snapshot keeps the full per-mode breakdown, so a challenge only ever reads the mode it names. Zenko never changes anything on your account, and you never share a password.

Fortnite hides career stats from third-party APIs by default. Zenko cannot read your data unless the Public Game Stats setting is turned on in your Epic account. About one in five players hits this gate during onboarding, including pro and streamer accounts. The bind flow detects it and walks you through the toggle, this section is the canonical reference if you want to turn it on ahead of time or troubleshoot.

Enable it in three steps

1. In Fortnite, open the menu and go to Settings → Account and Privacy.
2. Scroll to Gameplay Privacy.
3. Turn Public Game Stats on, then save.

That is it. Re-run the Zenko bind flow and your account will verify on the next attempt. The setting is per-Epic-account, not per-platform, so flipping it on once covers PC, PSN, and Xbox. Keep it on while a challenge runs, or your result cannot be read.

Reference: Epic's official help article.

What you see if it is off: the bind flow stops at a "stats are private" screen with a retry button. Nothing is saved on Zenko's side until the toggle is on and verification succeeds.

Without a record of each match, Zenko compares totals. When you start a Fortnite challenge, Zenko reads your career stats. As you play, it reads them again, and what your totals in that mode gained in between is your result.

Two clocks. You have 12 hours from starting to play your first match. Play none and the challenge is cancelled, and your entry is returned. Once we see your first finished match, the challenge's time limit starts. It is set when you create the challenge, from your own average match length and the number of matches the challenge allows, and falls between 90 minutes and 10 hours. The challenge shows it.

A match count is a limit. If your challenge names a number of matches, reach the target within that many matches in its mode. If your stats show more matches than the limit before the win is recorded, the challenge ends as a loss, even if you reached the target along the way: totals cannot show which match got you there.

How a result is recorded:

• On its own. Once your stats show every target met, the win is recorded at the next check, with nothing for you to do.
• "Refresh progress" (optional). Reads your stats straight away instead of waiting for the next check, once every 60 seconds per challenge. If it shows every target met, it records the win.
• "End challenge" (optional). Finishes the challenge early once you have played, settled on what you played so far.
• When time runs out. The challenge settles on what you played inside the time limit.

While a challenge is running, Zenko checks your Fortnite stats in the background every 5 to 30 minutes, roughly once per match at your usual pace. That check is what notices your first match and records a win without you pressing anything.

With no challenge running, we still take a reading of your career stats, on a schedule that follows how recently you played: about every hour if you played in the last day, every six hours if you played in the last week, and once a day otherwise. If you have not played a challenge on Zenko in 30 days, it is once a day however much you play.

Every one of these checks reads a linked Fortnite account and no other, so unlinking stops them. They run at a steady, rate-limited pace, and Zenko never sends commands to your account.

Each Fortnite challenge is scoped to one team mode, and settlement reads only that mode's career bucket:

• Solo, placement counters: top 10 / top 25 finishes (10% / 25% of a 100-player lobby).
• Duos, placement counters: top 5 / top 12 finishes (10% / 25% of 50 duos).
• Squads, placement counters: top 3 / top 6 finishes (~10% / 25% of 25 squads).

If you take a Solo challenge and play 3 solo matches plus 2 duo matches in the same window, only the solo totals count toward the challenge, and the duo matches are invisible to it. They do not use up a Solo match limit either.

Each card names its mode, and only that mode counts. If a card's mode doesn't suit you, reroll it.

Fortnite challenges count your regular Solo, Duos, and Squads matches. Ranked, Trios, Reload, and other special playlists don't count, because Fortnite reports them separately from the stats we score.

The Fortnite stats API does not separate Build from Zero Build, both variants of the same team mode fold into a single bucket. So at the data layer we cannot tell whether your kills came from Build or Zero Build matches.

What this means for you: a Solo challenge is satisfied by either Build Solo or Zero Build Solo matches. Play whichever variant you prefer; the challenge measures only the kills, wins and placements that flow into the solo bucket.

Career-delta settlement opens specific exploit vectors that the per-match settlement in Riot games does not. Zenko applies three floors to keep challenges fair:

• Lifetime BR matches floor, your linked account must have at least 50 lifetime BR matches across all modes. This blocks kill-farming in fresh-account bot lobbies, which Epic uses to ease new players into matchmaking.
• Average match duration floor, on elimination and score challenges the average length of the matches you play must exceed 10 minutes. This blocks the bus-drop pattern where a player suicides off the bus to hot-drop a high-loot point of interest, grabs a few quick kills, dies, and re-queues.
• Combat floor on placement challenges, your eliminations across the challenge must reach at least half of your own usual average in that mode for that many matches. This blocks the AFK-in-ring pattern where a player avoids combat and survives by hiding to a placement bracket.

Targets are not fixed numbers. Each one is built from your own recent matches in its mode: a challenge over a number of matches starts from what you usually reach in that many and asks for a little more, and a harder level asks for more again. A hot streak raises your next targets, a cold streak relaxes them.

Each team mode has its own baselines. Your duo average and your solo average are tracked separately, so a Duos target reflects how you play Duos, not Solo.