Server-side tracking

Conversions API is the floor. Matching the buyer is the product.

Browser Pixel alone under-reports purchases. Caply sends the sale from our servers, counts it once with the Pixel, retries failures. That only gets the event in the door. Match Forecast scores how likely Meta is to recognize the buyer. Ghost lines up Caply-sent vs Ads Manager. Tracking vs creative stops you from rebuilding ads when checkout is still unmatched.

Start 14-day trial Scan your site

What you send

Purchase, Lead, AddToCart, checkout started, PageView — counted once
Email and phone — hashed on the server before Meta
Browser and click signals when the Pixel ran in the same visit
Order value and currency so Meta can optimize for revenue

Developers: field names live in /docs.

What you do not run

No tagging server. No extra hosting bill. No Meta one-click mirror that still dies when the browser is blocked. Connect a Pixel token in the dashboard. Drop https://trycaply.com/v1.js. The npm SDK is in progress.

Next step

Scan the live site, create a workspace, connect the Pixel, fire a test purchase, then open Ads Coach. If email coverage is thin or purchases have no dollar value, the coach will say so with numbers from your stream — not a generic checklist.

Match Forecast · How much are you losing? · How Ads Coach works · Docs · vs tagging servers