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-events-per-contact.md.
  • English

      • How do I see which Pixel events a contact generated?

      Open the contact and go to the Pixel events tab. Each row is an event your ad Pixels (Meta and Google Ads) received for that contact, such as Lead, CompleteRegistration, Schedule or Purchase. For each Pixel you see what arrived from the browser and what was sent by the server (Conversions API).

      Before you start

      • You need permission to view Traffic in addition to contacts. Without it the tab is hidden.
      • The Pixel must be registered and linked to the page, form, calendar or funnel where the event happens — see Pixel scopes.

      1. Open the contact tab

      In Contacts, open the contact and click Pixel events. Events are listed newest first.

      2. Read each row

      Each card shows when the event happened on the left. At the top of the card you see the event name as it appears in Meta Events Manager (Lead, Schedule...) and what the person did ("Booked", "Started a conversation"). Conversion events get the Conversion tag. Below, each Pixel that received the event shows the platform logo, its name, its ID and the browser and server badges.

      The same event also shows up in the contact's Activity History, together with the rest of the journey.

      3. Understand the badges

      BadgeMeaning
      Browser ✓ (green)The Pixel fired on the page the person opened
      Browser — (gray)No browser fire was recorded (ad blocker, declined cookies, or an event that doesn't happen on a page, such as a won opportunity)
      Server · sent (green)The ad platform confirmed receipt from the server
      Server · sending (yellow)The send is queued and goes out within seconds
      Server · failed (red)The platform rejected the send or didn't answer. The reason shows right below the Pixel
      Server · not sent (gray)The send was skipped by configuration, for example the event is turned off on the Pixel or the Pixel has no Conversions API token. The reason shows right below the Pixel
      Server — (gray)This event isn't sent by the server (for example, a page view)

      When the browser and the server send the same event, the platform counts a single conversion. Both use the same event ID for exactly that reason.

      4. See the journey to the conversion

      On conversion events (Lead, CompleteRegistration, SubmitApplication, Schedule, StartTrial, Subscribe and Purchase), the Activity History item also shows the Journey to the conversion: a timeline of the contact's last 8 pixel steps up to that point, each with the event, what the person did (became a contact, started a conversation, booked, purchased) and when. The conversion closes the timeline, highlighted. Repeated events in a row, such as several page views, show as one step with the count (PageView ×5 · "Viewed 5 pages").

      What doesn't show here

      • Events from before the person became a contact. Browser fires from an anonymous visitor show up once they identify themselves (form, quiz, checkout or a tracked link click), as long as they happened in the same session.
      • Old events. History starts when the feature was enabled. Some recent server sends from before that may show up: contact capture, booking, webinar registration, and sales pipeline stages and wins. Conversations, purchases, link clicks and calls from before the feature don't appear, and old browser fires were never recorded.
      • Purchases from people who never became contacts. A purchase only appears once Clickmax knows which contact it belongs to.

      If it didn't work

      • The tab is missing: ask your workspace admin for permission to view Traffic.
      • The contact signed up and no event appears: check that the Pixel is linked to the sign-up form or page and validate the fire.
      • Only "Server: not sent" appears: read the reason below the Pixel. The usual ones are the event being turned off in the Pixel settings or the Pixel missing a Conversions API token — see Pixel details.