The Deposit Verification page asks a lead to type the amount they deposited, and typed amounts have a documented relationship with the truth: loose. Some leads round up. Some show off. Some fat-finger a zero. In ordinary analytics that is noise; in ad platforms it is poison, because value-based bidding literally optimises delivery toward the profile of your highest-value converters. Feed it fabricated values and it optimises toward fabricators.
The Toolkit, in Escalating Strength
- Clamps. Every bridge page carries a minimum and maximum for the typed amount. A cap simply stops the absurd outliers at the door. This should always be on, and Scalegram defaults it sensibly.
- Fixed-value mode. Instead of the typed number, send a constant value per conversion. You lose granularity, you gain sanity: the platform optimises for depositors, not for typists. The recommended default for anyone running value-based bidding on cold traffic.
- The verification queue. Submissions land as unverified. You check them against your broker portal, where the real deposit numbers live, and confirm or reject in one click. Your reporting now distinguishes claimed from confirmed.
- Reconciled events, the real answer. Scalegram already holds true deposit data where you import broker records into trading accounts. Match a submission to a real deposit and a second, verified Purchase event fires with the actual amount. Or hold the event entirely and fire only on verification, if you prefer your ad account to see nothing but truth.
Which Mode for Which Operator
Running awareness campaigns optimised on volume? Typed values with clamps are fine; the value is informational. Running value-based bidding at real budgets? Fixed value at minimum, reconciled events if you import broker data at all. The single worst configuration is raw typed values feeding value optimisation, which is unfortunately also the default everywhere else attribution is attempted in this niche.
This is the moat. Plenty of tools can fire a Purchase event from a form. Closing the loop against actual broker records, and holding events until they are true, is what nobody else in the Telegram-affiliate niche does. It converts your reporting from optimistic to bankable.
The Numbers You End Up With
Per tracking link: clicks, submissions, verified deposits, claimed versus confirmed value, and cost per verified depositor once spend is entered. Those are numbers you can scale a campaign on, argue a broker rebate on, and run a business on. The wider architecture is in closing the black hole.
"Inflated conversion values are worse than no values. Meta believes what you send it, spends accordingly, and the bill for the fantasy arrives as bad traffic."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Self-reported deposit values inflate ROAS and actively degrade value-based bidding.
- Clamps and fixed-value mode are the safe defaults; the verification queue separates claimed from confirmed.
- Reconciled events fire the true amount after matching against imported broker records, or hold until verified.
- End state: cost per verified depositor, a number you can actually scale on.
Frequently Asked Questions
Does holding events until verification hurt attribution?
Slightly: platforms prefer fresh events, and a delayed event may attribute less precisely. The trade is timeliness against truth. The middle path many operators choose is a fixed-value event on submit plus a verified event on confirmation.
Where does the true deposit data come from?
From your broker portals: you export their reports and import the CSVs into Scalegram's trading accounts, with per-broker column mapping. Matching against submissions then happens in the verification queue.
Can I mix modes across campaigns?
Yes. Value mode, clamps and fire timing are configured per bridge page, so a cold-traffic campaign can run fixed values while a warm retargeting flow sends typed amounts.