Connect TikTok's Events API
Two things to copy from TikTok — your Pixel Code and an access token — and git-royal handles the rest. Here's what the Events API is, why it matters, and exactly where to click.
The short version: the TikTok pixel lives in the visitor's browser and reports what people do on your page. But browsers increasingly block it — ad blockers, privacy modes, in-app browser limits — so a big share of your real conversions never get reported. When TikTok can't see conversions, it can't optimize your ads or build accurate audiences.
The Events API fixes that by sending those same events a second way: server to server, straight from git-royal to TikTok, where a browser can't block them. Each event is sent with a shared ID so TikTok deduplicates the browser and server copies — you never double-count, you just stop losing data. (Meta calls its version the Conversions API; it's the same idea.)
You don't write any code. git-royal does the server-side sending for you. You only need to give it two values from your TikTok account so it sends to your pixel: a Pixel Code and an Events API access token.
Server-side
Events sent from our servers, not the browser — nothing to block.
Deduplicated
Shared event IDs mean the browser + server copies never double-count.
Your data
Events flow to your own TikTok pixel. You own it.
Get your Pixel Code + access token
- 1
Open TikTok Events Manager
In TikTok Ads Manager, open Tools → Events (this is Events Manager). Under Web Events, click Manage or Set up Web Events.
- 2
Create a Web pixel
Click Connect data source → Web. Choose TikTok Pixel and Manually install the code (you won't actually paste code — git-royal fires the events — but this is the path that also exposes the Events API). Give it a name like “git-royal” and create it.
- 3
Copy your Pixel Code
Open the pixel you just made. Its Pixel Code (the ID) is shown near the top — a short alphanumeric string like
C1A2B3D4E5F6G7H8. Copy it. - 4
Generate an Events API access token
In that pixel's Settings, find Events API and click Generate access token. TikTok creates a private, long-lived token tied to this pixel — copy it now, as it may only be shown once.
- 5
Paste both into git-royal
In git-royal, go to Settings → TikTok, paste your Pixel Code and access token, and save. That's it — server-side tracking is live. Your token is stored privately and never shown in your browser again.
Keep the access token private — it can send events to your pixel. Treat it like a password. If it's ever exposed, revoke and regenerate it in the same Events API settings.
Common questions.
Do I need to be a developer?+
No. git-royal does all the server-side sending. You only copy two values (Pixel Code + token) from TikTok once and paste them into Settings.
Will this double-count my conversions?+
No. git-royal sends each event with a shared event ID, which TikTok uses to deduplicate the browser pixel and the server copy. You get accuracy, not inflation.
Can I connect both Meta and TikTok?+
Yes. Connect either or both in Settings. git-royal sends your funnel events to each connected platform independently, so you can advertise on both from the same pages.
TikTok's screens look a little different from these steps.+
TikTok updates Events Manager fairly often, so labels may move. The path is always: Ads Manager → Tools → Events → your Web pixel → Settings → Events API → generate token.
Is my access token safe with git-royal?+
It's stored privately server-side and is never sent back to your browser or exposed on your public pages. Only git-royal's servers use it to forward your events to TikTok.
Official reference: TikTok — About Events API. Next: run an effective retargeting campaign →