Server-side conversion tracking that repairs itself.
X-Ray tracks conversions, revenue, and ad attribution across Google, Meta, TikTok, LinkedIn, and Microsoft, then watches for events that go silent. When something breaks, it files a pull request to fix it.
The week nobody noticed.
- Mon
Someone refactors the checkout button. The purchase event stops firing with it.
- Tue
Conversions look flat. Nobody looks twice. Flat is normal on a Tuesday.
- Fri
Spend is up and revenue is not. Nothing has errored. There is nothing to alert on.
- Day 14
Someone opens the file. Two weeks of budget went against numbers that never arrived.
The fix is one line. Reaching it took a ticket, a sprint, and an engineer with other work.
It reads its own conversion data.
When a funnel step drops, X-Ray finds the event that stopped firing and surfaces what fixing it requires. Attribution, funnel analysis, and retention data in one view.
It follows the click past the browser.
X-Ray captures the click identifier from Google, Meta, TikTok, LinkedIn, and Microsoft the moment a visitor lands. When your backend confirms the purchase hours later, the revenue joins on that same identifier, so every conversion points back to the ad that started it.
- 01
Ad click
The click identifier from Google, Meta, TikTok, LinkedIn, or Microsoft arrives and gets stored against the visitor session.
- 02
Signup
You call identify. The anonymous visitor becomes a known one, and the attribution carries forward.
- 03
Purchase
Confirmed server-side, with no browser in the room. Revenue and conversion value join on the same identifier.
It installs itself.
Connect your repo and walk away. It reads the codebase, maps the path your customers actually take, and writes the instrumentation to match. A second agent reviews the work before you ever see it. What reaches you is a pull request.
Common questions.
- What is server-side conversion tracking?
- Server-side conversion tracking records purchase and signup events on your backend server instead of in the user's browser. Because the data never passes through a browser, ad blockers, iOS privacy restrictions, and cookie expiry cannot interfere with it. X-Ray goes further: it installs the tracking code itself, monitors events for decay, and opens a pull request when something stops firing.
- Which ad platforms does X-Ray support?
- X-Ray captures click identifiers from Google (gclid), Meta (fbclid, fbc, fbp), TikTok (ttclid), LinkedIn (liFatId), and Microsoft (msclkid). Each identifier is stored against the visitor session and joined to server-side purchase data, so revenue attribution works across all five platforms without relying on browser cookies.
- How does X-Ray track server-side conversions?
- X-Ray stores the ad click identifier when the visitor lands, then joins it to the purchase event when your backend confirms it. The match happens server-side, so conversions attribute correctly even when a user clears cookies or changes devices between the ad click and the purchase.
- How is X-Ray different from Google Analytics?
- Google Analytics relies on browser-side JavaScript that breaks when users block cookies or scripts. X-Ray uses server-side event capture, so conversion data survives ad blockers and browser restrictions. It also writes and repairs its own tracking code, so broken events get fixed before a week of spend goes against missing data.
- What happens when my conversion tracking breaks?
- X-Ray monitors every event it installed. When an event goes silent or conversion numbers drop unexpectedly, it finds the code change responsible and files a pull request with the fix. You review and merge. No ticket, no sprint, no engineer pulled away from other work.
- Does X-Ray support the Meta Conversions API?
- Yes. X-Ray captures the Meta fbc and fbp identifiers client-side and sends matched conversion events to the Meta Conversions API server-side. This improves event match quality and extends attribution beyond what the Meta Pixel can record on its own.
- How does X-Ray install conversion tracking without a developer?
- X-Ray reads your codebase, maps the path your customers actually take, and writes the tracking instrumentation to match. A second agent reviews the work before you see it. What reaches you is a pull request you approve. No developer is pulled away from other work and no tracking spec needs to be written by hand.
- Does server-side conversion tracking comply with GDPR and CCPA?
- Server-side tracking keeps personal identifiers on your infrastructure rather than exposing them to third-party browser scripts, which reduces your attack surface and gives you direct control over what data is collected, what is sent to ad platforms, and when it is deleted. This makes it generally lower risk under GDPR and CCPA than pixel-based client-side tracking.
Find out what your funnel is missing.
Point X-Ray at your repo and see what conversion events it would write and which ones it would fix.