Server events (Conversions API)
Server events let Meta receive Conversions API (server-side) signals in addition to browser pixel events. In Atomicat, this is configured per Meta pixel in Page settings → Pixel.
Enable server events
- Open Page settings → Pixel.
- Add or edit a Meta pixel row.
- Turn on Send Server Events (wording may appear as “Send Server Events?” in the interface).
- Paste your Conversions API token (labeled Conversions API token / Pixel Token in places in the product).
- Select at least one standard event to send (for example PageView).
- Save Page settings, then save the page.
Requirements
| Requirement | Why |
|---|---|
| Valid Pixel ID | Browser and server-side measurement must reference the same pixel in Meta. |
| Valid access token | Meta rejects server events without a working token. |
| At least one event | The product validates that an event is selected when server events are expected. |
If the token is missing while server events are enabled, you may see prompts to add the token or to confirm saving without it (depending on the validation path).
Best practices
- Rotate tokens in Meta Events Manager if they leak; update Atomicat immediately after rotation.
- Keep browser pixel and server events aligned on event names and parameters your media buyer expects.
- Test with Meta’s Test Events tool outside Atomicat when troubleshooting delivery.
Frequently asked questions
Are server events required?
No. They are optional but recommended when you need stronger attribution or browser restrictions affect pixel quality.
Do server events replace the browser pixel?
No. They complement the browser pixel when both are configured. Your implementation plan should follow Meta’s current guidance for your vertical.