Skip to main content

Pixel issues

Use this guide when tracking events, page views, or conversions are missing or duplicated.

First checks​

  1. Confirm the pixel or tracking ID is correct.
  2. Publish the page after changing tracking settings.
  3. Test the live page, not only builder preview.
  4. Disable ad blockers and privacy extensions while testing.
  5. Check whether another script is firing the same event.
  6. Use the ad platform’s testing tool for confirmation.

Pixel does not fire​

Common causes include:

  • Page was not republished after adding the pixel.
  • Pixel ID was copied incorrectly.
  • Browser blocks tracking scripts.
  • Consent settings prevent firing until accepted.
  • The pixel was added to the wrong page or project.

Duplicate events​

Duplicate events often happen when the same pixel is added in more than one place, for example both page settings and custom code.

To reduce duplicates:

  • Keep one source of truth for each pixel.
  • Remove old custom scripts after moving to page settings.
  • Avoid installing the same tracking code through multiple integrations.
  • Retest after publishing.

Conversion not appearing in ad platform​

Ad platforms may take time to process events. Also confirm that the event name, domain, and attribution settings match what the platform expects.

Frequently asked questions​

Why does Atomicat show the page but the ad platform shows no event?

The page can load correctly while the platform blocks, delays, or filters the tracking event. Use the platform’s event tester.

Should I add the same pixel in custom code and settings?

No. That can create duplicate events.