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-contact-and-schedule.md.
  • English

      • How does the pixel record someone messaging me on WhatsApp or booking a meeting?

      Two actions count as conversions and happen outside a sales page or a checkout: the visitor clicking to talk to you, and the visitor booking a meeting. Clickmax sends both to your pixel — Contact on a contact click and Schedule on a completed booking — as long as the pixel is set up and the page is published.

      Before you start

      • Role: Owner, Admin or Editor.
      • A pixel already checked on the screen in question: the page holding the contact button, and the booking page. If you haven't done that yet, see how to choose which pixels track each screen.
      • A saved but unpublished pixel never reaches the visitor. Publish the page (or the scheduling page) before validating.

      1. Contact clicks: WhatsApp, phone and SMS

      You don't have to tag anything beyond checking the pixel on the page itself. On any published page with an active pixel checked on it, Clickmax recognises clicks on contact links and sends Contact:

      The visitor clicksRecognised as
      A WhatsApp link (wa.me, api.whatsapp.com, web.whatsapp.com, or the link that opens the app)WhatsApp contact
      A phone link (tel:)Phone contact
      An SMS link (sms:)SMS contact

      A link to a site that merely looks like WhatsApp does not count — the match is on the exact address, so no conversion is invented on top of an unrelated click.

      The floating WhatsApp button

      The floating button already is a WhatsApp link, so it starts sending Contact with no change on your side. To check that it is active on the page:

      1. Open the page in the editor and go to Integrações (the page settings tab with the puzzle icon).
      2. Open the WhatsApp card.
      3. Confirm that Contact number is filled in and save.
      4. Publish the page.

      If your button opens the conversation through code (your own short link, or a number assembled on click), the automatic match has no way to know the destination. Declare the channel on the element with the data-cx-contact attribute, whose value can be whatsapp, phone or sms:

      <button data-cx-contact="whatsapp">Talk to a consultant</button>

      The attribute wins over the link address: when both exist, the declared channel is what counts.

      2. Completed booking

      On your public scheduling page, the pixel fires at two moments:

      • When the page opens: ViewContent.
      • When the visitor completes the booking: Schedule.

      To pick the pixel for one specific booking page:

      1. Go to Scheduling and open the Booking pages tab.
      2. Open the booking page you want to track, on the General tab.
      3. In the Pixels on this booking page block, check the box next to the pixel.

      Every check saves right away. The Meta Pixel ID field that used to sit here is gone: the ID is typed once under Traffic › Pixel and tracking, and the booking page only picks which pixel to use.

      The block only shows on a booking page with a public link. On one you have just created, the message is Save the booking page to pick its pixels — save and come back.

      If you want every new booking page to be born with a pixel, check Use on everything I create from now on in the pixel form — see how to use the same pixel on everything I create.

      3. If you were already using a pixel on your scheduling page

      Read this before checking your reports.

      If you already had a pixel on your scheduling page, it keeps sending the previous event: a completed booking still arrives as Lead, not as Schedule. This is deliberate. Switching the event on its own would change the optimisation basis of a running campaign, and you would see your Lead history stop for no apparent reason.

      The new event applies once you turn it on — Clickmax offers the switch on the pixel screen. Until then, nothing changes in what your campaign receives today.

      On a new pixel, Schedule is active from the very first booking.

      4. Publish and validate

      Publish and test on the published screen, never in the editor preview. The checking steps are in validate your Pixel and events.

      A quick test: open the published page, click the WhatsApp button and check for a Contact; then complete a test booking and check the booking event.

      If it didn't work

      • No Contact shows up: confirm that you clicked on the published page and that the link really is a contact link (a link to a "contact us" page is not a contact click — tag the button with data-cx-contact).
      • The Contact only shows up after a reload: that's normal. The event goes out on the click, and the jump to WhatsApp happens right after.
      • The booking arrives as Lead and you expected Schedule: that's the behaviour described in step 3. Turn the new event on from the pixel screen.
      • Neither ViewContent nor the booking shows up: the pixel isn't checked on that booking page. Open it on the General tab and check it under Pixels on this booking page.
      • You looked for the Meta Pixel ID field on the booking page and could not find it: it has left. The Pixels on this booking page block took its place.
      • A WhatsApp message someone sent you outside a page of yours does not show up: a conversation started in the app is a different path, and it depends on the Receive events that do not happen on a screen mark on the pixel — see how the pixel receives a conversation, a call or an email link click.
      • The Contact is counted twice: look for the same event in a Google Tag Manager tag or in code pasted into Scripts.