An affiliate funnel is split across systems by design. The conversation is in Telegram. The card payment is on a checkout platform. The deposit that actually pays you is inside a broker's back office. Three places, three logins, and a client list that is only ever as current as the last time somebody reconciled them by hand.
Scalegram pulls the last two into the first.
Checkouts Come Back In
Connect a Whop account and completed sales are synced into the client list. A purchase is matched to the person it belongs to, so their record shows what they bought and when, and their stage moves without anyone typing. Past sales can be pulled in when you first connect, with the same purchase counted only once no matter how many times a sync runs.
The immediate effect is on the assistant. Once the purchase is on the record, the person who paid this morning is not asked whether they are ready to join this evening. That single fact removes the most embarrassing failure mode an automated sales assistant has.
Broker Deposits Come Back In Too
For trading affiliates the paying event is not a checkout, it is a funded account. Where the broker exposes an affiliate API, accounts and deposits under your affiliate link are synced into a local cache and matched to your contacts by UID. The assistant can then check whether a UID it was given is really registered under you, and whether it has been funded, before anything is granted. That is the layer described in a CRM that knows what a UID is.
Two limits worth stating plainly. Affiliate APIs differ, and some of them report a deposit without an amount, so a verified deposit is not always a verified figure. And several are range queries rather than live feeds, which is exactly why the data is cached locally instead of being asked for at the moment somebody wants an answer.
What the Ad Platforms Get
A synced purchase is also a conversion. It fires server side to Meta, TikTok and Snapchat with its value attached, carrying the campaign identifiers captured back at the landing page, and it is deduplicated so a resynced sale does not become a second sale in your reports. That is what turns a cost per lead report into a cost per paying customer report, which is the only number a media buyer can optimise against. The full argument is in verified conversions.
Integrations are connected once at the account level, on the Integrations screen, and every other screen only picks from what is already connected. It is a deliberately boring rule and it is why nobody ends up with two half-configured Whop connections.
What Is Not Stored
The same restraint applies here as everywhere else in the product. Contacts, purchases, amounts, stages, tags and timing are stored. The text of your Telegram conversations is not, and card details never touch the platform at all, since the checkout stays with the processor that took the payment. The reasoning is in Telegram lead management.
"Nothing destroys trust faster than pitching somebody an offer they paid for two hours ago. Syncing the sales back was the cheapest credibility we ever bought."
— Alex Onta, Executive Director, SINGUARD
Key Takeaways
- Completed Whop sales sync into the client list, matched to the contact and counted once however often the sync runs.
- Where a broker exposes an affiliate API, accounts and deposits under your link are cached and matched by UID so the assistant can verify funding before granting access.
- Synced purchases fire server side to Meta, TikTok and Snapchat with a value and the original campaign identifiers, deduplicated against replays.
- Some affiliate APIs report a deposit without an amount, so a verified deposit is not always a verified figure.
Frequently Asked Questions
Do I have to sell through Whop?
No. The sync exists for people who already do. Sales recorded any other way, including a deposit at a broker or a purchase confirmed in conversation, land on the same client record.
Will connecting a broker API expose my clients to the broker?
The connection is your own affiliate account, reading the accounts already registered under your link. Nothing new is disclosed to the broker.
What happens if the same purchase syncs twice?
It is claimed once. The second attempt is recognised and dropped, which is what keeps the conversion count in your ad reports honest.
Where do I connect these?
On the Integrations screen, once, at the account level. Every other part of the product selects from what is connected there rather than asking for keys again.