Pulsar is a single pixel that captures every standard event at your origin and relays it server-side to Meta CAPI, TikTok Events API, Google Ads, GA4, Snapchat, LinkedIn, and Pinterest — with the rich first-party signals each platform needs for high match quality.
No third-party SDKs. No client-side tag chaos. No ITP or ad-blocker losses. Just clean, enriched, server-to-server delivery to every platform you run ads on — with per-event delivery logs you can actually audit.
A real customer pixel — each ring is a funnel stage, each sector a destination.
A diagnosis of how conventional conversion tracking fails in 2026 — and why the loss is invisible until your CAC explodes and you can't figure out why.
(ITP).fbq() calls before they fire.You're paying Meta to optimize on the easy half of your funnel.
Conversions API. TikTok wants Events API v3.uploadClickConversions.Measurement Protocol v2.Seven integrations. Seven payload shapes. Seven retry loops. Seven things to monitor.
Operators need observability, not promises.
We've watched browser pixels go from 95% reliable to 60% reliable in five years — and we still couldn't tell anyone exactly where the other 40% went.
The team behind Pulsar has spent the last decade running performance ad campaigns and shipping conversion infrastructure for ecommerce brands. We've shipped Meta Conversions API integrations three times, in three different stacks, for three different clients, and re-shipped them after every Meta API version bump.
We've debugged match-quality drops with no tooling, paged engineers at 2am over a TikTok token expiry, and lost real money to ad-blocker shrinkage we couldn't measure. We've watched plugin vendors silently change auth schemes mid-campaign. We've explained to marketing teams why their EMQ was 2.8 when they were "doing everything right."
Pulsar is the tool we wished existed. Built by operators who got tired of flying blind, for operators who refuse to.
Install one snippet. Pulsar captures every standard event at your origin, enriches it server-side with the rich signals each ad platform wants — IP, User Agent, parsed device class, hashed PII, click IDs from every paid network — and fans it out to every destination you've connected: Meta CAPI, TikTok Events API, Google Ads, GA4, Snap, LinkedIn, Pinterest.
Every event has a delivery log. Every destination has a health card. You see exactly what each platform received — and when it didn't, you see why.
Four metrics from live customer deployments. Every number verified against the source — Meta's own dataset_quality API for match-quality, server-side UA classification for human-only signal. Nothing inflated by crawlers.
Pulled live from Meta's dataset_quality API on Armadorn (2026-06). Composite average 4.6 across all event types. Industry browser-pixel baseline is typically 2.8–3.5.
Meta's own preview crawler, Googlebot, SEO scrapers, headless test runs — Pulsar tags them at ingestion and skips the destination fan-out. 46,313 bot events filtered across live deployments. Your match-quality stays clean.
Real-time UA classificationPlus 52% with Meta's _fbp cookie and 17% with hashed email — the exact signals every ad platform's match-quality model rewards. Measured on bot-filtered live traffic.
Signal coverage, human eventsMeta CAPI, TikTok Events API, Google Ads, GA4 MP, Snap, LinkedIn, Pinterest. One snippet, one payload, every platform's match-quality optimization handled server-side.
Production adapters, all liveEvery feature solves a concrete operator pain. Click any card to read the deep-dive.
Your conversions arrive even when the browser doesn't. Route around ITP + adblockers from your own origin.
Read more ›Install once. Pulsar fans out to Meta, TikTok, Google, GA4, Snap, LinkedIn, Pinterest from a single payload.
Read more ›Pulsar detects WooCommerce/Shopify/Wix events automatically. ViewContent, AddToCart, InitiateCheckout, Purchase — no tag-manager required.
Read more ›Captures fbclid, gclid, ttclid, gbraid, wbraid, sccid, li_fat_id, epik on landing — persists across the session — sends to every destination.
Read more ›IP, User Agent, parsed device class, OS, browser, screen, timezone, language, UTM, connection — harvested + sent server-side.
Read more ›Persistent personaId. Email, phone, name, company auto-extracted from any form. Hashed before leaving the server.
Read more ›Every event has a delivery log. Every destination has a health card. See exactly what each platform received — and didn't.
Read more ›Claude reads your last 24h of deliveries, surfaces actual problems in plain English: "Snap mismatched 12% of currency codes — check checkout."
Read more ›Self-host. Per-account scoping. Per-pixel ownership. You own the database. Your data never leaves your infrastructure.
Read more ›Every event your visitors trigger is captured at the source, relayed server-to-server, and delivered to every ad destination you run — without ever touching the parts of the browser adversaries can block.
Your site fires a single, bare-metal event to your Pulsar origin. Pulsar enriches it server-side — IP, User Agent, hashed identifiers, click IDs, device class — then forwards to Meta, TikTok, Google Ads, GA4, Snap, LinkedIn, and Pinterest through their official server APIs. The browser never speaks to an ad network directly.
Browser-side fbq()
calls ship in every adblocker filter list. iOS Safari
erases third-party cookies on a 7-day clock. The
server-to-server channel between your origin and Meta is
invisible to both — and indifferent to whatever cookie
policy a vendor decides on next.
Industry benchmarks place conversion loss from adblockers + ITP between 25% and 40%. And the customers you lose are precisely the cohort you most want to optimize for — privacy-aware, mobile-Safari, higher-intent. Browser pixels show you the easy half of your funnel.
Install once. Pulsar fans every standard event out to every destination you've connected — with platform-specific match-quality optimization baked in.
A single async <script> on every page. Auto-versioned via ?v=N + 5-minute cache. No tag manager required.
Meta CAPI, TikTok Events API, Google Ads (Customer Match + Click Conversions), GA4 MP, Snap, LinkedIn, Pinterest — all fed from the same payload.
Each adapter reshapes the canonical payload into its destination's expected schema — including hash format, event-name mapping, and click-ID propagation.
Pulsar reads the URL + DOM and infers standard events. WooCommerce, Shopify, Wix, custom checkouts — it just works.
Five URL patterns trigger the canonical funnel events. Capture-phase click handlers infer AddToCart from button text + DOM context.
And most that do haven't wired up the right dataLayer events. Pulsar removes the chicken-and-egg: events ship from day one.
If a funnel event matches, the default PageView is replaced. No duplicate-event spam. Currency parsed from ISO codes + symbols (EGP, USD, EUR, JPY...).
fbclid, gclid, ttclid, gbraid, wbraid, sccid, li_fat_id, epik — captured on landing, persisted across the session, attached to every event you ship.
Detected from URL on first hit, stored in localStorage + Pulsar's session, replayed on every downstream event for 90 days.
Stronger than email-hash or IP+UA. Required for Google Enhanced Conversions and Meta's deduplication. Operators lose them constantly through SPA navigation.
Runs before SPA routers can rewrite the URL. Backed by a 30d localStorage key and the server-side Pulsar persona.
Pulsar harvests every first-party signal each destination's match-quality model rewards — from server-side IP/UA to client-side timezone, language, screen, and connection.
IP + UA from the request. Device class, OS, browser parsed with ua-parser-js. UTM, timezone, language, screen, connection, color scheme from the snippet.
Meta's EMQ rewards each signal you send. Adding IP + UA + click-ID + email-hash + phone-hash typically lifts EMQ from 3.2 to 5+ on the same traffic.
IP extracted via X-Forwarded-For chain. UA parsed once, stored as deviceType / os / browser for downstream campaign filtering.
Pulsar issues a persistent personaId per visitor. The moment they fill any form — name, email, phone, company — we capture, hash, and attach those identifiers to every downstream event.
Any <input> with a recognizable name/type (email, tel, fname, company) is captured on blur, hashed, and merged into the persona.
Meta CAPI, LinkedIn Conversions, Google Enhanced — all reward hashed email + phone + name. Without form capture, you ship blank user_data and EMQ caps below 3.5.
SHA256 hashing happens in the Pulsar backend, not in the browser. Raw email/phone live in your DB; only hashes leave the network.
Every event has a delivery log per destination. Every destination has a live health card. The cockpit answers "did it actually arrive?" without you opening Ads Manager.
Click any event in the Analytics drawer. See the exact JSON each destination received, HTTP response, attempt count, retry status. Auditable.
When match-quality drops or a destination silently breaks, you need to see which destination, which event, and why. Black boxes don't cut it.
Bullseye visualizes event-by-destination success at a glance. Health cards surface delivery rate + recent errors. Drill into the table for raw payloads.
Claude reads your delivery logs, your match-quality, your retry chains — and tells you, in plain English, exactly which destinations are degrading and why.
Open any destination card. Hit "Generate insight." Claude Sonnet 4.6 synthesizes your last 24h of deliveries into 2–4 actionable sentences.
The pattern is buried in there — "12% currency-code mismatches", "auth refresh expired 3h ago", "ViewContent missing PII on mobile". AI surfaces it instantly.
The prompt only sees your actual delivery aggregates + sampled payloads. Each insight cites the metric range. You can verify everything in the underlying log.
Pulsar is built on a strict account > pixel > event isolation model. Self-host and your visitor data never leaves your infrastructure — only relayed payloads do.
Accounts hold team members + billing. Pixels are owned by accounts. Every event/delivery/persona is hard-scoped to a pixel. No cross-tenant leakage.
A SaaS pixel that sends your visitor data to a third-party warehouse defeats the purpose. Pulsar's data plane runs on your infra; only the cockpit UI is shared (if you choose managed).
Docker compose or native Node. Mongo for state, BullMQ for delivery, Caddy for TLS. MIT-licensed open core means audit, fork, harden — whatever your security team needs.
Three things compound every week you wait. None of them show up on your Meta dashboard until they've already cost you.
That's one in three customers your ad platforms never learn from. The longer this runs, the worse your audiences get and the more you overpay to reach the wrong people.
Compounds weeklyMeta optimizes against the signal it receives. Feed it noise and you pay more per acquisition. Operators we've migrated saw blended CAC fall 28% in the first 30 days.
Direct revenue impactToken expires. API version drops. Plugin updates. You find out from a cost spike in Ads Manager three days later — not from your tracking tool. Black-box infra ages badly.
Discovered too lateDeploy on your own infra. MIT-licensed open core. Your data, your servers, your control.
SHA256 hashing client-side on the server hop. Raw email/phone never leave your origin.
BullMQ-backed retry, exponential backoff. Every failure logged and resumable.
Consent flags propagate per-event. PII can be stripped on a per-jurisdiction policy.
No tag manager. No DNS changes. No engineering sprint. Drop one script, connect your destinations, watch payloads arrive.
Paste the Pulsar tag in your site's <head>. Works on WordPress, Shopify, Wix, custom builds — anywhere you can drop a script tag.
The snippet is ~2.4kb gzipped, async, and never blocks the page.
<script async src="https://pulsar.<your-host>/p/PIX_8f3a.js?v=8"> </script>
Open your pixel page. Add Meta CAPI, TikTok, Google Ads, GA4, Snap, LinkedIn, Pinterest — each takes a token + account ID.
Pulsar validates the credential live: green light = ready to ship.
⚫ meta-capi // auth ok · ds_124 ⚫ tiktok-events // auth ok · pix_K1 ⚫ google-ads // auth ok · cust_9 ⚫ ga4-mp // auth ok ⚫ snap-capi // auth ok
WooCommerce / Shopify / Wix events are detected from URL patterns + DOM signals. Pulsar enriches the payload with IP, UA, device, click IDs, hashed PII — then fans out to every destination.
You can also fire custom events via pulsar('track', 'Lead', {...}).
{ "type": "Purchase",
"value": 1299.00,
"currency": "EGP",
"email_h": "a83f...4d",
"fbclid": "IwAR1...",
"ip": "154.187.x.x",
"device": "mobile/iOS" }
Every event appears in the Analytics drawer with a delivery log per destination. Click any row to see the exact JSON each platform received and its HTTP response.
Match-quality drops? Health cards flag the destination before you see it in Ads Manager.
13:42:08 Purchase ✓meta ✓tt ✓g ✓ga4 13:41:52 AddToCart ✓meta ✓tt ✓g ✓ga4 13:41:33 PageView ✓meta ✓tt ✓g ✓ga4 EMQ avg: 5.4 · deliver: 99.8%
A standard CAPI integration sends events to one destination (Meta) from your server. Pulsar sends every event to every destination you've connected (Meta, TikTok, Google, GA4, Snap, LinkedIn, Pinterest) with platform-specific match-quality optimization, and gives you a delivery log per event per destination.
You don't write seven integrations. You don't monitor seven retry loops. You don't debug seven black boxes.
No. Pulsar runs alongside your browser pixels and complements them. Meta/Google explicitly recommend dual-firing (browser + server) and de-duplicate by event ID. Pulsar handles the server-side leg of that pattern for every destination.
If you don't have a browser pixel installed yet, Pulsar still works — you just lose the dedup match boost on the part of your traffic that does survive ad-blockers.
Pulsar is self-hostable as an open-core product. You deploy the backend (NestJS + MongoDB) on your own infrastructure. Your visitor data never leaves your servers — only the relayed payloads go to the destinations you configured.
A managed cloud option is also planned for teams that don't want to operate the infra.
Every event carries a consent flag from your consent banner. Pulsar can strip PII per-event based on consent state, jurisdiction, or destination policy. PII is SHA256-hashed before relay — raw email/phone never reach the destinations.
You can configure per-destination consent policies (e.g., "drop the event for non-EU-consenting users on Meta but allow on GA4 without PII").
One snippet in your <head>. One CAPI token per destination you want to feed. Under 5 minutes from sign-up to first delivery. Walk through it in How It Works.
Match-quality is Meta's scoring of how confidently they can identify the user behind each event — based on the signals you send (IP, UA, email hash, phone hash, click IDs, fbp/fbc cookies, etc).
Higher match-quality = better attribution = lower CAC. Browser pixels alone typically score 3.0–3.8. With Pulsar's server-side enrichment, operators reach a consistent 5.0+ on Meta's EMQ composite.
Yes. Pulsar's form auto-capture extracts email, phone, name, company, title from any form submission — the signals that matter for B2B match-quality on LinkedIn, Meta, Google. Custom Lead + SubmitApplication events ship out of the box.
Open core is free forever: self-host the full feature set. Managed cloud pricing is event-based and scales with usage — starts free for small operators, with paid tiers for higher volume + premium support. Reach out for early-access pricing.
Install in 5 minutes. Connect your destinations. Watch every payload arrive in the cockpit. Default rules: no credit card, no engineering sprint, no lock-in.