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-on-pipeline-stage.md.
  • English

      • How do I send a conversion when a contact enters a pipeline stage?

      Each pipeline stage can have a pixel event. When a contact enters that stage, Clickmax sends the chosen event from the server, through the Conversions API, to the Meta pixels that are active and set to receive events that do not happen on a screen. That is how a sales milestone — a meeting booked, a proposal sent — becomes a conversion in your campaign.

      Before you start

      • Role: Owner, Admin or Editor. Attendants see the stage but cannot configure the event.
      • The Traffic permission, to see the account's pixels while setting the event. Without it, the event screen tells you that you don't have access to the pixels. Once set, sending does not depend on who moves the contact.
      • At least one active Meta pixel with Receive events that do not happen on a screen turned on and the Conversions API enabled with a valid token. See how the pixel receives conversations, calls and email link clicks.

      1. Pick the stage event

      1. In the CRM menu, open Pipelines and enter the pipeline you want to configure.
      2. At the top of the stage, click the ⋮ menu.
      3. Click Pixel event.
      4. Pick an event from the list. Each option shows Meta's standard name in parentheses — for example Purchased (Purchase) or Became a lead (Lead).
      5. Click Configure event.

      The stage then shows Meta's standard name right below its title — Purchase, Lead — so you can check every stage at a glance.

      To turn it off, open the same screen and click Do not send an event.

      The list only shows events the Conversions API accepts from a stage. ViewContent and the Meta standard events Clickmax does not send from the server (Search, AddToWishlist, CustomizeProduct, Donate, FindLocation) are not listed. If one of your stages already had one of them, it stays selected with the notice The server does not send this event — pick another one so the stage sends again.

      2. When the event is sent — and when it is not

      What happens in the pipelineSends the event?
      Someone drags the contact into the stage and the move is savedyes
      An automation changes the contact's stageyes
      You change the stage with a bulk actionyes
      You change the stage from the opportunity record or from the chatyes
      The stage refuses the move and the contact goes back to the original stageno
      The opportunity has no linked contactno
      You reorder the contact inside the same stageno
      You just configured the event and contacts were already in the stageno

      The rule behind the table: the event goes out after the stage change is saved, wherever it came from. It does not depend on whoever moved the card having the browser open or an ad blocker.

      Each opportunity counts once per stage: if the opportunity leaves the stage and comes back, the event is not sent again. Setting the event is not retroactive — whoever was already in the stage does not generate a conversion.

      3. Which pixels receive the event?

      The active Meta pixels in your account that have Receive events that do not happen on a screen turned on. The event screen shows how many there are.

      The filter exists because moving a card does not happen on a page, funnel or product: it is a sales milestone, and there is no screen to pick the pixel from. It is the same case as a WhatsApp conversation or an email link click.

      4. What Meta receives

      The event arrives as a conversion recorded by the CRM, in the format Meta uses for lead stages, with the contact's data: email, phone, city and state from the record, and the ad click they came from. The internet address and browser of whoever moved the card are not sent — the conversion belongs to the contact, not to your team.

      If the contact's latest ad click was on a click-to-WhatsApp ad, the event goes as a conversation from that ad — see events sent from the server.

      For the deal closed in the pipeline, prefer sending the won opportunity as a conversion. Use one path or the other for the same sale, never both.

      5. Check that it works

      1. Move a test contact into the configured stage.
      2. Open Traffic › Pixel and tracking, enter the pixel and check the row in the Delivery history.
      3. In Meta's Events Manager, the event shows up with Meta's standard name, once per pixel that receives events without a screen.

      The full check is in validate Pixel and events.

      If it did not work

      • The Pixel event option is missing from the stage menu: your role cannot configure stages. Ask an Owner or Admin.
      • The screen says you have no active pixel: the pixel may exist without Receive events that do not happen on a screen. Open Edit on the pixel, turn the option on and come back. If there is no pixel, create one under Traffic › Pixel and tracking.
      • The screen says you don't have access to the pixels: your role is missing the Traffic permission. Ask an account admin.
      • The screen says it could not read your account's pixels: a temporary read failure, not a missing pixel — do not create another one. Close and reopen the screen in a moment.
      • The contact entered the stage and nothing arrived: check that the opportunity has a linked contact and that the pixel has the Conversions API on with a valid token. The reason for each delivery is in the pixel's Delivery history.
      • The contact came back to the stage and the conversion did not go out again: expected — each opportunity counts once per stage.
      • The conversion counts twice: look for the same event set on two stages the contact passes through, or in a Google Tag Manager tag.