Tracking that survives ad blockers.
Up to 40% of ad conversions vanish to blockers, iOS privacy, and cookie limits — and that broken data is exactly what makes your retargeting misfire. git-royal sends your events server-side through Meta's Conversions API and TikTok's Events API, so they land no matter what the browser does.
Clean data is the foundation everything else stands on.
Server to server
Events are sent from our servers, not the browser — there's nothing for a blocker to block.
Deduplicated
A shared event ID lets Meta and TikTok merge the browser + server copies, so you never double-count.
Meta CAPI + TikTok Events API
The same protocols serious advertisers rely on — connected once, running on every release page.
Your pixel, your data
Events flow to your own Meta and TikTok datasets. You own them and keep them.
Better optimization
When the platform sees the real conversions, it optimizes your ads toward them — and your costs fall.
Feeds your retargeting
Fuller event data means fuller, more accurate warm audiences to retarget. This is what makes the loop work.
Two values, then it just runs.
Connect your pixel
Paste your Pixel ID and access token in Settings — Meta, TikTok, or both.
Events fire twice
Every preview and stream-click is sent from the browser and from our server, with a shared ID.
Platforms dedupe
Meta and TikTok merge the two copies — accurate counts, no inflation.
Ads keep learning
With the real conversions visible, optimization improves and your audiences stay full.
No code required
Point-and-click setup. git-royal does all the server-side sending for you.
Private by design
Your token is stored server-side and never exposed to your browser or your public pages.
Works with your stack
Connect a pixel you already use — git-royal makes it more accurate, not fragmented.
Server-side tracking, answered.
Why do I lose conversions with a normal pixel?+
The browser pixel is blocked by ad blockers, iOS App Tracking Transparency, and privacy modes — so a big share of real conversions (widely estimated as high as 40%) never get reported. When the platform can't see them, it can't optimize your ads or build accurate audiences.
What does server-side tracking fix?+
git-royal sends the same events a second way — straight from our servers to Meta and TikTok, where a browser can't block them. Each event carries a shared ID so the platforms deduplicate the browser and server copies. You never double-count; you just stop losing data.
Do I need to write any code?+
No. Paste your Pixel ID and an access token once in Settings and git-royal does the server-side sending for you. See the Meta and TikTok setup guides — about five minutes each.
Does it work with a pixel I already use?+
Yes. Connect your existing pixel and dataset and git-royal's events flow right in alongside what you already track — making that pixel more accurate, not fragmented.
Is my access token safe?+
It's stored privately server-side and never sent back to your browser or exposed on your public pages. Only git-royal's servers use it to forward your events.
Stop losing the conversions you paid for.
Connect a pixel free and your tracking goes server-side in minutes.
Start free