For AI agents: the complete documentation index is available at https://docs.clickmax.io/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.io/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.io/en/guides/pixel-details.md.
  • English

      • Where is this pixel being used?

      Under Traffic › Pixel and tracking, open the actions menu on the pixel's row and click View details. The screen that opens lists every screen that picked that pixel, lets you remove it from any of them, and shows the delivery history.

      Before you start

      1. Open the pixel details

      1. Go to Traffic › Pixel and tracking.
      2. On the pixel's row, open the actions menu.
      3. Click View details.

      At the top of the screen there are four quick answers about the pixel: the platform and its ID there, whether the Conversions API has a Credential configured or shows No credential, whether it is Receiving or Not receiving the Events without a screen, and when it was Updated at. The Edit button opens the same form as the Pixel and tracking screen.

      2. See where it is

      The Where this pixel is block lists one row per screen that picked this pixel. Each row shows the kind of screen and its name:

      Kind of screenWhere the choice was made
      DomainIn that domain's settings
      FunnelIn that funnel's settings
      Funnel (previous version)On a funnel from the previous generation. It still applies, but has no picking screen — it can only be removed from here
      PageIn that page's settings
      ProductOn that product's Pixels tab
      OfferOn that offer's screen
      Booking pageOn that booking page's General tab
      WebinarOn that webinar's Pixel step
      FormIn that form's or quiz's settings
      Redirect linkIn that link's menu

      On a funnel row that also reaches the funnel's pages and quizzes, a shortcut shows the count — Reaches 4 pages, Reaches 4 pages and 1 quiz. Click it to open the list of what that funnel covers, each item marked Page in this funnel or Quiz in this funnel, and click Hide to close it. These items have no remove button: they come from the funnel, and the funnel is what you remove.

      This list is for looking and removing. It does not add: for the pixel to start tracking a new screen, open that screen and check the pixel there — see how to choose which pixels track each screen.

      When the list is empty, the message says what to do: No screen has picked this pixel yet. Open a funnel, page, product, form or booking page and pick the pixel there.

      If the pixel is set to add itself to what you create, the notice reads This pixel adds itself to everything you create. Removing it here only takes it off this surface. — see how to use the same pixel on everything I create.

      One extra row shows up when the pixel receives the Events without a screen: conversations, email link clicks, calls and leads from capture links. It has no remove button, because it is not a screen choice — it is a mark on the pixel itself, turned off under Edit. See how the pixel receives a conversation, a call or an email link click.

      3. Remove the pixel from one screen

      1. On that screen's row, click Remove.
      2. The confirmation says exactly what will happen: the pixel stops receiving that screen's events and keeps applying everywhere else it was picked.
      3. Confirm with Remove.

      The effect is the same as unchecking the box inside the screen itself. Doing it from here pays off when the pixel is in many places and you want it off just one, without opening screen after screen.

      If a row says Surface removed instead of a name, the screen behind that binding was deleted and it no longer does anything. The button becomes Clear binding, and clearing only removes the row from the list.

      4. Check the delivery history

      Below the bindings sits the Delivery history: the latest events Clickmax tried to send to this pixel and what happened to each one — Sent, Failed, Not sent (with the reason on the row itself) or In progress.

      When the delivery reached Meta, the row also shows what Meta answered:

      • Meta response: the reason for the refusal, in Meta's own words — for example an expired token, a wrong pixel or event data in the wrong format.
      • The error Code and subcode, which separate a credential problem from a problem in the event.
      • Trace ID (fbtrace_id): the identifier Meta support asks for to investigate a delivery. Use the button next to it to copy it.
      • On an accepted delivery, the confirmation of how many events Meta received in that call.

      5. Count and filter by status

      At the top of the block sit four buttons, each with a number: All, Sent, Failed and Not sent. The numbers cover the pixel's whole history — not only the rows currently on screen.

      Click one to see only the deliveries with that status. Click the same button again, or All, to go back to the full list.

      Filtering does not change the numbers: they keep telling you how much of each status exists, so you do not lose the reference when you pick one. If the status you picked has no deliveries, the list says No deliveries with this status — the pixel does have deliveries, just none of that kind.

      This is where "why didn't my event arrive" gets answered. The results table and the most common reasons are in add a pixel and choose its events.

      Why the counts are not the total number of fires

      The numbers in the Delivery history count the deliveries that leave our server, through the Conversions API. They are not "how many times this pixel fired".

      A fire that happens in the visitor's browser goes straight from their browser to the ad platform and never passes through us — that is what makes the pixel work with no delay, and also what stops us from counting it. A pixel that sends from the browser only, including every pixel that came from the old setup, shows 0 here and is still firing correctly on each visitor.

      The total number of fires is in the ad platform's own panel: Meta Events Manager or your Google Ads conversions. What this screen answers better is the next question — why one specific event didn't arrive — and that lives in the Delivery history.

      If it didn't work

      • The list is empty and you had configured the pixel before: check whether the old setup was on another pixel in the list. Each pixel has its own details screen.
      • You want to add a screen and cannot find the button: there isn't one. Adding always happens inside the screen — see how to choose which pixels track each screen.
      • A row shows as Surface removed: the screen behind that binding was deleted. Use Clear binding to drop the row.
      • The history is empty, or the counts are all 0, but the pixel works: that is normal if it only sends from the browser. The history records only the deliveries that leave our server.
      • The list went empty after you clicked one of the buttons: that is the filter. Click All to see the whole history again.