I build the quiet engines that turn paid ads & Google traffic into real customers.

I write the tracking code most marketers can't read.

When iOS privacy updates broke the Meta Pixel for half the internet, the marketers who survived were the ones who could deploy Conversions API server-side. That's not a marketing skill — it's an engineering skill. Mine, since 2020.

• Server-side event tracking — Meta CAPI, Google Enhanced Conversions, GA4 measurement protocol.
• 5-event Pixel funnels — Lead → OTP Verified → Conversation → Booking → Successful, with proper deduplication.
• Click-to-call instrumentation with 20s / 60s call-quality gates — not vanity-counted phone clicks.
• B.Tech, Computer Science — Anurag Group of Institutions. Python, AWS, data analytics — the whole stack.

meta-capi-lead.js · server-side conversion
// Fire a Lead event server-side to Meta Conversions API
// so iOS 17, ad-blockers, and Safari ITP can't drop it.

const payload = {
  "data": [{
    "event_name": "Lead",
    "event_time": Math.floor(Date.now() / 1000),
    "action_source": "website",
    "event_source_url": req.headers.referer,
    "user_data": {
      "em": [sha256(email.trim().toLowerCase())],
      "ph": [sha256(normalizePhone(phone))],
      "client_ip_address": req.ip,
      "client_user_agent": req.headers["user-agent"],
      "fbc": cookies._fbc,
      "fbp": cookies._fbp
    },
    "custom_data": {
      "currency": "INR",
      "value": leadValue,
      "content_name": campaign
    },
    "event_id": dedupeId  // matches client Pixel event
  }]
};

await fetch(`https://graph.facebook.com/v19.0/${pixelId}/events`, {
  method: "POST",
  headers: { "Authorization": `Bearer ${ACCESS_TOKEN}` },
  body: JSON.stringify(payload)
});