--- title: "Conversion API | Cometly" description: "Cometly's Conversion API sends enriched server-side events to Meta, Google, TikTok, and LinkedIn — boosting match quality, attribution, and ad performance." source: "https://www.cometly.com/platform/conversion-api" --- Platform / Conversion API # Better data. Better ad performance Send conversions server-side to Meta, Google, LinkedIn, TikTok, Microsoft, Reddit, and Taboola, and lift Meta event match quality from a typical 4 / 10 to 9.3 / 10, so the algorithms optimize against your real funnel instead of thin browser events. Get started Server-side Conversion API Meta Google Ads LinkedIn TikTok Microsoft Reddit Taboola AdRoll One OAuth-based setup pushes enriched, deduplicated conversions to all seven networks. Meta match quality ships at 9.3 / 10. What you actually get ## Server-side, 9.3 match quality, live in under an hour ### Server-side delivery Conversions fire from your backend, not the browser. Bypasses ad blockers, iOS privacy controls, and OAuth redirects. Match quality jumps from a typical 4 to 5 out of 10 to 9.3 out of 10 on Meta. Event stream Server-side Stripe subscription.created 200 HubSpot deal.stage.closed_won Browser trial.activated Sign Up Google OAuth ### Auto-enrichment Every event ships with hashed email, phone, IP, user agent, and browser ID, the full set of parameters Meta and Google use to match conversions back to real people. Match quality 9.3 / 10 - Email hashed - Phone hashed - IP address passed - User agent passed - Browser ID captured - Geo inferred ### Every major ad platform Meta, Google, LinkedIn, TikTok, Microsoft, Reddit, and Taboola, all powered by one Conversion API layer with consistent setup and consistent payloads. Server-side CAPI 9.3 / 10 match Meta Purchase +182 Google Conversion +148 LinkedIn Sale +96 ### Event deduplication Browser-side and server-side events are deduplicated by event ID before they hit the ad platform. No double counting, no inflated conversion numbers, no broken reporting. Inbound · 1,432 716 unique - P Pixel purchase evt_a92 primary - Stripe purchase evt_a92 deduped - P Pixel trial.start evt_b13 primary - Stripe trial.start evt_b13 deduped ### Optimize on the right outcome Send paying customers, demos attended, or closed-won deals, not just trial signups. The bidding algorithm trains on buyers, not browsers, so spend lands on revenue. Synced to ad platforms live · - signup via Stripe - start.trial via Stripe - deal.created via HubSpot - closed.won via HubSpot ### OAuth setup, no engineering Authenticate your ad accounts, pick the events you want to send, confirm field mapping. Live in under an hour without a developer ticket or a tag manager. OAuth setup ~5 min - Stripe Connected · just now - HubSpot Connected · 1m ago - Salesforce Connect → Day-1 capture · zero code shipped Works with your stack ## Built for every ad platform that matters Cometly's Conversion API supports the eight ad platforms B2B SaaS teams use most. Setup is consistent across all of them: connect your account, pick events, confirm mapping. Your connected stack - Meta Ads Conversions API + audiences Live - Google Ads Offline conversion import + enhanced conversions Live - LinkedIn Ads Conversions API for ABM Live - TikTok Ads Events API Live - Microsoft Ads Bing offline conversions Live - Reddit Ads Conversions API Live - Taboola Conversions API Live - AdRoll Server-to-server Conversion API Live Connect once via OAuth. Cometly manages campaigns across every platform. FAQ ## Conversion API, enrichment, and match quality: straight answers Platform-by-platform coverage, dedup with the pixel, and how Cometly pushes revenue-aware events. Book a call and we'll validate against your ad accounts. Talk to sales → What is match quality? It's Meta's score (out of 10) for how well your conversion data matches their user graph. Higher means better optimization and stronger lookalike audiences. Cometly customers typically hit 9.3 / 10. Manual CAPI setups average 4 to 5 out of 10. Does this replace the Meta Pixel? No, they work together. The Comet Pixel handles browser-side events; Cometly's server-side CAPI handles the rest. Events are deduplicated automatically. You get the best of both with no extra setup. How does Cometly enrich events? Each event includes hashed email, phone, IP address, user agent, browser ID, click IDs (fbc / fbp), and any custom CRM properties you tag. This enrichment is what gets you to 9.3 / 10 match quality. Can I send only specific events? Yes. Filter by source, value, lifecycle stage, or any custom property. Many B2B SaaS teams send only paying customers (not trial signups) to Meta, so the algorithm optimizes for revenue, not free signups. How long does CAPI setup take? Under an hour for most teams. OAuth in your ad accounts (5 min), pick which events to send (5 min), confirm field mapping (a few min). You can be sending high-quality data the same day. ## Stop training on bad data. Send better, in an hour Server-side conversions enriched with first-party data, so Meta, Google, and LinkedIn hit top-tier match quality and start optimizing on real buyers within an hour.