Test your Meta tracking with Test Events
Send a test event, walk through a lander like a visitor, and confirm in Meta and in Bottega that each event arrives once.
On this page6 sections
Do this once after connecting a pixel, and again after changing what your landers send to Meta. It takes about ten minutes. You need the pixel ID and access token saved first (see Connect the Meta pixel and Conversions API).
Copy the test code from Meta
Open the Test Events tab for your pixel. Meta shows a test code there. Keep this tab open, because events appear in it as they arrive.
Paste it into Bottega
Go to Marketing › Tracking › Setup & health. In step 3, Send a test event, paste the code into Test event code and click Save.
Click Send test server event
The button is greyed out until the pixel ID and token are saved and there are no unsaved changes. When it works, Bottega shows Sent. Check Test events in Meta Events Manager.
In Meta's Test Events tab you should see a
PageViewreceived from the server within a few seconds. Bottega sends it from a placeholder page address, so don't worry about the URL Meta shows for it.
The Test your setup card lists the steps with a link to start from. Follow them in a normal browser window, not a private preview.
Click Open test click
This opens your first published lander with sample Meta ad parameters, as if someone had tapped your ad on Instagram Reels.
Scroll down the page, then tap a register button
Scroll past the depth shown in the card (50% unless you changed it). That sends the engaged-visit event. The button tap sends the CTA click.
Register with an email you haven't used on this webinar
Then submit the same email again. The second submit must not create another registration event.
Tap the WhatsApp bonus button on the thank-you page
This sends the bonus click, if your thank-you page has one.
Server events carry the test code, so they appear in Meta's Test Events tab. Look for these, using the event names from your own event map.
| Event | What to check |
|---|---|
PageView | One for each page you opened. |
ViewContent | One for the session, with scroll_depth set to your scroll depth. |
ClickCTA | Parameters cta_position and cta_text match the button you tapped. |
Lead | Exactly one, with customer information attached. Nothing new after the repeat submit. |
Contact | After the WhatsApp tap, with content_name. |
Meta counts a browser event and a server event as one when they share the same event name and event ID and arrive within 48 hours of each other. To see both sides of each event paired, use Bottega's event debugger below.
The debugger lists the latest 12 sessions from people and refreshes every few seconds while Live is on. Find your session (it shows Instagram and Instagram reels from the test click) and check each row.
- Deduplicated
- The browser and the server sent the same event ID. Meta counts it once. This is what you want.
- Server only
- Only the server sent it, because the browser side is off, an ad blocker stopped the pixel, or the page closed first. It still counts once.
- Browser only
- Only the pixel sent it. Either the server side is off for this event or it is still on its way.
- No server twin
- The server should have sent this over a minute ago and didn't. Check the access token, or the per-session limit for that event was reached.
- Rejected
- Meta refused the server event. Hover the badge to read Meta's error.
Rows sent while the test code was set show a small test label.
Clear the test event code
On Setup & health, empty Test event code and click Save. Step 5 then reads No test code set, so server events count toward your ads.
Check Meta's match quality after a day
Once real registrations have come through, Meta scores how well your events match its users. Meta shows this as Event Match Quality, from 1 to 10, on your pixel's Overview in Events Manager.
Check that it worked
- The test PageView appeared in Meta's Test Events tab.
- Your test registration produced exactly one registration event, and the repeat submit produced none.
- The event debugger shows Deduplicated on your events.
- The test event code is cleared and saved.
| What you see | Why | What to do |
|---|---|---|
| Add a pixel ID and access token first. | One of the two isn't saved. | Finish steps 1 and 2 on Setup & health. |
| Meta rejected the event. See the latest error below. | Meta refused the token or the pixel ID. | Read the Detail column under Recent Conversions API events. Usually generating a new token for this pixel and clicking Replace fixes it. |
| Nothing in the debugger | You opened a preview link. Previews and QA links show a “not tracked” badge and send nothing. | Use Open test click or the lander's live address. |
| Your session is missing from the debugger | The browser looked automated (for example a testing tool or headless browser), so it was treated as a bot. | Test in an ordinary browser window. |
| Too many attempts. Please try again in a few minutes. | Landers accept 3 submits per email per hour and 6 per network every 10 minutes. | Wait, or use a different email address. |
| The registration event is missing after the repeat submit | That is correct. Only a new seat sends a registration event. | Nothing to fix. |
Read next
Something here out of date? Tell us and we'll fix the guide.