Connect a Meta ad account to Scalegram and campaigns, ad sets, ads and their spend are mirrored into a local store belonging to that account. Every list you then look at, every filter, every sort and every page of results, is served from that copy. The Marketing API is called on a sync, not on a click.
That sounds like an implementation detail. It is the difference between an integration that works at scale and one that spends its afternoons rate limited.
Why a mirror rather than a live query
Ad platform APIs are metered, and the meter is generous right up until it is not. A screen that queries live has to make a call for every filter change and every page of a list, and several people looking at reporting at the same time multiply that without anybody doing anything unusual. Worse, the failure is not graceful: once the quota is spent, screens stop loading, and they stop loading for everyone in the workspace at once.
Copying the account down turns the problem inside out. Lists are queried in plain SQL against local data, so paging and searching a large account is fast and costs nothing. The API budget is spent on syncing, which is a predictable job you can schedule, rather than on human curiosity, which is not.
The same argument applies to the broker affiliate data described in purchase sync, and for the same reason: several of those APIs answer range queries rather than offering a live feed, so a local cache is the only shape that works.
The quota guard
A mirror still has to be polite. Scalegram tracks how much of the ad account's API allowance the sync has consumed and slows itself down as that allowance is used up, backing off before the platform starts refusing calls rather than after. The point is to leave headroom, so an automated sync never becomes the reason a person cannot load a screen.
Practically, that means a first sync of a large historical account takes a while and then steady-state syncing is cheap, because only what changed needs fetching.
Numbers in the mirror are as fresh as the last sync, not live. When a figure in Scalegram and a figure in Ads Manager disagree by a small amount, check the sync time before checking anything else. Attributed conversion counts also move for a while after the event, on both sides.
Scrub and rename before Meta sees a file
The second rule has nothing to do with quotas. Creative files carry metadata, and the metadata people forget about is the interesting kind: device identifiers, editing software, sometimes location, and the original filename, which in this industry is frequently the name of whoever made the ad or the account it was made for.
Scalegram strips that metadata and renames the file before it is uploaded. Every creative goes up clean and under a name the platform sees for the first time. This matters for two separate reasons. The first is basic privacy hygiene for the people producing the creatives. The second is operational: a media buyer running several accounts does not want files that quietly announce their shared origin.
Treat it as the default and not as an option, because the one file that skips the step is the one that matters. Nothing in this changes the advertising policies themselves. Scrubbing metadata is housekeeping, and it is no defence at all against a creative whose actual content breaks the rules.
What the mirror is for
Once the ad data sits in the same place as the client list, spend can meet outcomes. The campaign that produced a contact is already on the contact record through the captured campaign values, and the cost side now sits beside it. Cost per verified depositor stops being a manual reconciliation between two browser tabs and becomes a column.
That is the only number worth building this for. Cost per click and cost per lead are printed by every tool in the market. Cost per customer who actually paid, tied to a creative, is the report a media buyer changes their behaviour over, and the reason the whole attribution loop exists.
Who in the team sees the ad account
An ad account connection carries spend figures, campaign structure and creative history, and not everybody in a workspace needs all of it. Access in Scalegram is granted per area, with read, add, write and delete handled separately, so a person can be given the reporting without being given the ability to disconnect the integration or remove the data behind it.
The connection itself is made in one place. Integrations are connected at the account level on the Integrations screen, and every other screen in the product only picks from what is already connected there. It is a deliberately boring rule and it exists because the alternative, connecting things from wherever you happen to be standing, produces two half-configured connections to the same ad account and a week of confusion about which one the numbers came from.
The practical version of the rule: if you are looking at a screen that offers to connect something, you are on the wrong screen. Go to Integrations, connect it once, then come back and select it.
The limits, stated plainly
The integration reads and reports. It does not turn Scalegram into a buying tool, and pointing a workspace at an ad account does not make anybody a better advertiser. Attribution is measurement. The offer at the end of the funnel still has to be worth buying, and where that offer sits in front of trading, the risk of loss for the people at the end of the chain is high and does not move because the reporting improved.
"Two rules keep this integration out of trouble: never let Meta see a file you did not name yourself, and stop calling the API long before Meta stops answering."
— Alex Onta, Executive Director, SINGUARD
Key Takeaways
- Campaigns, ad sets, ads and spend are mirrored into a local store, so lists are served by SQL rather than by the API.
- A quota guard slows the sync as the ad account's API allowance is used up, leaving headroom before calls get refused.
- Creative files are stripped of metadata and renamed before upload, so nothing about their origin travels with them.
- Mirrored figures are as fresh as the last sync, so compare sync times before chasing a small mismatch with Ads Manager.
Frequently Asked Questions
Is the ad data queried live from Meta?
No. The account is mirrored into a local store and every list, filter and page is served from that copy. The Marketing API is called during a sync rather than on every screen.
Why are creative files renamed before upload?
Because file metadata and original filenames can carry device, software and origin details. Files are stripped and renamed so nothing unintended travels with the creative.
Can Scalegram create or edit campaigns in my ad account?
The integration is built around reading account data and reporting against it. It does not replace a buying tool, and it does not make advertising decisions for you.
About the Author
Alex Onta is an Executive Director at SINGUARD. He built eTrader, the terminal, the mobile apps, eTrader Broker, Copytrading, Business and Community, along with the worldwide clustered-server infrastructure it all runs on, with his brother Roman Onta helping on the design, and he leads that division today. Together with Roman he builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals, and the two of them carry worldwide compliance, payment processing and international business structuring side by side. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.