In e-commerce, a user clicks an ad, lands on a product page, adds an item to cart, and checks out in five minutes. Standard browser pixels handle this without breaking a sweat.
In fintech, forex, crypto brokerages, and prop trading platforms, the conversion lifecycle looks completely different: A trader clicks a paid search or social ad. They register an account (Lead). They submit identification documents for compliance (KYC verification, taking anywhere from 2 hours to 3 business days). Their identity is verified by back-office systems. They fund their wallet or trading balance with a First-Time Deposit (FTD).
If your ad algorithms optimize only for top-of-funnel form fills (registrations), you end up training ad platforms like Meta and Google to flood your funnel with bot signups and unverified users who never deposit a dollar.
Worse, client-side pixels cannot see the funded deposit. It happens behind authenticated banking portals, payment gateway webhooks, or native trading terminals (MT4/MT5/cTrader).
To fix this, you must run a server-side offline conversion pipeline. Here is how to architect one with Node.js and Meta Conversions API (CAPI).
Instead of relying on front-end browser events, your application backend sends verified milestone events directly to Meta’s Graph API:
[User Registration] -> Store click IDs (fbp / fbc / gclid) in DB │ ▼ (24-72 hours later) [Payment Gateway Webhook] -> (Stripe, Crypto Gateway, Wire Clear) │ ▼ [Internal Event Worker] -> Hash User Identifiers (SHA-256) │ ▼ [Meta Conversions API (POST)] -> "FundedAccount" / "Purchase"
When a user lands on your registration page, extract Meta's primary tracking cookies (fbp and fbc) alongside any query parameters (fbclid). Store these against the user profile in your primary database.
``javascript // client-side helper to read tracking cookies function getCookie(name) { const value = ; ${document.cookie}; const parts = value.split(; ${name}=); if (parts.length === 2) return parts.pop().split(';').shift(); }
// Payload sent to your /api/register route const registrationData = { email: document.getElementById('email').value, fbp: getCookie('fbp') || null, fbc: getCookie('fbc') || null, clientUserAgent: navigator.userAgent };
Step 2: Implement the Server-Side CAPI Dispatcher When the deposit webhook clears, your backend server dispatches the conversion event.
Because financial data contains personally identifiable information (PII), Meta requires all identifiers (email, phone, name) to be normalized and hashed using SHA-256 before transmission.
/ Normalizes and hashes user identifiers according to Meta standards / function hashParam(value) { if (!value) return null; return crypto .createHash('sha256') .update(value.trim().toLowerCase()) .digest('hex'); }
/ Sends verified funded account event to Meta Conversions API / export async function sendFundedAccountEvent({ email, depositAmount, currency = 'USD', fbp, fbc, clientIp, userAgent, transactionId }) { const PIXELID = process.env.METAPIXELID; const ACCESSTOKEN = process.env.METACAPIACCESSTOKEN; const APIVERSION = 'v19.0';
const payload = { data: [ { eventname: 'FundedAccount', // Custom conversion or mapped to Purchase eventtime: Math.floor(Date.now() / 1000), actionsource: 'website', eventid: transactionId, // Critical for deduplication userdata: { em: [hashParam(email)], clientipaddress: clientIp, clientuseragent: userAgent, fbp: fbp || undefined, fbc: fbc || undefined }, customdata: { currency: currency, value: Number(depositAmount), leadtype: 'LiveTrader' } } ] };
try { const response = await fetch( https://graph.facebook.com/${APIVERSION}/${PIXELID}/events?accesstoken=${ACCESSTOKEN}`, { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify(payload) } );
const result = await response.json(); if (!response.ok) { console.error('Meta CAPI Error:', result); return false; }
return result; } catch (error) { console.error('Network failure sending CAPI event:', error); return false; } }