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/validate-pixel-and-events.md.
  • English
  • How do I test that my Pixel is really firing?

    Tracking configured is not tracking working. Validating takes a few minutes and saves you discovering, after spending on ads, that no conversion was ever recorded.

    Before you start

    • The Pixel must be configured — see end-to-end tracking.
    • Always test on the published page. Tracking does not run in the editor preview, so testing there always gives a false negative.

    1. Publish before testing

    If you have just pasted the ID, save and publish. A change that is saved but not published never reaches the visitor.

    2. Open the page as a visitor

    Use a private window and go to the real public URL, on the final domain. Ad blockers stop the event firing — disable yours for the test, or use another browser.

    3. Confirm it in the platform's manager

    In Meta's Events Manager, check whether the page view shows up in real time. If it does, the basics are working.

    4. Test the whole path, not just the home page

    Walk the funnel as a buyer: sales page, checkout, thank-you page. It is common for the first page to be right while the final conversion does not register — and that is exactly the event that matters.

    5. Rule out the common causes

    SymptomLikely cause
    No event fires at allYou tested in the preview, or the page was not published
    Fires on the home page, not on the conversionThe thank-you page sits outside the funnel, or does not inherit the code
    Conversion counted twiceThe same event firing through both the Pixel and GTM
    Works on your machine, not the customer'sAn ad blocker or a cookie consent banner

    If your page or funnel is set up with a Google Ads conversion ID (the one that starts with AW-), the published page now initializes that ID correctly. Before, the ID was only half loaded and Google received nothing — neither the page view nor the conversion. If you had an AW- ID configured and never saw a conversion arrive, republish the page and test again: no reconfiguration is needed.

    To validate:

    1. Republish the page, even if you changed nothing on it.
    2. Open the public URL in a private window, with no ad blocker.
    3. In Google Ads, open Goals › Conversions and check the recent activity of the conversion action.

    Two notes that prevent a false negative:

    • Google Ads takes longer than Meta to show recent activity — allow a few hours before concluding it did not work.
    • A Google Ads conversion is only counted when the event has a conversion label attached. Without a label the initialization works, but the conversion is not recorded.

    Pages set up with only the Meta Pixel or with Google Tag Manager keep working exactly as before.

    If it didn't work

    • The ID is right and nothing fires: confirm the published page is the one you are opening — check the domain.
    • Only the conversion fails: check the thank-you page belongs to the same funnel and inherits the tracking.
    • An error on the page: see the error codes (Portuguese).