How to verify a milestone before you send the award
Fire awards from data you hold where you can; where you cannot, what proof to accept, how platforms define what counts, and how to review claims.
The best way to verify a milestone is not to ask for proof at all: fire the award from data you already hold, the way Shopify counts orders on Shopify and YouTube counts subscribers. Where you cannot see the number, ask for evidence from the system that recorded it, a processor or platform dashboard showing the total and the period, and check it against a written rule. Review every claim the same way and treat the evidence as confidential financial data.
Write the rule first
The rule is what you point to when a claim is borderline. Platform programs make theirs explicit. Shopify counts only orders completed on Shopify, per shop, and excludes imported, cancelled, returned, off-platform, free and fully discounted orders (Shopify terms). Kajabi counts total revenue earned on Kajabi over the life of the account, only from payments processed through Kajabi (Kajabi help center). ClickFunnels' Two Comma Club requires $1 million through ClickFunnels, according to a SupplyGem review updated October 2024. All checked November 2026.
Your rule should name:
- The metric: gross revenue, revenue net of refunds, orders, recurring revenue, cash collected.
- The period: lifetime, a calendar month, one launch.
- The source: any processor, or only activity on your platform.
- The unit: per account, per company, or per person.
- Exclusions: refunds, test accounts, accounts not in good standing.
What proof to accept
| Proof | Strength | Use when |
|---|---|---|
| Data you already hold | Strongest | The activity happened in your product or your reporting; fire the award from an event or a CSV |
| A read-only connection to the recipient's processor | Strong | You can build one; TrustMRR, a public revenue leaderboard, says it verifies revenue through a restricted, read-only payment provider key (checked November 2026) |
| A screen recording of the dashboard | Good | No integration; harder to fake than a still image |
| Dashboard screenshots with account name, period and total | Fair | Lower tiers, or alongside a short call |
| A statement from an accountant | Good, slow | The top tier, where a mistake would be public |
Review with three outcomes
- Approve when the proof meets the rule.
- Ask for more when it is incomplete, with a private link to add documents to the same claim.
- Reject with a short reason tied to the rule.
Keep a history of who decided what and when.
Handle the evidence carefully
- Limit who can open proof to the reviewers.
- Never publish proof. Ask before you share the figure.
- Ask recipients to hide customer names and bank details.
- Delete proof on a fixed schedule after the decision.
How PlaqueHQ handles it
PlaqueHQ sends awards from a CSV or pre-approved claim links when you hold the data, and runs proof submission with review when you do not: reviewers approve, reject or ask for more, and the recipient adds documents through a private link. Approval sends the recipient to claim, personalise and confirm their address. The whole sequence is in how to run a customer milestone program from your product's events and how to run a milestone award program. See the pages for platforms, agencies and communities, try a tier in the instant mockup, or read more on the home page.