Pixels and tracking
The Pixel tab in Page settings configures Meta (Facebook) pixels for the current page, including optional Conversions API server events. Related integrations (Utmify, AtomicTracker) use adjacent controls in the same area of settings.
Meta pixel list
Each saved pixel typically includes:
| Field | Required | Notes |
|---|---|---|
| Name | Yes | Human-readable label. |
| Business manager (BM) | Per product form | Identifies the Business Manager context when configured. |
| Ad account (CA) | Per product form | Identifies the ad account context when configured. |
| Pixel ID | Yes | The Meta pixel identifier. |
| Conversions API token | If server events are on | Required when sending server events from Atomicat. |
| Events | At least one when applicable | Standard events such as PageView; optional value and currency for suitable events. |
Pixels are shared objects in the product: editing or deleting a pixel can affect other pages that reference the same pixel. Confirm dialogs warn before destructive actions.
Server events (Conversions API)
When Send Server Events is enabled for a pixel, the product expects a valid Conversions API token (Pixel Token in the UI). If the token is missing or invalid, saves can be blocked or you may see validation messages.
For better match quality, adding the token is recommended when you rely on server-side events.
Pixel usage summary
The usage section lists where the Meta pixel fires on the page (for example page load and specific elements such as buttons or WhatsApp). You can jump to the builder selection for an element or clear Meta pixel configuration from the page with Remove all (you can still close without saving to undo).
Orphaned element IDs (IDs no longer on the page) are called out so you can clean up events.
Utmify and Meta pixel exclusivity
Utmify pixels (Meta or Google types managed in the Utmify UI) cannot be installed at the same time as the classic Facebook Pixel configuration in the same page settings flow. The product shows a clear message if you try to mix them.
Use either the Meta pixel list workflow or the Utmify workflow for a given page, per the on-screen rules.
Validation and errors
Common messages include:
- Missing name or pixel ID.
- At least one event must be selected when events are required for the configuration.
- Pixel already exists when adding a duplicate.
- Invalid Pixel ID or Token for API validation failures.
Frequently asked questions
Should I paste my Meta base code in Custom code instead?
The product suggests using the Pixel tab for Facebook Pixel code rather than pasting duplicate tags in Codes. Follow the suggestion to avoid double-firing.
Where is Google Tag Manager?
Atomicat’s Page settings focus on Meta pixel management, Utmify for supported Google or Meta paths, and Custom code slots for other tags. Use Codes for GTM container snippets when your stack requires it.