Clicks, impressions and on-Meta conversions tell you how an ad behaved. They tell you almost nothing about whether a forex broker, crypto exchange or signals channel actually made money. The metrics that matter in regulated finance verticals live off-platform: a first-time deposit recorded in the broker’s back office, a paid Telegram join that turns into a funded account, a qualified lead that clears KYC. None of those show up cleanly in Meta Ads Manager.
This guide is about closing that gap. It covers the custom metrics finance agencies actually report on, how to track them when the conversion happens outside Meta, and how to feed them back into the platform so optimisation works against real outcomes instead of proxy events.
Why Meta’s Default Metrics Fail Finance Verticals
Standard Meta reporting was built for ecommerce. A purchase fires a pixel event, the value flows back, and ROAS reconciles itself. Finance funnels break that loop in three ways.
- The conversion is delayed and off-site. An FTD might land days after the click, inside a trading platform or casino back office that has no pixel.
- The conversion is on another app entirely. A signals provider’s “purchase” is a Telegram join, then a paid subscription, neither of which Meta sees natively.
- Volume metrics lie about quality. A campaign can drive 400 cheap leads where 12 fund accounts, and another drive 90 leads where 40 fund. On clicks and lead-form fills, the first looks better. On cost-per-FTD it is a disaster.
If you optimise to the metrics Meta hands you by default, you optimise to the wrong thing. The fix is to define the metrics your client measures their P&L by, track them at the source, and report on those instead.
The Custom Metrics Finance Agencies Actually Need
Cost per First-Time Deposit (Cost-per-FTD)
The FTD is the anchor metric for forex brokers, crypto exchanges and iGaming operators. It marks the first real money a new customer commits, which is the only acquisition number a finance client trusts. The work is in attribution: the deposit happens in the back office, so you have to tie it back to the ad that drove the click.
In practice that means logging each FTD against its source click, deduplicating returning depositors so you only count genuinely new funded accounts, and capturing the deposit value rather than a flat count. Reported per campaign and per ad, cost-per-FTD becomes the number you scale and cut on. We go deeper on this in our guide to off-Meta conversion and FTD tracking.
Cost per Telegram Join
For signals providers and any broker running a Telegram funnel, the join is the conversion. The problem is that Telegram and Meta do not talk to each other. The link between an ad click and a channel join is the Facebook Click ID (fbclid): capture it on the click, carry it through the join, and you can attribute each Telegram join to the exact ad that produced it. Send that join back to Meta through the Conversions API and the algorithm can finally optimise toward it.
Track cost-per-Telegram-join the same way you track cost-per-FTD: per ad, with the join value where one exists. It is the single metric most finance agencies are flying blind on. Our breakdown of Telegram conversion tracking for ad campaigns covers the attribution mechanics in full.
Qualified Deposits and KYC-Cleared Leads
Not every lead is worth the same, and in regulated verticals the gap is enormous. A lead that never clears KYC has zero value; a deposit that gets reversed for fraud has negative value. Worth tracking as distinct custom metrics:
- Qualified lead rate — leads that pass KYC or your client’s qualification bar, as a share of total leads.
- Deposit-to-funded rate — deposits that stick versus those reversed or charged back.
- Cost per qualified deposit — spend divided by deposits that survive verification.
These let you optimise toward customers a broker can actually keep, not toward form fills that evaporate at the compliance step.
CAO Funnel Efficiency
Cost-per-acquisition optimisation (CAO) funnel analysis looks at efficiency at every stage rather than just the endpoints: click to landing, landing to Telegram join, join to FTD, FTD to funded. When cost-per-FTD spikes, the CAO view tells you where, whether the click got more expensive, the landing page stopped converting, or joins stopped depositing. That is the difference between “the campaign got worse” and “fix the landing page.” A CAO funnel breakdown turns a single bad number into a specific action.
Setting Up Custom Metric Tracking
Step 1: Define the metric with the client
Before any code, agree on definitions. What counts as an FTD, the deposit minimum, whether a returning depositor counts. How a qualified lead is defined. The reporting currency and how multi-currency deposits are normalised. The target cost-per-FTD or cost-per-join. Write it down. Most reporting disputes in finance come from two parties counting the same event differently.
Step 2: Capture the click identifier
Everything downstream depends on stitching the off-Meta conversion back to the ad. Capture the fbclid at the moment of the click and persist it, through to the Telegram join via a deep link or bot start parameter, and through to the deposit via your landing page and CRM. Lose the click ID and the conversion becomes an anonymous number with no campaign attached.
Step 3: Send conversions back via CAPI
On-pixel tracking cannot see a back-office deposit or a Telegram join, so use the Meta Conversions API for server-side events. Fire the custom event (FTD, qualified deposit, Telegram join) from the server, include the deposit or subscription value and currency, and attach the click ID so Meta attributes it correctly. For conversions you missed, a Meta Events CSV import backfills them rather than leaving holes in the data.
Step 4: Validate against the back office
A custom metric is only as good as its accuracy. Reconcile your tracked FTD count against the broker’s actual deposit ledger, check for double-counting of returning customers, confirm values match, and watch for conversions that fired but never attributed. Run this monthly. A cost-per-FTD that quietly drifts from reality is worse than no metric at all.
Optimising Against Custom Metrics
Once the real metrics flow back into Meta through CAPI, optimisation changes. Instead of bidding to landing-page views or lead-form submissions, you optimise to FTDs and qualified deposits, scale the ads with the lowest cost-per-FTD, and cut the ones generating cheap leads that never fund. Value-based bidding becomes possible too: a USD 50 deposit and a USD 5,000 deposit are not the same conversion, and passing the value lets Meta chase the depositors actually worth acquiring.
This is also where campaign triage earns its place. When you are watching cost-per-FTD across dozens of campaigns and several brands, you need a surfaced view of what breached threshold overnight, not a manual sweep through Ads Manager. Triage flags the campaigns where the custom metric moved, so you act before spend compounds.
Reporting Custom Metrics to Clients
A finance client does not want a screenshot of Meta’s dashboard. They want the numbers they run their business on, framed against target. Build the report around cost-per-FTD and cost-per-Telegram-join by campaign and brand, the qualified-deposit and KYC-clearance rates, value-based ROAS on real deposits rather than pixel-reported revenue, and CAO funnel efficiency so they can see where the money leaks.
For agencies running ten or twenty brands, this is where flat-fee tooling matters. Stacking a Telegram tracker that bills a percentage of ad spend on top of a per-client reporting tool gets expensive fast, and it leaves the FTD data in one place and the join data in another. A platform built for multi-brand finance management keeps Meta metrics, Telegram joins and FTDs under one client-to-brand-to-account hierarchy, at a flat price with no per-client or per-join charge. If you want it programmatically, the same custom metrics are available through the MCP and REST API for AI-driven reporting workflows.
Get Your Real Metrics in One Place
The agencies that win finance accounts are the ones reporting on deposits, not clicks. That means defining the metrics your clients measure their business by, capturing the click ID, sending conversions back through CAPI, and validating against the back office, then optimising and reporting against those numbers instead of Meta’s defaults.
Ott was built to do exactly this for forex, crypto, iGaming and signals agencies: FTD tracking, Telegram join attribution, CAO funnels and budget alerts in one platform at a flat monthly fee. Start a free trial, no card required, or book a demo and we’ll map your custom metrics with you.