Editorial
Practical guides on CAPI setup, deduplication, delivery monitoring, and how to evaluate tracking tools based on operational reality — not marketing hype.
Featured
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 articleAll posts
GTM 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 postEnhanced Conversions improves Google's match rate by sending hashed first-party data with each conversion. This guide covers what to hash, where to fire events, and how to verify payloads land.
Read postServer-side GTM containers and Stape proxy Meta and Google through your subdomain. Purpose-built edge routers skip the GTM layer while keeping first-party delivery.
Read postSending the same conversion from browser and server without a shared event ID double-counts in ad platforms. Here is how dedup works at Meta, Google, and TikTok — and how to implement it in your app.
Read postuBlock Origin and filter lists like EasyList block requests to `facebook.net` and `google-analytics.com` by default. Understand the mechanism so you can design tracking that actually delivers.
Read postBeyond Meta and Google, LinkedIn and TikTok have server-side conversion APIs with their own payload shapes and match keys. Here is what each expects and where teams get stuck.
Read postPostHog answers product questions; TrackStack delivers conversions to ad platforms. Here is how to run both without duplicate scripts, conflicting proxies, or split event schemas.
Read postTrackStack public keys ship in client bundles. Domain allowlisting restricts which origins can send events — a basic security control every production app should configure.
Read postCAPI endpoints return 429s, 500s, and invalid payload errors. Without retries and a dead-letter queue, failed conversions vanish. Here is what to monitor and how to alert on delivery health.
Read postCDPs excel at enterprise data routing to hundreds of tools. If your only goal is reliable Meta and Google conversion delivery, the cost and complexity rarely justify the bill.
Read postPipeline SaaS and e-commerce shops share ad platforms but not conversion logic. Match keys, event timing, and what you optimize for differ — and your tracking setup should reflect that.
Read postAd blockers, ITP, consent banners, and SPA routing gaps silently drop browser-side events. Here is the full failure stack — and why server-side delivery is no longer optional.
Read postSkip Google Tag Manager. Wire first-party Meta CAPI in Next.js with an SDK that handles hashing, deduplication, retries, and delivery logs from your existing app code.
Read postWhy TrackStack routes conversions on Cloudflare Workers: low latency, first-party domains, durable retries, and platform adapters without shipping secrets to the browser.
Read postMeta Event Match Quality and Google's match diagnostics reward complete, consistent identifiers. Learn which fields move scores and how to debug weak match keys in delivery logs.
Read postClerk gives you verified emails and stable user IDs at signup. Wire identify() and SignUp capture so Meta and LinkedIn get match keys the moment accounts are created.
Read postEvery conversion should leave an HTTP trail. Delivery logs show platform responses, payloads, and retries — so you fix match issues before wasting ad spend.
Read postThe Configure split separates credentials, per-platform event allowlists, and checklists from generic settings — so you ship destinations without tag manager indirection.
Read postElevar optimizes Shopify and WooCommerce datalayers. B2B SaaS on Next.js needs Clerk identity, trial events, and LinkedIn pipeline CAPI — a different shape than ecommerce server-side GTM.
Read postSelf-serve signups and enterprise closed-won deals happen weeks apart. Instrument product milestones and CRM offline events so ads optimize on the full funnel.
Read postClosed-won in Salesforce does not automatically teach Meta or Google. Upload offline conversions with hashed email and deal value to close the attribution loop.
Read postExpanded canonical events — BookDemo, ActivateWorkspace, ExpandSeat — let ad platforms optimize on pipeline quality, not pageviews.
Read post