First-party conversion tracking vs third-party pixels
Browser pixels and server-side CAPI solve different problems. Here is when to use each, how they complement each other, and what breaks when you rely on scripts alone.
Read postEdge conversion infrastructure
One SDK sends canonical events through your first-party edge to Meta, Google, LinkedIn, TikTok, and seven more APIs — with hashing, dedup, retries, and delivery logs built in.
Supported destinations
One SDK
Integration surface
10 platforms
Destination APIs
Logs + DLQ
Operations
Drop in the SDK, and let us handle the ad platform specs, retries, and delivery logs.
Send canonical events from your app with the TrackStack SDK.
TrackStack maps and fans out payloads across platform conversion APIs.
Monitor delivery, retries, and failures from one operational dashboard.
Install once, configure once, and start routing conversions with confidence.
Install in 60 seconds
Start with a minimal config and keep one shared event pipeline for all your conversion platforms.
npm install @trackstack/sdkMeta Ads conversion events with pixel + CAPI deduplication.
Google Ads and GA4 conversion routing with purchase-focused mapping.
LinkedIn conversion delivery with lead and purchase normalization.
Reddit Ads CAPI delivery with event-id aware retry handling.
TikTok Events API routing with high-throughput batch semantics.
X conversion delivery with OAuth 1.0a-ready edge transport.
Microsoft UET client tracking; server-side adapter in planning.
Quora conversion routing with deterministic event shaping.
Pinterest pixel tracking available; edge CAPI adapter is planned.
Snap Pixel support in SDK toggles; edge CAPI adapter is planned.
import { createTrackStack } from "@trackstack/sdk";
export const ts = createTrackStack({
publicKey: process.env.NEXT_PUBLIC_TRACKSTACK_KEY!,
edge: "https://edge.gettrackstack.com",
platforms: {
"meta": true,
"google": true,
"linkedin": true,
"reddit": true,
"tiktok": true,
"x": true,
"microsoft": true,
"quora": true,
"pinterest": true,
"snapchat": true
},
consent: { ad_storage: "granted" }, // optional consent state
});
// In your app
ts.identify("user_123", { email, plan: "growth" });
ts.capture("SignUp", { email, platformHints: ["web", "app"] });3. Go to Dashboard → Settings → Platform Tokens and add your destination credentials.
Your app only uses a publishable TrackStack key. Destination platform tokens stay in your dashboard settings and are encrypted server-side.
Drop it into your Next.js/React app. Works alongside PostHog, Clerk, and Stripe.
Analytics
Auth
Payments
Frameworks
Core capabilities included by default so you can replace brittle pixel and tag setups.
Direct market analysis on where conversion products fail and how to pick the right architecture.
Browser pixels and server-side CAPI solve different problems. Here is when to use each, how they complement each other, and what breaks when you rely on scripts alone.
Read postGTM excels at marketer-controlled tag deployment. Server-side CAPI excels at reliable delivery. Most teams need both — but not the same tool for both jobs.
Read postRudderStack routes events to warehouses and SaaS tools. If Meta and Google are your primary sinks, a CDP adds latency and schema work you may not need.
Read postCreate a free account for your API key, follow the quickstart, and confirm your first event in delivery logs.