Should I fire the Meta Pixel from a Server Component?

No — the Pixel is a browser script. Load it with next/script in the root layout and track route changes client-side. Server Components are where you call the Conversions API instead.

Do I need the @caply/track SDK or the snippet?

Either. The snippet works in any app; the TypeScript SDK gives typed helpers for App Router projects. Both share event_id with the Pixel for deduplication.

How do I test without polluting production data?

Use Meta's test_event_code and Caply's test event flow from the dashboard — events show in Events Manager's Test Events tab within seconds.

Next.js

Check your Next.js app's Meta tracking

Paste your production URL to see what tracking ships to the browser. Next.js gives you everything you need for correct Meta tracking — a Script component for the Pixel and route handlers for server events — which is exactly why half-finished setups are so common: the browser half ships, the server half stays on the backlog.

Deep scan (SPA / JS-rendered)

Real browser. Pro and Team from a workspace. Static scan stays free, no login.

Static scan

The Pixel belongs in next/script

Load fbevents.js with strategy="afterInteractive" and fire route-change PageViews from the router. The scanner shows whether the Pixel made it into the served HTML at all.

Route handlers can post to Meta — with sharp edges

A POST to graph.facebook.com from a route handler works until you hit the details: SHA-256 normalization, event_id dedup against the browser, retries with backoff, token rotation. That maintenance is the product Caply sells.

Send plaintext, we hash

From your server, send email and phone in plaintext to Caply's API — hashing happens before Meta, values are never stored raw, and each checkout is counted once via the shared event_id.

Next.js tracking questions

Should I fire the Meta Pixel from a Server Component?: No — the Pixel is a browser script. Load it with next/script in the root layout and track route changes client-side. Server Components are where you call the Conversions API instead.
Do I need the @caply/track SDK or the snippet?: Either. The snippet works in any app; the TypeScript SDK gives typed helpers for App Router projects. Both share event_id with the Pixel for deduplication.
How do I test without polluting production data?: Use Meta's test_event_code and Caply's test event flow from the dashboard — events show in Events Manager's Test Events tab within seconds.

After the scan

Send Next.js sales from the server. Count each one once.

Caply sends Purchase and Lead from managed servers with hashed customer data, deduplicated against your Pixel by event_id. Pro $29 or Team $99, 14-day trial (card required).

Start 14-day trial How Caply works

Other platforms: Shopify · WooCommerce · Wix · Squarespace · Webflow · Framer · Full scanner