Skip to main content

Pixel issues

Use this guide when page views, pixel events, checkout clicks, or conversions are missing, duplicated, or inconsistent between Atomicat and your ad platform.

Atomicat supports several tracking paths, including page pixel settings, Meta pixel events, server event options, Utmify, ClickGenius, and custom code. Problems usually come from mixing those paths without a clear source of truth.

First checks​

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

Where pixels can be configured​

Check all places that can affect tracking:

  • Page settings Pixel tab for Meta/Facebook pixel events.
  • Utmify and ClickGenius settings if enabled.
  • Page settings Code tab for top head, bottom head, top body, or footer scripts.
  • Button or element events configured inside the builder.
  • External checkout or payment provider scripts.
  • Tag Manager or scripts installed by your domain host.

If the same Meta pixel is installed in both Atomicat's pixel tab and raw custom code, duplicate events are likely.

Pixel does not fire​

Common causes include:

  • Page was not republished after adding the pixel.
  • Pixel ID was copied incorrectly.
  • No event was selected for the pixel.
  • Browser blocks tracking scripts.
  • Consent settings prevent firing until accepted.
  • The pixel was added to the wrong page or project.
  • The test was run in preview instead of the published URL.
  • The custom code has malformed script, noscript, or style tags.

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.

Atomicat can show where a Meta pixel is used on the page, including page-load events and element-triggered events. Use that usage summary before removing everything blindly.

Meta pixel and server events​

If you enable server events, Atomicat may require or recommend a Pixel Token / Conversions API token. Missing or invalid token information can prevent server-side tracking from being saved or accepted.

Use server events only when you understand how your ad account, business manager, pixel ID, and token are connected. If you are not sure, configure browser events first, then add server events with support or a tracking specialist.

Custom code warnings​

When you paste code into page settings, Atomicat validates common malformed tags and blocks suspicious redirect-injection scripts. If save fails:

  • Check that every <script> tag has a closing </script>.
  • Check that every <noscript> and <style> tag is closed.
  • Remove redirect scripts that hijack the page unexpectedly.
  • Prefer the Pixel tab for Meta pixel setup instead of raw fbq snippets.

Conversion not appearing in ad platform​

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

If Atomicat shows the lead or page action but the ad platform does not show the conversion, treat it as a tracking/attribution issue rather than a page failure.

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.

Why does Atomicat ask for a pixel token?

A token is needed for server-side events such as Conversions API. Browser-only pixel events can be configured separately, but server events need the correct token.

Can I use Meta pixel and Utmify together?

Avoid installing Meta/Facebook pixel and Utmify in the same page setting flow unless your tracking plan explicitly requires it. Duplicate tracking can create confusing or inflated events.