BizFalcon AIMeta Ads reporting, computed from the rows.
Spend, impressions, clicks and conversions by campaign, ad set and ad.
- Spend by campaign, ad set and ad
- Impressions, clicks and CPC
- Purchases and conversion value
Why connect Meta Ads.
Contribution margin per campaign rather than blended ROAS, and the channel table in every client report.
What we read from it
- Spend by campaign, ad set and ad
- Impressions, clicks and CPC
- Purchases and conversion value
You do not have to connect it
Download the Ads Manager report as CSV and upload it. The column mapper handles the rest.
Both products were built to run on a file, because an agency cannot always get a client’s login and a brand should not have to grant one to try something.
Disconnecting is one click
Revoke the connection from Settings whenever you like. Reports you already built keep their figures; only the refresh stops.
Meta reports conversions on its own attribution window, which is why its revenue rarely matches your store's. Both figures are shown rather than reconciled into one number nobody can trace.
Connected or exported, the maths is the same.
Connect or upload
Authorise Meta Ads from Settings, or drop in the export it already produces. The column mapper handles the naming differences.
It computes, in Python
The engine writes pandas and runs it against your rows. Every figure keeps the code that produced it, so any number on the page opens to its own arithmetic.
You decide
The result lands in ProfitFalcon and ClientFalcon. Agents queue what they find; nothing runs against your account until you approve it.
The rest of the ads connectors.
See Meta Ads on your own numbers.
Fourteen days, no card. Connect it, or upload the export you already have and skip the connection entirely.