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/custom-events.md.
  • English

      • How do I track clicks and specific actions on a page?

      Page views and purchases are automatic. Everything between the two — a button click, video progress, a block being opened — has to be declared as a custom event.

      Before you start

      • Basic tracking has to be working first.
      • Decide up front what you will do with the data. An event nobody looks at only clutters the report.

      1. List what is worth measuring

      Good candidates are actions that signal intent before the purchase: a click on the main button, reaching the end of the page, interacting with the form. Start with two or three.

      2. Standardise the names

      Agree a convention and keep it. click_main_button and mainButtonClick become separate events and the report stops making sense.

      3. Declare the events

      For pages hosted elsewhere, the route is the Browser SDK — see external pages with Clickmax. The available events and their formats are in the reference (Portuguese).

      4. Validate on the published page

      Like any tracking, a custom event does not fire in the preview. Follow validate pixel and events.

      5. Use the event

      A custom event can become an automation trigger — tagging whoever clicked the button and did not buy, for example.

      If it didn't work

      • The event does not appear: confirm you tested on the published page, with no ad blocker.
      • Similar names show up separately: standardisation is missing — fix and republish.
      • The trigger does not fire the automation: check the event's exact name.