For partners
How EGC verifies results
A studio pays for a confirmed in-game event, not for a post. A player is rewarded only after the event is confirmed. Below: how we confirm results, how we filter out fake activity, and the numbers we can show.
Verification
Three ways to confirm a result
Game data via official API
The player links their in-game tag and we compare progress with the game's official API: wins, trophies, achievements and so on. Only progress made after the player took the quest counts. The answer comes automatically and the reward is paid once the condition is met. Today this covers Brawl Stars, Clash Royale and Clash of Clans quests.
Confirmation from the studio
If a game has no open API, confirmation comes from the studio: a file of confirmed players, unique promo codes, or your postback. For a trial quest a file is enough. There is no universal integration yet: each setup is configured for the studio by agreement. The player is rewarded only after confirmation.
Screenshot and moderation
The player sends a screenshot and a moderator approves it, rejects it with a reason, or asks for more details. This is the weakest method, so for results a studio pays for we recommend the first two.
Protection
How fake activity is filtered out
Principles only, without technical details: we do not publish thresholds or trigger rules.
- Progress from a baseline. By API, only what happened after the quest was taken counts; earlier achievements are ignored.
- Repeated screenshot check. A screenshot is compared with the same player's past submissions and with other players' submissions; the moderator sees a warning.
- Multi-accounts. Suspicious accounts are flagged and reviewed manually, and violators are banned.
- Cooldowns and limits. Re-submitting the same quest is limited by a time window, and rewards are capped by limits.
- Payout holds. In tournaments a prize is held until a moderator decides if there are questions about the result.
- Manual review. Disputed cases and suspicions are checked by a person, not only by automation.
Numbers
Last 30 days
Values are calculated from the live database and refreshed hourly. Each share shows its sample size; if the sample is smaller than 30, we do not show the share.
Loading numbers…
Cross-check
What a studio can verify itself
- An export without personal data: a hashed player ID, time, submission status, quest and verification method. We currently generate it on request for the period you need; filter it by the quest column to get the rows for your quest and reconcile them with your data. Exports are shared under an NDA, kept for 90 days and deleted on the studio's request.
- By agreement: confirmation from your side in a form that suits you. The simplest option: you send a file of confirmed players (nickname or ID and event date), and we reconcile it and pay the reward. Later we can connect unique promo codes or your postback. This is a custom setup, not a ready-made feature.
- A trial quest with a report: funnel, verification structure, what was filtered out, timelines. We prepare the report manually in this structure.
Payouts
Payout transparency
Proofs of real payouts to players are published in the channel @egc_payouts. They show that rewards are received by real people.
Honestly
What we do not promise
- Part of the quests is checked manually by screenshot: this is less reliable than an API, and we do not call such results "100% verified".
- We do not offer "100% protection from fake activity": we show which checks we apply and what the numbers look like in practice.
- We do not have an independent external audit yet (for example via AppsFlyer): the proof rests on the description of our mechanics and the real numbers above.
Want to test it on a trial quest?
Write to us: we will launch a quest for your task and send a report on the results.