After you paste a snippet, the diagnostics tells you whether Nightify recognized it, which IDs it read and how the sending from the server is going. The Send test event button sends a test event to the providers configured on the server, so you can check that it arrives in the provider’s panel before launching a campaign.
At a glance
- Where: the Pixel diagnostics box under the Tracking code (pixel) field in the Publish step, and on the Statistics page of the event.
- Permissions for the test: View event statistics or Manage events.
- When the button appears: Send test event is visible only if a saved snippet exists or you are in the Publish step with the field filled in.
- What the test sends: a PageView event marked as a test to Meta, a ViewContent to TikTok; Google receives nothing because it has no server-side sending.
The rows of the diagnostics
| Row | What it means | How to read it |
|---|---|---|
| Status (next to the title) | Valid: snippet recognized. Invalid: snippet refused, the reason is shown in red. Not configured: no pixel on the event. | With Not configured the Configure pixel link appears, if you have the permissions. |
| Allowed providers | A fixed list: Meta, TikTok, Google. | Always there. |
| Detected providers | The providers found in the snippet. | It appears only if at least one provider was recognized. |
| Detected IDs | The identifiers that were read, per provider, in the format Meta: 1234567890 separated by a vertical bar. | Without identifiers it shows no ID detected. |
| Server-side | Status of the sending from the server for every detected provider. For Google always Google: browser only. For Meta and TikTok a list of four items: server enabled or server disabled, pixel detected or pixel not detected, token configured or token missing, test code configured or test code missing. | For example: Meta: server enabled, pixel detected, token configured, test code configured. Tokens and test codes are configuration of the platform, not of the snippet. |
| Tracking quality | Four counters of the sending from the server: queued, sent, failed, requeued (put back in the queue for another attempt). | It is not a rating: they are cumulative numbers. |
| Queue | Three counters of the current state of the queue: pending (waiting), due (ready to be sent), failed (failed for good). | Values that stay high on failed point to a configuration problem on the platform side. |
| Row per provider (for example Meta:) | sent and failed for that provider and, if there is one, last followed by the reason of the last error. | It appears only if the provider has at least one send, one failure or one skip recorded. |
| Last test | Outcome and date/time of the last Send test event; below, one row per provider with the outcome, the reason if any and the HTTP response code. | It appears only after at least one test. |
Step by step for the test
- Check the status. In the Pixel diagnostics box the status must be Valid and the Server-side row must show, for Meta or TikTok, server enabled, pixel detected, token configured and test code configured.
- Start the test. Press Send test event. What you see: the button is disabled and Sending test... appears next to it; in the Publish step the current content of the boxes is used, even if it has not been saved yet.
- Read the outcome next to the button (see the table below) and the Last test row, which also reports the HTTP code per provider.
- Check in the provider’s panel that the test event arrived: for Meta in Events Manager, in the test events section, where the PageView event carries the test_event_source data with the value nightify.
Messages and errors
| Message | Why it appears | What to do |
|---|---|---|
| Test event sent to configured server-side providers. | At least one provider accepted the test event. | Nothing: sending from the server works. |
| Test event not sent: server-side provider or test code missing. | No provider with server-side sending is configured for this snippet, or the test event code is missing on the platform side (the test is skipped). With Google only, this is the normal outcome. | Tracking in the browser works anyway. If you need server-side sending for Meta or TikTok, ask Nightify support to check the configuration of the platform. |
| Test event failed. Check tokens, pixel IDs, and logs. | The provider refused the event (expired or revoked token, pixel ID not matched, network error). | Check that the ID in the snippet is the one of the right pixel; for tokens and configuration contact Nightify support. Updating the snippet does not fix an expired token. |
| Enter a valid Meta, TikTok, or Google snippet before testing. | There is no valid snippet saved or in the field. | Paste an official snippet and check that the status is Valid. |
Special cases
- Google only. The events leave from the browser only: the Server-side row shows Google: browser only and the test always comes out as not sent.
- Counters at zero. The Tracking quality and Queue rows appear only with a snippet in place and they start from zero: they fill up with the first completed reservations, because sending from the server happens only on the confirmation of the order.
- Failed sends going up. The problem is in the configuration on the platform side (token or test code), not in the snippet: report it to support giving the event and the provider.
Rules and limits
- The test does not count as a real conversion and it does not change the reservation counters.
- The test only covers sending from the server: you check the pixel in the browser with the provider’s tools (the Meta extension, for example) by opening the event page.
Related articles
- Set up the Meta, TikTok and Google pixels on the event