Survives ad blockers
Server-side events fire from your backend, not the browser. uBlock, Brave, Privacy Badger, and ITP can't block what they never see.
Platform / Server-Side Tracking
Tracking that
doesn't break.
Cookie-less, server-side event tracking that survives ad blockers, iOS, and OAuth flows , so the events that matter most actually arrive.
Events Manager
EventsConversion APIEvents Log
Event NameDescriptionIntegrationStatusTotal Events
- PurchaseAll Stripe payments
Stripe930Last received 5 minutes ago - First Time PurchaseConverted trial in StripeStripe189Last received 1 hour ago
- Booked CallWhen someone books a call
CalendlyConfigureAction RequiredComplete0No activity yet - Deal CreatedDeal is created in HubSpot
HubSpot89Last received 3 hours ago - LeadLead created in HubSpotHubSpot2,983Last received 1 minute ago
- Qualified LeadLifecycle stage changed to MQLHubSpot1,734Last received 1 minute ago
- Sign UpWebhook catches data upon new sign up
Webhook3,093Last received 1 hour ago - Course RegistrationWebhook catches data from Skool upon sign upWebhook839Last received 2 hours ago
What you actually get
Server-side
by default.
iOS-resilient
First-party server-side calls bypass iOS Intelligent Tracking Prevention. Conversion events arrive even from the most privacy-conscious devices.
OAuth-flow safe
Google sign-in, GitHub OAuth, magic-link auth, all break browser-side tracking. Cometly's server-side events stitch the journey through every redirect.
Cross-domain capable
What does this do?
When a visitor moves between your domains, Cometly keeps them recognized as the same person. Without that link, each domain can treat them as a brand-new visitor.
Example
A visitor clicks your ad, lands on yourdomain.com, then goes to app.yourdomain.com to sign up. Cometly connects both visits to the same person.
Sign-ups happen on app.yoursaas.com? Stripe Checkout on a third-party domain? Server-side events follow the user across domains automatically.
Stripe + CRM webhooks
Native server-side ingestion of Stripe subscription events and HubSpot / Salesforce lifecycle changes. No webhooks to wire up.
Custom events via API
Send any custom event from your backend with a one-line API call. Tag with revenue, plan tier, custom properties, Cometly handles the rest.
Works with your stack
Server-side, end to end.
Cometly captures events from the browser, your servers, Stripe webhooks, and CRM webhooks, then enriches and routes them to every ad platform via Conversion API.
Your connected stack
- Live
Comet Pixel - LiveServer-side APIBackend events
- LiveStripe webhooksSubscription events
- LiveHubSpot / Salesforce webhooksLifecycle events
- Live
Meta / Google / LinkedIn / TikTok / Microsoft / Reddit / TaboolaServer-side CAPI delivery - Live
Snowflake / BigQuery / RedshiftWarehouse export via 2-way API
Connect once via OAuth. Cometly manages campaigns across every platform.
FAQ
Server-side tracking from backend, Stripe, and CRM: FAQ rundown.
Pixel pairing, Stripe lifecycle signals, cross-domain flows, and CAPI delivery. Book a call and we'll sanity-check your event architecture.
Talk to salesDo I need to give up the Comet Pixel?
No. The Comet Pixel and server-side tracking work together. The pixel handles browser-side events; the server-side layer fires for backend conversions and acts as a redundant signal that bypasses ad blockers.
How does this work with Stripe?
Native Stripe integration. Subscription events (trial start, new customer, recurring payment, churn) flow into Cometly directly via Stripe webhooks, no manual setup.
Is this the same as Meta's Conversions API?
Cometly's server-side tracking feeds Meta's Conversions API automatically. We handle event mapping, hashing, deduplication, and field enrichment, match quality typically hits 9.3 / 10.
What about cross-domain tracking?
When someone moves between your marketing site, app subdomain, or a hosted checkout like Stripe Checkout, Cometly keeps them as the same visitor, not a brand-new person on every domain. When they convert, that conversion is stitched back to the original ad click, even if the click and the purchase happened on different sites.
Will this slow down my site?
No. The Comet Pixel runs async and doesn't block page loads. Server-side events fire from your backend asynchronously and have zero impact on user-facing performance.
Tracking that survives.
Browsers can't kill it.
Server-side tracking that survives ad blockers, iOS, and browser changes — so every conversion lands, every dashboard reconciles, and your ad platforms finally optimize on real data.