Your token stays with you
The request goes from this page to graph.facebook.com and nowhere else; Trakero never receives the token. It's in the request body, never in a URL.
Check that your pixel id and access token work before you connect a server. The event goes from this browser to Meta with your test event code, so it shows up under Test events and never in your live data.
Fill in the pixel id, access token and test event code.
The request goes from this page to graph.facebook.com and nowhere else; Trakero never receives the token. It's in the request body, never in a URL.
The tool won't send without a test event code, so Meta shows the event in Events Manager → Test events and doesn't count it as a real conversion.
An invalid token, a wrong pixel id or a missing permission each get a plain explanation and the step that fixes it.
Platform rules from Meta: Conversions API, using the API and test events, Meta: Server event parameters.
In Events Manager, open your dataset and the Test events tab. The code (like TEST12345) is shown next to “Test server events”.
Test events usually appear within a minute. Check you are looking at the same dataset id, and that the Test events tab shows server events.
No: Trakero sends a test event from the dashboard when you connect Meta. This tool is for checking a token or an existing setup.
Trakero captures click ids, hashes customer data and sends each purchase once to Meta, TikTok, GA4 and more from your server, so ad blockers and Safari can't lose it.
Free tools
Check, build and debug your tracking in the browser. Nothing you paste leaves the page.
A short email when Meta, Google or TikTok change a tracking rule that affects stores, and when we add a free tool. A few a year. Unsubscribe in one click.
We use your address only for these emails. Privacy policy.