---
title: "Server-Side Tracking | Cometly"
description: "Cometly's server-side tracking captures every event — even when browsers, ad blockers, and ITP get in the way. Cleaner data, better attribution, more revenue."
source: "https://www.cometly.com/platform/server-side-tracking"
---

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.

Get started

Track Any Event

Direct Integrations

Catch Webhook data from any application

### Events Manager

Create Event

Events Conversion API Events Log

Event Name Description Integration Status Total Events

- Purchase All Stripe payments Stripe 930 Last received 5 minutes ago
- First Time Purchase Converted trial in Stripe Stripe 189 Last received 1 hour ago
- Booked Call When someone books a call Calendly Configure Action Required Complete 0 No activity yet
- Deal Created Deal is created in HubSpot HubSpot 89 Last received 3 hours ago
- Lead Lead created in HubSpot HubSpot 2,983 Last received 1 minute ago
- Qualified Lead Lifecycle stage changed to MQL HubSpot 1,734 Last received 1 minute ago
- Sign Up Webhook catches data upon new sign up Webhook 3,093 Last received 1 hour ago
- Course Registration Webhook catches data from Skool upon sign up Webhook 839 Last received 2 hours ago

What you actually get

## Server-side by default

### 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.

Delivery vs blockers 100% pass

uBlock Brave ITP ATT

Browser

Server-side

### iOS-resilient

First-party server-side calls bypass iOS Intelligent Tracking Prevention. Conversion events arrive even from the most privacy-conscious devices.

iOS · ITP + ATT +49 pts

Browser pixel 47%

Server-side 96%

Match rate, last 30 days

### 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.

OAuth redirects stitched

1. 1 /signup your.app visitor_8f2
2. 2 /oauth google.com visitor_8f2
3. 3 /callback your.app visitor_8f2
4. 4 /trial your.app visitor_8f2

### 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.

Learn more

Sign-ups happen on app.yoursaas.com? Stripe Checkout on a third-party domain? Server-side events follow the user across domains automatically.

Cross-domain journey 1 visitor

yoursaas.com Marketing

app.yoursaas.com Product

checkout.stripe.com Billing

All stitched to visitor_8f2

### Stripe + CRM webhooks

Native server-side ingestion of Stripe subscription events and HubSpot / Salesforce lifecycle changes. No webhooks to wire up.

Stripe webhooks live

- subscription.created → trial.start
- invoice.paid → conversion
- subscription.updated → upgrade
- charge.refunded → refund

### 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.

POST /v1/events 200 OK

```
{
  "event": "feature.activated",
  "revenue": 99,
  "plan": "pro",
  "account_id": "acc_8f2"
}
```

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

- Comet Pixel Live
- Server-side API Backend events Live
- Stripe webhooks Subscription events Live
- HubSpot / Salesforce webhooks Lifecycle events Live
- Meta / Google / LinkedIn / TikTok / Microsoft / Reddit / Taboola Server-side CAPI delivery Live
- Snowflake / BigQuery / Redshift Warehouse export via 2-way API Live

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 sales →

Do 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.