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/manage-pixels.md.
  • English

      • How do I add a pixel and choose the events it receives?

      Go to Traffic › Pixel and tracking — in the sidebar, Traffic sits inside Marketing —, click Add pixel and follow the three steps: platform, details and events. Registration happens once: the pixel stays available across the whole account and you never paste it again anywhere.

      This screen is list and registration. Choosing where the pixel tracks is each screen's job — open the funnel, the page, the product or the form and check the pixel inside it. See how to choose which pixels track each screen.

      Before you start

      • You need create access in the workspace.
      • For Meta: the Pixel ID (digits only) and, if you want server-side delivery, a Conversions API access token. Both are in Meta Events Manager.
      • For Google Ads: the Conversion ID (starts with AW-) and the conversion label for each event you turn on.

      1. Add the pixel

      1. Open Traffic › Pixel and tracking.
      2. Click Add pixel.
      3. Under Where do you advertise?, pick the platform. The cards are split into two groups — Pixel and Ad tracking — because not every measurement tool is called a pixel: the Google Ads one is a conversion tag. Platforms with a Coming soon tag cannot be picked yet.
      4. Click Continue.
      5. Fill in the Pixel ID (Meta) or the Conversion tag ID (Google Ads).
      6. Fill in the Pixel nickname. Only you see it: it is what tells two pixels of the same account apart.
      7. Pick a Project if you want. It is optional and only organises your list — see the section below.
      8. Decide the two options on this step:
      9. Click Continue.

      If the ID is in the wrong format, the screen tells you before letting you move on: the Meta one has digits only, and the Google Ads one starts with AW- followed by digits.

      2. Choose the events

      The third step lists the 13 journey events. Each row shows the visitor action in plain words, the name the platform recognises, and two switches:

      SwitchWhat it does
      From the browserThe event is sent from the visitor's browser
      From the serverThe event also leaves Clickmax's server, through the Meta Conversions API

      A new pixel starts with every event on. Turn off whatever you do not want to measure.

      When the same event goes through both paths, the platform counts one conversion — you do not need to turn one of them off to avoid duplicates. Why some events reach Meta even with an ad blocker explains how.

      A few details per event:

      • Bought has the Payment methods filters. A sale paid with an unchecked method does not generate a purchase event.
      • Opened the checkout has the Only count after personal details option. When it is on, the event waits for the visitor's name and email.
      • Opened a page and Viewed the main content can only be sent from the browser. The From the server switch shows as off, and hovering over it explains why: they are the highest-volume, lowest-identification events.
      • On Google Ads, the From the server switch is unavailable on every event, and each event you turn on asks for its Conversion label. Without the label, Google receives the hit and records no conversion.

      Click Add pixel to save.

      3. Turn on the Meta Conversions API

      With Meta selected, the third step shows the Meta Conversions API block:

      1. Paste the Access token you generated on Meta.
      2. Click Test token. The test sends a test event and does not count as a conversion.
      3. If you see Token rejected, generate a new token on Meta and paste it again.

      The Test code is optional. While it is filled in, events show up in Meta's test events tab and do not count as conversions — clear the field before using the pixel in a real campaign.

      For safety, the token is never shown back to you. When you edit a pixel that already has one, the block shows Token saved with two options:

      • Replace token opens the field so you can paste a new one.
      • Remove deletes the credential when you save, and server-side events stop being sent.

      Leaving the field blank keeps the token that is already saved.

      4. Check the delivery history

      When it looks like the pixel "is not working", start here — the answer is almost always in this list.

      1. Under Traffic › Pixel and tracking, open the actions menu on the pixel's row.
      2. Click Delivery history.

      The shortcut takes you to the pixel details screen, straight to the history block — it sits below the list of screens that picked the pixel. See where is this pixel being used, which also covers the buttons that count each outcome.

      Each row shows the event, the date and time, and the outcome:

      OutcomeWhat it means
      SentThe platform received the event
      FailedThe attempt did not complete. We retried automatically
      Not sentA setting stopped the delivery. The reason appears on the row
      In progressThe delivery started and has not finished yet

      The most common Not sent reasons:

      Reason shownWhat to do
      This event is off on this pixelTurn the event on when editing the pixel. If it is a purchase, check the payment method too
      The Conversions API token is missing on this pixelPaste the token in the Conversions API block
      This event waits for the visitor personal detailsThat is the Only count after personal details option. Turn it off to count earlier
      Meta rejected the deliveryCheck the pixel ID and generate a new token
      This event is not sent from the serverNothing to do: the event only goes out from the browser
      The event happened more than 7 days before its turn to be sentNothing to do: Meta does not accept events older than 7 days. The other events go out normally

      Turn on the new events for a pixel you already had

      If you were already using this pixel before this change, the screen shows the New events available notice at the top. While it is there, the pixel sends only the events you had configured before — and it sends three of them under the old name.

      Click See what changes to review the list, then Turn on new events to apply it. From then on the pixel sends all 13 journey events.

      The notice is about your whole account, and the button applies to every pixel that came from the old setup — including the ones on other pages of the list. The text tells you how many there are. If any of them fails to turn on, the message says how many did, and the notice stays on screen for the ones left; just click again.

      To turn on one pixel at a time, open Edit on that row: the same button appears inside the pixel's settings and applies only to it.

      Three events start arriving under a different name:

      Visitor actionArrives today asWill arrive as
      Started a purchase (opened an offer's checkout)InitiateCheckoutAddToCart
      Started a free trialPurchaseStartTrial
      Booked a meetingLeadSchedule

      If you use those names in custom audiences or in campaign optimization, review your campaigns after turning this on: a campaign optimizing for Purchase stops counting trial starts, and one optimizing for Lead stops counting bookings.

      The other events keep the same name, and no event is turned off — turning them on only adds.

      Whatever you already adjusted inside each event stays as it is too. If you unchecked bank slip on the purchase, it stays unchecked; if you asked to only count checkout openings after the personal details, that request still holds. The one exception is a purchase that was turned off in both channels: when it comes on, it starts counting every payment method, because being on with no method checked would send nothing.

      Organise the list by project

      If you run several projects in the same workspace, the Project field in the form helps you find the right pixel in a long list. Under Filters, the Project field narrows the list, and No project shows the ones you left unassigned.

      This only organises your list. The pixel stays available across the whole account. Linking a pixel to a project does not limit where it can be picked: it still shows up in the picker of any funnel, page or product in the workspace, in any project.

      The other filters in the same panel are Platform and Status, and the search at the top of the list looks up nickname or ID.

      Where the old setup went

      The Pixel ID field that used to sit inside each funnel, page, product and booking page is gone from those screens. The pixel is now registered once, under Traffic › Pixel and tracking, and where it tracks is chosen inside each screen.

      • Whatever you had set up per funnel, per page, per domain, per product or per booking page still works: every pixel was brought into this screen automatically, with the events it was already firing and the screens it was already tracking. You do not need to set anything up or pick anything again.
      • To choose which funnels, pages, products, booking pages or forms a pixel tracks, open that screen and check the pixel inside it. See how to choose which pixels track each screen.
      • To see every screen that picked a pixel at once, open View details in the row's action menu — see where is this pixel being used.
      • The tracking tabs in the page editor and in the funnel are still there, with Google Tag Manager and custom code — those are not pixels and are still set up there. Those same tabs are where the page's and the funnel's pixel picking now lives.
      • The Pixels tab inside each product is now where you pick which pixels track that product's checkout. It does not register pixels: registration stays under Traffic › Pixel and tracking.
      • The booking page's Meta Pixel ID field no longer accepts a new value. In its place, the booking page's General tab has the Pixels on this booking page block.

      Activate, deactivate and delete

      From each row's actions menu:

      • Deactivate stops the pixel from receiving events without deleting it. You can activate it again from the same menu.
      • Delete removes the pixel for good. Events stop reaching every page, checkout and form where it applied, and this cannot be undone — that is why the screen asks for the pixel nickname to confirm.

      Next steps