BizFalcon AICallTrackingMetrics reporting, computed from the rows.
Calls, texts and form fills with their attributed source.
- Calls by source
- Texts and form fills
- Conversion outcomes
Why connect CallTrackingMetrics.
Every conversion type on one table, in the client's report.
What we read from it
- Calls by source
- Texts and form fills
- Conversion outcomes
You do not have to connect it
Export activity from CallTrackingMetrics and upload the CSV.
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.
CallTrackingMetrics logs calls, texts and forms in one export with a type column. All three are reported separately, because a form fill and a fifteen-minute call are not the same conversion.
Connected or exported, the maths is the same.
Connect or upload
Authorise CallTrackingMetrics 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 ClientFalcon. Agents queue what they find; nothing runs against your account until you approve it.
See CallTrackingMetrics on your own numbers.
Fourteen days, no card. Connect it, or upload the export you already have and skip the connection entirely.