Skip to main content

How to Track Button Clicks with a Pixel

Use pixel click tracking when paid traffic depends on knowing which CTAs convert. Atomicat can fire Meta events from Button clicks (and related controls such as WhatsApp) when the page pixel setup supports it.

Before You Start​

Make sure you have:

  • Access to Page settings → Pixel on the target page.
  • A valid Meta Pixel ID (and Conversions API token if you use server events).
  • A Button (or WhatsApp component) already placed for the CTA you want to measure.

Do not paste a duplicate Meta base code in Custom code if the Pixel tab already manages the pixel — double tags cause double-firing.

See How to add pixels to a page and Pixels and tracking.

Step 1: Configure the Page Pixel​

  1. Open the page in the Page Builder.
  2. Open Page settings → Pixel.
  3. Add or select a Meta pixel with at least:
    • Name
    • Pixel ID
    • One or more events (for example PageView, plus click events you will attach later)
  4. Save pixel settings.
RuleDetail
Shared pixelsEditing a pixel can affect other pages that use it.
Utmify exclusivityClassic Facebook Pixel list and Utmify Meta/Google pixels cannot be mixed on the same page.

Step 2: Attach Tracking to the Button​

  1. Select the Button on the canvas.
  2. Open button settings for pixel / click tracking (available when page tracking supports it).
  3. Choose the Meta event that should fire on click (for example a custom or standard event your ads use for CTA measurements).
  4. Keep the button’s main click action (link, modal, checkout) configured separately — tracking sits alongside the CTA action.

See Button element (reference).

For WhatsApp chat starts, use the WhatsApp component’s Facebook pixel click settings instead. See How to add a WhatsApp button.

Step 3: Check the Pixel Usage Summary​

  1. Return to Page settings → Pixel.
  2. Open the usage summary — it lists where the Meta pixel fires (page load, buttons, WhatsApp, and similar).
  3. Confirm your button appears. Jump to the builder selection if you need to edit an orphaned or wrong element.

Clean up events tied to deleted element IDs so reports stay accurate.

Step 4: Publish and Verify​

  1. Save and Publish the page.
  2. Open the live URL in a fresh session.
  3. Click the tracked button.
  4. Confirm the event in Meta Events Manager / Test Events (or your ad platform tester).

If numbers stay at zero, see Pixels troubleshooting.

Best Practices​

  • Track the primary CTA first — avoid attaching every decorative button.
  • Name buttons and pixels clearly so the usage summary stays readable.
  • After changing pixel or button events, republish before testing ads.
  • Prefer the Pixel tab over Custom code for Meta base tags.

Troubleshooting​

ProblemWhat to try
Event not in MetaConfirm publish, ad blockers off, and the button event selection.
Double countingRemove duplicate pixel snippets from Custom code / Codes.
Button missing from usageRe-select the button event; remove orphaned element IDs.
Utmify conflict messageUse either classic Meta list or Utmify on that page — not both.

Outcome​

CTA clicks fire the Meta events your ads and analytics depend on, with a clear map of where the pixel is used on the page.

FAQ​

Can buttons fire pixel events?

Yes. Button clicks can be tied to pixel events when the page tracking setup and button settings support that event.

Should I paste Meta base code in Custom code?

Prefer the Pixel tab for Facebook Pixel configuration to avoid double-firing.

Does this replace Convertions API setup?

Click events on elements work with your page pixel setup. If you enable Send Server Events, add a valid Conversions API token in the Pixel tab as well.